| 1 |
On Tuesday 24 December 2002 08:59 am, Johannes Findeisen wrote: |
| 2 |
> short again: i can compile in my gcc 2.95.3 system and in the chrooted |
| 3 |
> gcc 3.2.1 but only when i'm chrooting from my gcc 2.95.3 system. i |
| 4 |
> defenitly could not compile when the gcc 3.2.* system is runing. |
| 5 |
|
| 6 |
If you can compile when chrooting from 2.95.3 to the 3.2.1 system, but not |
| 7 |
when booting directly into the 3.2.1 system, my guess is that you have a |
| 8 |
kernel problem. |
| 9 |
|
| 10 |
Theoretically, the only effective difference between the chroot environment |
| 11 |
and the directly booted environment is whether a 2.95.3 compiled or a 3.2.1 |
| 12 |
compiled kernel is running. |
| 13 |
|
| 14 |
Consider adding a new boot menu option which boots the gcc 3.2.1 system using |
| 15 |
the kernel from the 2.95.3 system. If you don't have problems with this, your |
| 16 |
3.2.1 system has a bad kernel. |
| 17 |
|
| 18 |
WHY that kernel would be bad is a pretty open question. It probably has |
| 19 |
nothing to do with it being compiled with the newer gcc; perhaps the |
| 20 |
configuration is somehow wrong? Or perhaps Gentoo has started using newer |
| 21 |
kernel versions with slightly different binary interfaces, and you need to |
| 22 |
compile libc against the new kernel so that it uses the new binary interface. |
| 23 |
|
| 24 |
Good luck, in any case. |
| 25 |
|
| 26 |
Evan Powers |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
gentoo-dev@g.o mailing list |
Archives