From: Jack Lloyd <lloyd@randombit.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Building vanilla gcc fails, any ideas?
Date: Wed, 6 Feb 2008 09:42:47 -0500 [thread overview]
Message-ID: <20080206144246.GE8236@randombit.net> (raw)
Trying to build a gcc 4.3 snapshot (20080125) fails on my x86-64
box. While building libstdc++, I see many problems with various libc
functions not being found, for instance
gcc-4.3-20080125-build/x86_64-unknown-linux-gnu/libstdc++-v3/include/cstdio:140: error: '::ungetc' has not been declared
I assume this has something to do with Gentoo's multilib header setup
but I'm not sure what extra paths I should be configuring the build to
search for. This snapshot is supposed to be stable (4.3 is in stage3
currently and from the reports on the mailing list is building well on
other platforms). Currently I'm configuring with
../gcc-4.3-20080125/configure --enable-languages=c,c++,objc,obj-c++ --prefix=/usr/local/gcc-4.3-20080125 --program-suffix=-4.3-20080125
Any hints?
Jack
--
gentoo-amd64@lists.gentoo.org mailing list
next reply other threads:[~2008-02-06 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 14:42 Jack Lloyd [this message]
2008-02-06 17:30 ` [gentoo-amd64] Re: Building vanilla gcc fails, any ideas? Duncan
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=20080206144246.GE8236@randombit.net \
--to=lloyd@randombit.net \
--cc=gentoo-amd64@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