64-bit nonsense

malloc · 01-03-2012, 02:35 AM

I have one laptop and one desktop which both run Slackware 13.37, 64-bit. On both I have used the Alien's approach to get multilib functionality (http://alien.slackbook.org/dokuwiki/...kware:multilib).

There should be no difference between these systems, yet on the desktop I get this when I try to compile the 3.1.6 kernel:

Code:

  CHK     include/linux/version.h
  CHK     include/generated/utsrelease.h
  UPD     include/generated/utsrelease.h
  CC      kernel/bounds.s
kernel/bounds.c:1:0: error: code model 'kernel' not supported in the 32 bit mode
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2

Whereas on the laptop I get no such error.

Why is this?

NoStressHQ · 01-03-2012, 03:58 AM

Have your tried:

Code:

 $ make ARCH=ia64 [...]

??

Edit: well more precisely, which target are you trying to compile (32/64) ? And then are you sure you didn't set the "32bit" compiling environment on one of your systems (.bashrc or /etc/profile.d/... ) ?

Cedrik · 01-03-2012, 05:14 AM

Quote:

Compiling 32-bit programs

In case you need to compile a 32-bit program (wine and grub are two examples of open source programs that are 32-bit only) you first configure your shell environment by running the command:

. /etc/profile.d/32dev.sh

http://alien.slackbook.org/dokuwiki/...kware:multilib

Maybe your /etc/profile.d/32dev.sh file is executable and sourced automatically each time you start a new shell ?

NoStressHQ · 01-03-2012, 05:46 AM

Quote:

Originally Posted by Cedrik

Maybe your /etc/profile.d/32dev.sh file is executable and sourced automatically each time you start a new shell ?

Hell well, I suspect something like this, and didn't encountered that problem, but reading your post I realize that /etc/profile.d might not be a clever (*) place for this file... At least to prevent problems like this, but more generally because it's not very coherent with the purpose of /etc/profile.d. Am I wrong ?

Cheers.

Garry.

(*) No offence AlienBob, I don't criticize your job, just raising a flag.

Edit: BTW, to the OP: You might want to specify 64bit/multilib in your title, as it is NOT a 64bit problem but more a multilib one... Or it seems to be.