From: Andrew Gaydenko <a@gaydenko.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] gcc, two problems
Date: Fri, 16 Jan 2009 10:14:29 +0300 [thread overview]
Message-ID: <200901161014.30094.a@gaydenko.com> (raw)
Hi!
I use ~amd64.
1. Just after synching I have:
emerge -pvDuN world
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] sys-devel/gcc-4.2.4-r1 [4.2.4] USE="fortran gcj mudflap
(multilib) nls openmp (-altivec) -bootstrap -build -doc -gtk (-hardened) -ip28
-ip32r10k -libffi -multislot (-n32) (-n64) -nocxx -objc -objc++ -objc-gc -test
-vanilla" 0 kB
The building ends with strange errors:
/wrk/tmp/portage/portage/sys-devel/gcc-4.2.4-
r1/work/gcc-4.2.4/gcc/config/i386/crtfastmath.c:1: error: bad value (core2)
for -march= switch
/wrk/tmp/portage/portage/sys-devel/gcc-4.2.4-
r1/work/gcc-4.2.4/gcc/config/i386/crtfastmath.c:1: error: bad value (core2)
for -mtune= switch
make[3]: *** [crtfastmath.o] Error 1
Have not found appropriate bug (don't believe I'm the first in upgrading :-)).
Thoughts?
2. Here http://packages.gentoo.org/package/sys-devel/gcc gcc-4.3.2 exists for
~amd64 and is unmasked. Why 'emerge -pvDuN world' does not see new gcc
version?
next reply other threads:[~2009-01-16 7:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 7:14 Andrew Gaydenko [this message]
2009-01-16 7:51 ` [gentoo-user] gcc, two problems Paul Hartman
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=200901161014.30094.a@gaydenko.com \
--to=a@gaydenko.com \
--cc=gentoo-user@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