Has anyone had any luck completing a "make modules_install" of the 2.6.14 linux kernel on a gcc3.3 sytstem? I've tried two systems, one an FC2 and one an FC3, and both fail with the following error message:
if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F System.map 2.6.14; fi make: *** [_modinst_post] Error 137
Running the commnad "/sbin/depmod -ae -F System.map 2.6.14" from the cli results in a "Killed" message.
I'm running with the depmod contained in the package: module-init-tools-3.1-0.pre5.3 I havent found a good definition for Error 137 and google results imply it means "Value not recognized."
The make modules_install works just fine on an FC4 system (with gcc4).
Bill
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
Bill Rees wrote:
Has anyone had any luck completing a "make modules_install" of the 2.6.14 linux kernel on a gcc3.3 sytstem? I've tried two systems, one an FC2 and one an FC3, and both fail with the following error message:
if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F System.map 2.6.14; fi make: *** [_modinst_post] Error 137
Running the commnad "/sbin/depmod -ae -F System.map 2.6.14" from the cli results in a "Killed" message.
I'm running with the depmod contained in the package: module-init-tools-3.1-0.pre5.3 I havent found a good definition for Error 137 and google results imply it means "Value not recognized."
The make modules_install works just fine on an FC4 system (with gcc4).
Bill
Bill,
The problem goes deeper than that. Please read the documentation about the kernel and you will see that you need to update much of the underlying operating system before you can use the new kernel. It is not related to gcc4 vs gcc3.3 or even gcc3.2
- From Changes document:
Current Minimal Requirements
Upgrade to at *least* these software revisions before thinking you've encountered a bug! If you're unsure what version you're currently running, the suggested command should tell you.
Again, keep in mind that this list assumes you are already functionally running a Linux 2.4 kernel. Also, not all tools are necessary on all systems; obviously, if you don't have any ISDN hardware, for example, you probably needn't concern yourself with isdn4k-utils.
o Gnu C 2.95.3 # gcc --version o Gnu make 3.79.1 # make --version o binutils 2.12 # ld -v o util-linux 2.10o # fdformat --version o module-init-tools 0.9.10 # depmod -V o e2fsprogs 1.29 # tune2fs o jfsutils 1.1.3 # fsck.jfs -V o reiserfsprogs 3.6.3 # reiserfsck -V 2>&1|grep reiserfsprogs o xfsprogs 2.6.0 # xfs_db -V o pcmciautils 004 o pcmcia-cs 3.1.21 # cardmgr -V o quota-tools 3.09 # quota -V o PPP 2.4.0 # pppd --version o isdn4k-utils 3.1pre1 # isdnctrl 2>&1|grep version o nfs-utils 1.0.5 # showmount --version o procps 3.2.0 # ps --version o oprofile 0.9 # oprofiled --version o udev 058 # udevinfo -V
Good Luck, James Kosin
James Kosin wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
Bill Rees wrote:
Has anyone had any luck completing a "make modules_install" of the 2.6.14 linux kernel on a gcc3.3 sytstem? I've tried two systems, one an FC2 and one an FC3, and both fail with the following error message:
if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F System.map 2.6.14; fi make: *** [_modinst_post] Error 137
Running the commnad "/sbin/depmod -ae -F System.map 2.6.14" from the cli results in a "Killed" message.
I'm running with the depmod contained in the package: module-init-tools-3.1-0.pre5.3 I havent found a good definition for Error 137 and google results imply it means "Value not recognized."
The make modules_install works just fine on an FC4 system (with gcc4).
Bill
Bill,
The problem goes deeper than that. Please read the documentation about the kernel and you will see that you need to update much of the underlying operating system before you can use the new kernel. It is not related to gcc4 vs gcc3.3 or even gcc3.2
- From Changes document:
Current Minimal Requirements
Upgrade to at *least* these software revisions before thinking you've encountered a bug! If you're unsure what version you're currently running, the suggested command should tell you.
Again, keep in mind that this list assumes you are already functionally running a Linux 2.4 kernel. Also, not all tools are necessary on all systems; obviously, if you don't have any ISDN hardware, for example, you probably needn't concern yourself with isdn4k-utils.
o Gnu C 2.95.3 # gcc --version o Gnu make 3.79.1 # make --version o binutils 2.12 # ld -v o util-linux 2.10o # fdformat --version o module-init-tools 0.9.10 # depmod -V o e2fsprogs 1.29 # tune2fs o jfsutils 1.1.3 # fsck.jfs -V o reiserfsprogs 3.6.3 # reiserfsck -V 2>&1|grep reiserfsprogs o xfsprogs 2.6.0 # xfs_db -V o pcmciautils 004 o pcmcia-cs 3.1.21 # cardmgr -V o quota-tools 3.09 # quota -V o PPP 2.4.0 # pppd --version o isdn4k-utils 3.1pre1 # isdnctrl 2>&1|grep version o nfs-utils 1.0.5 # showmount --version o procps 3.2.0 # ps --version o oprofile 0.9 # oprofiled --version o udev 058 # udevinfo -V
Good Luck, James Kosin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD4DBQFDZ3ilkNLDmnu1kSkRA8ncAJdkbgNFqHg0s2QQhLruRw13DgVSAJ96fkqX qQMk5NchGoKncTH/vabjYw== =7EX1 -----END PGP SIGNATURE-----
Thanks for the help guys, the adventure begins.
bill