| 1 |
On 20 Jan 2002 21:55:48 -0500 |
| 2 |
Richard Reich <rreich@×××××××.com> wrote: |
| 3 |
<snip> |
| 4 |
> |
| 5 |
> Next is glibc, aparently there is some check and it won't compile under |
| 6 |
> gcc 3.0.3 only 2.95 here is the exact message I get... |
| 7 |
> |
| 8 |
> *** This version of GNU libc cannot be compiled by GCC 3.x. |
| 9 |
> *** GCC 3.x will generate a library that is binary incompatible to |
| 10 |
> *** older and future releases of GNU libc. |
| 11 |
> *** You should compile this GNU libc release by an older GCC version |
| 12 |
> *** or wait for the next GNU libc release. |
| 13 |
> *** If you really mean to use GCC 3.x, run configure again |
| 14 |
> *** using the extra parameter `--disable-sanity-checks'. |
| 15 |
> |
| 16 |
> !!! ERROR: The ebuild did not complete successfully. |
| 17 |
> !!! Function src_compile, Line 15, Exitcode 1 |
| 18 |
> !!! (no error message) |
| 19 |
> |
| 20 |
> !!! emerge aborting on |
| 21 |
> /usr/portage/sys-libs/glibc/glibc-2.2.4-r9.ebuild . |
| 22 |
> |
| 23 |
> Now, I've tried the --disable-sanity-checks but emerge gives me an |
| 24 |
> error... |
| 25 |
> loki portage # emerge sys-libs/glibc/ --disable-sanity-checks |
| 26 |
> !!! Error: --disable-sanity-checks is an invalid option. |
| 27 |
|
| 28 |
I think you should change the .ebuild file and put the --disable-sanity-checks |
| 29 |
flag in the ./configure stage. |
| 30 |
|
| 31 |
> |
| 32 |
> Any ideas on how to fix this? |
| 33 |
> |
| 34 |
> Now I haven't rebooted my machine yet, for some reason su doesn't work |
| 35 |
> either, for normal users that is, root just ignores the errors. Here is |
| 36 |
> the specific error... |
| 37 |
> sh-2.05a$ su |
| 38 |
> su: Module is unknown |
| 39 |
> Sorry. |
| 40 |
> sh-2.05a$ |
| 41 |
|
| 42 |
I guess you use PAM, how does your /etc/pam.d/su file look? Does it even exist? |
| 43 |
|
| 44 |
<snip> |
| 45 |
|
| 46 |
Regards |
| 47 |
|
| 48 |
-- |
| 49 |
Joachim Blaabjerg |
| 50 |
styx@×××××.org |
| 51 |
www.SuxOS.org |
Archives