public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego Elio Pettenò" <flameeyes@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: GCC 4.6.0
Date: Wed, 06 Apr 2011 03:37:55 +0200	[thread overview]
Message-ID: <1302053875.2330.83.camel@raven.home.flameeyes.eu> (raw)
In-Reply-To: <20110402221112.2101b4c1@gentoo.org>

Il giorno sab, 02/04/2011 alle 22.11 -0600, Ryan Hill ha scritto:
> Common errors:

I've been running my tinderbox with GCC 4.6 now, so I hope to help out
discovering the issue asap, but in the mean time I'd like to point out
that GCC 4.6 (a little more than others, afaict) could cause ./configure
scripts to fail (or misdetect availability of functions).

If something does not seem to build right, but doesn't appear directly
related to GCC 4.6, make sure to attach the config.log of the configure
execution.

In particular, since with GCC 4.5 (and modern glibc) doing things such
as

write(fd, buf, bufsize);

would have caused "return value ignored" warnings, which would have
thrown off detections using -Werror, they were rewritten as

int n = write(fd, buf, bufsize);

... too bad that this *now* causes the "unused but set" warning.

-- 
Diego Elio Pettenò — Flameeyes
http://blog.flameeyes.eu/




      parent reply	other threads:[~2011-04-06  1:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-03  4:11 [gentoo-dev] GCC 4.6.0 Ryan Hill
2011-04-03  5:50 ` [gentoo-dev] " Duncan
2011-04-03 10:19   ` Ryan Hill
2011-04-03 14:04     ` Mike Frysinger
2011-04-03 16:31       ` Branko Badrljica
2011-04-03 17:29         ` Chí-Thanh Christopher Nguyễn
2011-04-03 14:56 ` [gentoo-dev] " Andreas K. Huettel
2011-04-03 17:31   ` Mike Frysinger
2011-04-06  1:37 ` Diego Elio Pettenò [this message]

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=1302053875.2330.83.camel@raven.home.flameeyes.eu \
    --to=flameeyes@gmail.com \
    --cc=gentoo-dev@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox