[gentoo-dev] System built with gcc 3.0.3

[gentoo-dev] System built with gcc 3.0.3

[Richard Reich]

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

Re: [gentoo-dev] System built with gcc 3.0.3

[Richard Reich]

I rebooted now, and I cannot log into the system,  It says invalid login
with any userid that I enter.  I've go the latest shadow package.  Is
there anything else that I need?

Rick

P.S.
Remember I'm the guy who rebuilt his system with gcc 3.0.3.

On Sun, 2002-01-20 at 21:55, Richard Reich wrote:
> 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
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
> 

Re: [gentoo-dev] System built with gcc 3.0.3

[Chad M. Huneycutt]

On 20 Jan 2002, Richard Reich wrote:

> I rebooted now, and I cannot log into the system,  It says invalid login
> with any userid that I enter.  I've go the latest shadow package.  Is
> there anything else that I need?
> > 
> > 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$ 

These two problems are related.  You need to emerge sys-apps/shadow after
emerging system.  This is not in the install docs b/c it is a bug.

You probably need to reboot from the CD, do the chroot, and emerge
shadow.  Then you should be able to set the password and reboot and login.

--
Chad Huneycutt
Ph.D. Student
Georgia Tech College of Computing
http://www.cc.gatech.edu/~chadh

Re: [gentoo-dev] System built with gcc 3.0.3

[Joachim Blaabjerg]

On 20 Jan 2002 21:55:48 -0500
Richard Reich <rreich@rdrtech.com> wrote:
<snip>
> 
> 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.

I think you should change the .ebuild file and put the --disable-sanity-checks
flag in the ./configure stage.

> 
> 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$ 

I guess you use PAM, how does your /etc/pam.d/su file look? Does it even exist?

<snip>

Regards

-- 
Joachim Blaabjerg
styx@SuxOS.org
www.SuxOS.org