Dear Mike Frysinger,
In message 201011101706.17988.vapier@gentoo.org you wrote:
based on your based comments, i'm really not surprised. you constantly prefer to ignore reality and the state of GNU toolchains. plus, you ignore other
I'm a software developer. If tool chains are broken, I try to fix them or get them fixed. My time is way to precious to be wasted on broken tools. Rather I spend it on getting tools to do what I need.
obvious setups. just because the toolchain in question may produce binaries doesnt mean the binaries are in the ABI format desired for linux userspace.
blindly assuming the toolchain that is being used to create u-boot will also be used for creating userspace apps is fundamentally wrong.
Sincere condolences if you have to work in such an environment.
But even then, this is not a reason to break the code for people who are in a more lucky position.
IIRC, HOSTCC refers to the C compiler on the and for the build host, i. e. when running on a x86 system it will create x86 code. This is obviously wrong when we try to build fw_printenv for, say, a PPC4xx system.
and it is trivial for the user to say "i wish to build tools for PPC4xx userland"
Is it? And how so? And why would this not be the default setting, then?
Mike, please state clearly if you have a solution for the current problem, or I will just revert that commit.
Best regards,
Wolfgang Denk