[Buildroot] make troubles
r.carter at cs.auckland.ac.nz
Sun Aug 6 22:03:06 UTC 2006
I'm beginning to understand what a strange creature gcc is. I found
this page during my research. Perhaps it might help in visualising
the various combinations of compilers and libraries on different
On 5/08/2006, at 6:18 AM, Rob Landley wrote:
> On Thursday 03 August 2006 8:36 pm, Robert Carter wrote:
>> I did a svn update to 15773 and ran the build once again with the
>> same result.
>> The good news is that when
>> is not set and busybox-1.2.1 is used the build succeeds. So perhaps
>> the problem is with some of the recent 'testing' busybox commits.
> I switched on -Werror to break on warnings during the devel cycle, but
> different versions of gcc produce different warnings and most of
> them are
> entirely spurious. (The gcc developers have this nasty habit of
> that their compiler is more important that the software it's
> compiling. If
> the Linux kernel guys felt that way, we'd need to rebuild the whole of
> userspace with every dot-release...)
> I switched them off for 4.1 because lots of the warnings that
> produces are
> confirmed non-problems that would cost us size to work around. (If
> the code
> does "if(a) x=1; else x=thingy();" then x is _not_ uninitialized
> after that.
> Trust me on this one!) As far as warnings go it's a deeply broken
> and -Werror just isn't feasible.
> With 4.0 it's mostly warning about things which are at least
> conceivably real
> under certain lighting conditions.
> Never bet against the cheap plastic solution.
More information about the buildroot