All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: buildroot@busybox.net
Subject: [Buildroot] make troubles
Date: Fri, 4 Aug 2006 14:18:16 -0400	[thread overview]
Message-ID: <200608041418.16879.rob@landley.net> (raw)
In-Reply-To: <94AB2BC3-0641-400D-9544-89338AD41BE9@cs.auckland.ac.nz>

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
> 
> BR_PACKAGE_BUSYBOX_SNAPSHOT
> 
> 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 thinking 
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 compiler 
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.

Rob
-- 
Never bet against the cheap plastic solution.

  reply	other threads:[~2006-08-04 18:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03  6:00 [Buildroot] make troubles Robert Carter
2006-08-03 20:39 ` Rob Landley
2006-08-04  0:36   ` Robert Carter
2006-08-04 18:18     ` Rob Landley [this message]
2006-08-06 22:03       ` Robert Carter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200608041418.16879.rob@landley.net \
    --to=rob@landley.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.