| 1 |
I'm building my system with gcc 3.0.3. I've got most packages compiled |
| 2 |
but I've run into a few with problems... |
| 3 |
|
| 4 |
First BitchX won't compile by default, I had to do a dirty hack to fix |
| 5 |
it. While it was compiling I had to edit |
| 6 |
/var/tmp/portage/bitchx-1.0.18-r4/work/BitchX/source/modules.c and |
| 7 |
comment out the line extern unsigned <somthing> bitchx_<somthing>ver. |
| 8 |
The reason is there is a duplicate decleration in irc.h. Sorry I cannot |
| 9 |
supply the <something> because the file has been deleted after a |
| 10 |
sucessfull merge. |
| 11 |
|
| 12 |
Next is glibc, aparently there is some check and it won't compile under |
| 13 |
gcc 3.0.3 only 2.95 here is the exact message I get... |
| 14 |
|
| 15 |
*** This version of GNU libc cannot be compiled by GCC 3.x. |
| 16 |
*** GCC 3.x will generate a library that is binary incompatible to |
| 17 |
*** older and future releases of GNU libc. |
| 18 |
*** You should compile this GNU libc release by an older GCC version |
| 19 |
*** or wait for the next GNU libc release. |
| 20 |
*** If you really mean to use GCC 3.x, run configure again |
| 21 |
*** using the extra parameter `--disable-sanity-checks'. |
| 22 |
|
| 23 |
!!! ERROR: The ebuild did not complete successfully. |
| 24 |
!!! Function src_compile, Line 15, Exitcode 1 |
| 25 |
!!! (no error message) |
| 26 |
|
| 27 |
!!! emerge aborting on |
| 28 |
/usr/portage/sys-libs/glibc/glibc-2.2.4-r9.ebuild . |
| 29 |
|
| 30 |
Now, I've tried the --disable-sanity-checks but emerge gives me an |
| 31 |
error... |
| 32 |
loki portage # emerge sys-libs/glibc/ --disable-sanity-checks |
| 33 |
!!! Error: --disable-sanity-checks is an invalid option. |
| 34 |
|
| 35 |
|
| 36 |
Any ideas on how to fix this? |
| 37 |
|
| 38 |
Now I haven't rebooted my machine yet, for some reason su doesn't work |
| 39 |
either, for normal users that is, root just ignores the errors. Here is |
| 40 |
the specific error... |
| 41 |
sh-2.05a$ su |
| 42 |
su: Module is unknown |
| 43 |
Sorry. |
| 44 |
sh-2.05a$ |
| 45 |
|
| 46 |
|
| 47 |
Here is a list of the other modules that did not compile... |
| 48 |
/usr/portage/app-admin/fam-oss/fam-oss-2.6.4-r1.ebuild |
| 49 |
/usr/portage/kde-base/kdelibs/kdelibs-2.2.2-r2.ebuild |
| 50 |
/usr/portage/sys-libs/glibc/glibc-2.2.4-r9.ebuild |
| 51 |
/usr/portage/sys-libs/ncurses/ncurses-5.2-r3.ebuild |
| 52 |
/usr/portage/dev-libs/pilot-link/pilot-link-0.9.6-r3.ebuild |
| 53 |
/usr/portage/net-misc/netkit-telnetd/netkit-telnetd-0.17-r1.ebuild |
| 54 |
|
| 55 |
|
| 56 |
Some of the packages that did build are... |
| 57 |
X, gnome, evolution, xchat, mozilla, galeon... There are others but I |
| 58 |
won't list them here. I have logs of all my building if anybody wants |
| 59 |
them. Also I'm going to keep this setup if I can even limp through it. |
| 60 |
I use gcc 3.0.3 as my development compiler, and I'd like to use gentoo |
| 61 |
as my primary test platform. So I'd be willing to act as a tester for |
| 62 |
the 3.0.3 compiler. |
| 63 |
|
| 64 |
DISCLAIMER: I do know that 3.0.3 is not supported by the gentoo team, |
| 65 |
this is something that I undertook on my own. There were too reasons, |
| 66 |
1. I'm sick and twisted when it comes to *NEEDING* the beeding edge |
| 67 |
2. I use 3.0.3 as my compiler. |
| 68 |
|
| 69 |
If any of this helps great! If not and I'm being a nusance tell me to go |
| 70 |
away and I'll go sit in the corner with my gcc 3.0.3 ;) |
| 71 |
|
| 72 |
Rick |
Archives