From: Richard Reich <rreich@rdrtech.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] System built with gcc 3.0.3
Date: 20 Jan 2002 21:55:48 -0500 [thread overview]
Message-ID: <1011581748.21442.16.camel@loki.rdrtech.net> (raw)
I'm building my system with gcc 3.0.3. I've got most packages compiled
but I've run into a few with problems...
First BitchX won't compile by default, I had to do a dirty hack to fix
it. While it was compiling I had to edit
/var/tmp/portage/bitchx-1.0.18-r4/work/BitchX/source/modules.c and
comment out the line extern unsigned <somthing> bitchx_<somthing>ver.
The reason is there is a duplicate decleration in irc.h. Sorry I cannot
supply the <something> because the file has been deleted after a
sucessfull merge.
Next is glibc, aparently there is some check and it won't compile under
gcc 3.0.3 only 2.95 here is the exact message I get...
*** This version of GNU libc cannot be compiled by GCC 3.x.
*** GCC 3.x will generate a library that is binary incompatible to
*** older and future releases of GNU libc.
*** You should compile this GNU libc release by an older GCC version
*** or wait for the next GNU libc release.
*** If you really mean to use GCC 3.x, run configure again
*** using the extra parameter `--disable-sanity-checks'.
!!! ERROR: The ebuild did not complete successfully.
!!! Function src_compile, Line 15, Exitcode 1
!!! (no error message)
!!! emerge aborting on
/usr/portage/sys-libs/glibc/glibc-2.2.4-r9.ebuild .
Now, I've tried the --disable-sanity-checks but emerge gives me an
error...
loki portage # emerge sys-libs/glibc/ --disable-sanity-checks
!!! Error: --disable-sanity-checks is an invalid option.
Any ideas on how to fix this?
Now I haven't rebooted my machine yet, for some reason su doesn't work
either, for normal users that is, root just ignores the errors. Here is
the specific error...
sh-2.05a$ su
su: Module is unknown
Sorry.
sh-2.05a$
Here is a list of the other modules that did not compile...
/usr/portage/app-admin/fam-oss/fam-oss-2.6.4-r1.ebuild
/usr/portage/kde-base/kdelibs/kdelibs-2.2.2-r2.ebuild
/usr/portage/sys-libs/glibc/glibc-2.2.4-r9.ebuild
/usr/portage/sys-libs/ncurses/ncurses-5.2-r3.ebuild
/usr/portage/dev-libs/pilot-link/pilot-link-0.9.6-r3.ebuild
/usr/portage/net-misc/netkit-telnetd/netkit-telnetd-0.17-r1.ebuild
Some of the packages that did build are...
X, gnome, evolution, xchat, mozilla, galeon... There are others but I
won't list them here. I have logs of all my building if anybody wants
them. Also I'm going to keep this setup if I can even limp through it.
I use gcc 3.0.3 as my development compiler, and I'd like to use gentoo
as my primary test platform. So I'd be willing to act as a tester for
the 3.0.3 compiler.
DISCLAIMER: I do know that 3.0.3 is not supported by the gentoo team,
this is something that I undertook on my own. There were too reasons,
1. I'm sick and twisted when it comes to *NEEDING* the beeding edge
2. I use 3.0.3 as my compiler.
If any of this helps great! If not and I'm being a nusance tell me to go
away and I'll go sit in the corner with my gcc 3.0.3 ;)
Rick
next reply other threads:[~2002-01-21 2:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 2:55 Richard Reich [this message]
2002-01-21 4:12 ` [gentoo-dev] System built with gcc 3.0.3 Richard Reich
2002-01-21 11:57 ` Chad M. Huneycutt
2002-01-21 11:51 ` Joachim Blaabjerg
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=1011581748.21442.16.camel@loki.rdrtech.net \
--to=rreich@rdrtech.com \
--cc=gentoo-dev@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