Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have been for the past couple days attempting to put together a 64 bit kernel on my computer but keep on getting the following error message
CC scripts/mod/empty.o
cc1: error: code model `kernel' not supported in the 32 bit mode
make[2]: *** [scripts/mod/empty.o] Error 1
make[1]: *** [scripts/mod] Error 2
make: *** [scripts] Error 2
anybody seen this before? below is my system information
Same message here on AMD Athlon 64 (dual core), booting with kernel 2.6.15-21.amd64-generic from kubuntu and trying to recompile that same kernel from source, using gcc-4.0.1.
Did anyone find how to solve the error from -mcmodel=kernel meanwhile?
Looks like I can compile that kernel on a good old x86 machine with the same options, but that's a bit of a workaround...
you won't be able to produce a 64 bit kernel unless the compile tools are already designed to output 64bit programs.
either rebuild the compile tools, configuring them for 64 bit system, then use them to compile the kernel, or download a 64bit live cd, and compile from it.
you won't be able to produce a 64 bit kernel unless the compile tools are already designed to output 64bit programs.
either rebuild the compile tools, configuring them for 64 bit system, then use them to compile the kernel, or download a 64bit live cd, and compile from it.
Would having tools capable of 64-bit compiles, prevent proper operation on 32-bit systems? If you rebuild the compile tools for a 64-bit system, can you still build 32-bit packages without trouble?
It seems I have a few alternatives to select from.
1. I can install a full 64-bit system with all of it's libraries included.
xx: This is just too easy!
2. I can keep my 64-bit kernel and recompile gcc to build 64-bit packages.
xx: This is more of a challenge.
But now, if I choose the second option and rebuild gcc, I need to know something here. I know that I can compile gcc with the ability to create a 64-bit kernel (and likely other packages as well). But I want to know is:
1. Should the gcc package be compiled as a native 32-bit (i686) binary, defaulting to 32-bit builds with the option of 64-bit builds (using "gcc -m64")?
2. Could the gcc package be compiled in 64-bit (x86_64) format (on my 32-bit system), with the option of building 32-bit packages?
a): Is that even possible?
b): Would I need a 64-bit glibc for a 64-bit gcc to be usable on my system? Meaning that I would be required to wind up with a complete 64-bit system.
3. Is there a way to build a 64-bit version of gcc which defaults to 32-bit builds, requiring that gcc -m64 be declared for 64-bit builds?
1. I can install a full 64-bit system with all of it's libraries included.
xx: This is just too easy!
Why don't you want easy? What are you actually trying to accomplish?
Quote:
2. I can keep my 64-bit kernel
You have a 64bit kernel now? Or that was a typo?
Quote:
1. Should the gcc package be compiled as a native 32-bit (i686) binary, defaulting to 32-bit builds with the option of 64-bit builds (using "gcc -m64")?
Sounds reasonable. But what are you actually trying to accomplish?
Quote:
2. Could the gcc package be compiled in 64-bit (x86_64) format (on my 32-bit system), with the option of building 32-bit packages?
Then how would you use it? You can compile a 64-bit native gcc on a 32 bot system, but you couldn't run it there.
Quote:
3. Is there a way to build a 64-bit version of gcc which defaults to 32-bit builds, requiring that gcc -m64 be declared for 64-bit builds?
I'm sure it can be done. I don't know how. If you look at the options for making a gcc cross compiler, you should be able to find what you need.
Why don't you want easy? What are you actually trying to accomplish?
Quote:
I need to compile 64-bit kernel modules for my system.
You have a 64bit kernel now? Or that was a typo?
Quote:
Yes! I have a 64-bit Slamd64 kernel now.
Sounds reasonable. But what are you actually trying to accomplish?
Quote:
The topic is compiling 64-bit kernels on a 32-bit system. I have 8 GBs of memory on this system. So I'm using a kernel that supports it. I choose not to use PAE, because it was stated that a 64-bit kernel is more efficient, especially on a 64-bit processor.
Then how would you use it? You can compile a 64-bit native gcc on a 32 bot system, but you couldn't run it there.
Quote:
Yeah. I realize that now.
I'm sure it can be done. I don't know how. If you look at the options for making a gcc cross compiler, you should be able to find what you need.
I think I'm going to settle on recompiling the present compiler to allow 64-bit compiles. I don't want to run 64-bit applications. So that's not a problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.