8 Dec
2005
8 Dec
'05
1:45 p.m.
Hello,
All I am trying to do is compile an x86_64 kernel on i386 machine. It
dos not work:
$ ARCH=x86_64 make oldconfig
<no errors>
$ ARCH=x86_64 make
CHK include/linux/version.h
SPLIT include/linux/autoconf.h -> include/config/*
CC arch/x86_64/kernel/asm-offsets.s
arch/x86_64/kernel/asm-offsets.c:1: error: code model 'kernel' not
supported in the 32 bit mode
make[1]: *** [arch/x86_64/kernel/asm-offsets.s] Error 1
make: *** [prepare0] Error 2
What gives? Do I need a different compiler to build for x86_64?
Shouldn't this Just Work?
Lee
8 Dec
8 Dec
2:48 p.m.
* Lee Revell <rlrevell(a)joe-job.com> wrote:
All I am trying to do is compile an x86_64 kernel on
i386 machine. It
dos not work:
$ ARCH=x86_64 make oldconfig
<no errors>
$ ARCH=x86_64 make
[...]
What gives? Do I need a different compiler to build
for x86_64?
Yes.
Cross compiling the kernel works like this:
$ make ARCH=<arch> CROSS_COMPILE=<arch-prefix>
The gcc cross compiler for x86_64 is usually named x86_64-linux-gcc.
In the special case of x86 -> x86_64 a 64 bit enabled gcc is sufficient
though (if your binutils support 64 bit). In all other cases you need
a "real" cross compiler.
Kai
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden:
http://mail.yahoo.de
3:29 p.m.
On Thu, 2005-12-08 at 20:48 +0100, Kai Ruemmler wrote:
* Lee Revell <rlrevell(a)joe-job.com> wrote:
Can you tell me which Ubuntu/Debian packages to install to make this
work? I did "apt-cache search | grep 64" and did not see any GCC or
binutils packages.
The closest thing I saw was lib64gcc1 which I'm installing now.
Lee
All I am trying to do is compile an x86_64 kernel
on i386 machine. It
dos not work:
$ ARCH=x86_64 make oldconfig
<no errors>
$ ARCH=x86_64 make
[...]
What gives? Do I need a different compiler to
build for x86_64?
Yes.
Cross compiling the kernel works like this:
$ make ARCH=<arch> CROSS_COMPILE=<arch-prefix>
The gcc cross compiler for x86_64 is usually named x86_64-linux-gcc.
In the special case of x86 -> x86_64 a 64 bit enabled gcc is sufficient
though (if your binutils support 64 bit). In all other cases you need
a "real" cross compiler.
4:31 p.m.
On Thu, 2005-12-08 at 20:48 +0100, Kai Ruemmler wrote:
* Lee Revell <rlrevell(a)joe-job.com> wrote:
Does not work. I installed binutils-multiarch and lib64gcc1 but I still
get the exact same error:
$ make ARCH=x86_64 CROSS_COMPILE=x86_64-linux-
make: x86_64-linux-gcc: Command not found
CHK include/linux/version.h
CC arch/x86_64/kernel/asm-offsets.s
/bin/sh: x86_64-linux-gcc: command not found
make[1]: *** [arch/x86_64/kernel/asm-offsets.s] Error 127
make: *** [prepare0] Error 2
There does not seem to be any x86_64-linux-gcc package at all for Ubuntu.
If I omit CROSS_COMPILE I get the same error as before:
$ make ARCH=x86_64
CHK include/linux/version.h
CC arch/x86_64/kernel/asm-offsets.s
arch/x86_64/kernel/asm-offsets.c:1: error: code model 'kernel' not supported in
the 32 bit mode
make[1]: *** [arch/x86_64/kernel/asm-offsets.s] Error 1
make: *** [prepare0] Error 2
Why does GCC insist on running in "the 32 bit mode" even though I told
it ARCH is x86-64?
Why doesn't this Just Work, is Ubuntu really such a piece of shit that
there's no easy way to do it?
Lee
All I am trying to do is compile an x86_64 kernel
on i386 machine. It
dos not work:
$ ARCH=x86_64 make oldconfig
<no errors>
$ ARCH=x86_64 make
[...]
What gives? Do I need a different compiler to
build for x86_64?
Yes.
Cross compiling the kernel works like this:
$ make ARCH=<arch> CROSS_COMPILE=<arch-prefix>
The gcc cross compiler for x86_64 is usually named x86_64-linux-gcc.
In the special case of x86 -> x86_64 a 64 bit enabled gcc is sufficient
though (if your binutils support 64 bit). In all other cases you need
a "real" cross compiler.
4:42 p.m.
Why does GCC insist on running in "the 32 bit
mode" even though I told> it ARCH is x86-64?>> Why doesn't this Just
Work, is Ubuntu really such a piece of shit that> there's no easy way to do it?
My experince with all the embedded processors I deal with is thatcross compiling
almost never "just works". You might try gettingcrosstool and building a 64bit
toolchain. That will take a hour or 2though. Unless you have a screaming machine.
--Richard A. Smith
4:56 p.m.
On Thu, 2005-12-08 at 15:42 -0600, Richard Smith wrote:
Ugh, there's no way to do this by just installing packages? x86-64
isn't some bizarre embedded arch, it must be the #1 or #2 selling PC
processor today. I can't believe there's no easy way to do it. This is
bullshit.
Lee
Why does GCC
insist on running in "the 32 bit mode" even though I told> it ARCH is
x86-64?>> Why doesn't this Just Work, is Ubuntu really such a piece of shit
that> there's no easy way to do it?
My experince with all the embedded
processors I deal with is thatcross compiling almost never "just works". You
might try gettingcrosstool and building a 64bit toolchain. That will take a hour or
2though. Unless you have a screaming machine.
--Richard A. Smith
5:04 p.m.
On Thu, 2005-12-08 at 15:42 -0600, Richard Smith wrote:
OK, brilliant. Apparently the only way to do this is to install the
"toolchain-source" package and, yep, BUILD A TOOLCHAIN FROM SOURCE.
http://www.gelato.unsw.edu.au/IA64wiki/CrossCompilation
Christ, I cannot believe what a pain in the ass this is. At this rate
it will have taken me 2 days to get this working.
Lee
Why does GCC
insist on running in "the 32 bit mode" even though I told> it ARCH is
x86-64?>> Why doesn't this Just Work, is Ubuntu really such a piece of shit
that> there's no easy way to do it?
My experince with all the embedded
processors I deal with is thatcross compiling almost never "just works". You
might try gettingcrosstool and building a 64bit toolchain. That will take a hour or
2though. Unless you have a screaming machine.
--Richard A. Smith
5:13 p.m.
Ugh, there's no way to do this by just installing
packages? x86-64> isn't some bizarre embedded arch, it must be the #1 or #2
selling PC> processor today. I can't believe there's no easy way to do it.
This is> bullshit.
Google seems to suggest that 32->64 is a compile option.
http://lists.freebsd.org/pipermail/freebsd-amd64/2004-November/002681.htmlI… for BSD but
still gcc.
Here's something that says there is a kernel-image-amd64 package thatcross compiles.
http://lists.debian.org/debian-amd64/2005/02/msg00059.html
--Richard A. Smith
5:17 p.m.
> OK, brilliant. Apparently the only way to do this
is to install the> "toolchain-source" package and, yep, BUILD A TOOLCHAIN
FROM SOURCE.>> http://www.gelato.unsw.edu.au/IA64wiki/CrossCompilation>>
Christ, I cannot believe what a pain in the ass this is. At this rate> it will have
taken me 2 days to get this working.
Yep. thats about par for the course. Perhaps
if you ask on thedebian-amd64 some kind soul has unofficial packages you can use.
--Richard A. Smith
5:19 p.m.
On Thu, 2005-12-08 at 15:54 -0600, Richard Smith wrote:
I don't have a 64 bit machine - that's the whole problem. I am trying
to reproduce a problem an x86_64 user at a remote location is having. I
have their kernel sources and .config. I expected to be able to install
a gcc-x86_64 package and be done with it. Apparently I was wrong, and
this is going to be a nightmare to get working. Grr.
Lee
cross
compiling almost never "just works". You might try getting> crosstool and
building a 64bit toolchain. That will take a hour or 2
Or perhaps try booting the
Kanotix64 livecd and compile under that?
5:20 p.m.
> Christ, I cannot believe what a pain in the ass
this is. At this rate> > it will have taken me 2 days to get this working.>>
Yep. thats about par for the course. Perhaps if you ask on the> debian-amd64 some kind
soul has unofficial packages you can use.>
Try here:
http://debian.speedblue.org/
--Richard A. Smith
5:20 p.m.
On Thu, 2005-12-08 at 15:54 -0600, Richard Smith wrote:
Would take weeks to download.
Lee
cross
compiling almost never "just works". You might try getting> crosstool and
building a 64bit toolchain. That will take a hour or 2
Or perhaps try booting the
Kanotix64 livecd and compile under that?
5:36 p.m.
On Thu, 2005-12-08 at 16:13 -0600, Richard Smith wrote:
Ubuntu does not have a kernel-image-amd64 and all combinations of -m64
and -mcpu=x86-64 in CFLAGS produce the same error.
It is as if the Ubuntu gcc (in fact all of Ubuntu) simply has no support
at all for x86-64.
Lee
Ugh,
there's no way to do this by just installing packages? x86-64> isn't some
bizarre embedded arch, it must be the #1 or #2 selling PC> processor today. I
can't believe there's no easy way to do it. This is> bullshit.
Google
seems to suggest that 32->64 is a compile option.
http://lists.freebsd.org/pipermail/freebsd-amd64/2004-November/002681.htmlI… for BSD but
still gcc.
Here's something that says there is a kernel-image-amd64 package thatcross compiles.
http://lists.debian.org/debian-amd64/2005/02/msg00059.html
5:39 p.m.
On Thu, 2005-12-08 at 16:20 -0600, Richard Smith wrote:
Thanks. Apparenly Ubuntu/Debian do not support any cross compiling
whatsoever OOTB. The only explanation I can think of is that they want
to keep the install small.
Lee
> Christ, I
cannot believe what a pain in the ass this is. At this rate> > it will have taken
me 2 days to get this working.>> Yep. thats about par for the course. Perhaps if
you ask on the> debian-amd64 some kind soul has unofficial packages you can use.>
Try here:
http://debian.speedblue.org/
5:48 p.m.
> Thanks. Apparenly Ubuntu/Debian do not support
any cross compiling> whatsoever OOTB. The only explanation I can think of is that they
want> to keep the install small.
Welcome.
Like you said its only us bizzare embeded dudes that really use thatstuff. So its not
worth the trouble. Especially when you can just geta live CD to bootstrap when you
actuall have 64bit hardware.
BTW. I found that using 'apt-get.org'. It's really helpful for stuff like
that.
--Richard A. Smith
6:17 p.m.
On Thu, 2005-12-08 at 16:20 -0600, Richard Smith wrote:
Thanks, it looks like this will work. Unfortunately gcc-4.0-x86-64 +
deps are an 80MB download but I guess that's better than nothing. I'm
still disgusted at having to use third party .debs to accomplish
something so utterly trivial.
FWIW I tried -m64 as described in one of the other links you sent and
got these errors.
I wonder if this is why so many x86-64 users use Gentoo despite its
apparent complexity: because the 64 bit support in other distros is
shit.
$ make CFLAGS="-m64 -mcpu=x86-64" ARCH=x86_64
CHK include/linux/version.h
CC arch/x86_64/kernel/asm-offsets.s
In file included from include/asm/system.h:5,
from include/asm/processor.h:18,
from include/asm/thread_info.h:17,
from include/linux/thread_info.h:21,
from include/linux/spinlock.h:53,
from include/linux/capability.h:45,
from include/linux/sched.h:7,
from arch/x86_64/kernel/asm-offsets.c:7:
include/linux/kernel.h:105: warning: conflicting types for built-in function
'snprintf'
include/linux/kernel.h:107: warning: conflicting types for built-in function
'vsnprintf'
In file included from include/linux/bitmap.h:8,
from include/linux/cpumask.h:82,
from include/linux/sched.h:15,
from arch/x86_64/kernel/asm-offsets.c:7:
include/linux/string.h:18: warning: conflicting types for built-in function
'strspn'
include/linux/string.h:19: warning: conflicting types for built-in function
'strcspn'
etc
Lee
> Christ, I
cannot believe what a pain in the ass this is. At this rate> > it will have taken
me 2 days to get this working.>> Yep. thats about par for the course. Perhaps if
you ask on the> debian-amd64 some kind soul has unofficial packages you can use.>
Try here:
http://debian.speedblue.org/
6:50 p.m.
Thanks, it looks like this will work. Unfortunately
gcc-4.0-x86-64 +> deps are an 80MB download but I guess that's better than nothing.
I'm> still disgusted at having to use third party .debs to accomplish>
something so utterly trivial.
This is kinda getting OT. But why do you think its
"utterly trivial?"
Also I found this on the Debian AMD64 page
---Minimalistic AMD64 runtime support for i386
The official i386 distribution actually includes minimalistic AMD64support, consisting of
a 64bit kernel, gcc-3.4 able to create 64bitbinaries and the amd64-libs package to run
third-party amd64 binarieswith native shared libraries.---
So somebody thinks Debian proper can do this. Try installing thegcc-3.4 package and see
if it works.
--Richard A. Smith
7:09 p.m.
(I apologise if anyone finds this thread OT, it is relevant to Linux
audio development and the kernel people don't want to hear about
toolchain problems)
On Thu, 2005-12-08 at 18:16 -0500, Lee Revell wrote:
On Thu, 2005-12-08 at 16:20 -0600, Richard Smith
wrote:
Try here:
http://debian.speedblue.org/
Thanks, it looks like this will work. Unfortunately gcc-4.0-x86-64 +
deps are an 80MB download but I guess that's better than nothing. I'm
still disgusted at having to use third party .debs to accomplish
something so utterly trivial.
FWIW I tried -m64 as described in one of the other links you sent and
got these errors.
Hmm, now I am getting somwhere. I had failed to run "make mrproper" so
include/asm was still symlinked to include/asm-i386. After fixing that,
I got a bit farther.
LD usr/built-in.o
ld: warning: i386 architecture of input file `usr/initramfs_data.o' is incompatible
with i386:x86-64 output
This one is worrisome, maybe I also need to pass LDFLAGS?
CC arch/x86_64/kernel/process.o
CC arch/x86_64/kernel/signal.o
AS arch/x86_64/kernel/entry.o
arch/x86_64/kernel/entry.S: Assembler messages:
arch/x86_64/kernel/entry.S:204: Error: cannot represent relocation type
BFD_RELOC_X86_64_32S
arch/x86_64/kernel/entry.S:275: Error: cannot represent relocation type
BFD_RELOC_X86_64_32S
arch/x86_64/kernel/entry.S:762: Error: cannot represent relocation type
BFD_RELOC_X86_64_32S
arch/x86_64/kernel/entry.S:815: Error: cannot represent relocation type
BFD_RELOC_X86_64_32S
arch/x86_64/kernel/entry.S:536: Error: cannot represent relocation type BFD_RELOC_64
arch/x86_64/kernel/entry.S:536: Error: cannot represent relocation type BFD_RELOC_64
arch/x86_64/kernel/entry.S:785: Error: cannot represent relocation type BFD_RELOC_64
arch/x86_64/kernel/entry.S:785: Error: cannot represent relocation type BFD_RELOC_64
make[1]: *** [arch/x86_64/kernel/entry.o] Error 1
make: *** [arch/x86_64/kernel] Error 2
Assembler problem?
So it looks like my GCC is OK but the assembler and linker still are not
happy. Any ideas?
Lee
Christ, I cannot believe what a pain in the ass this
is. At this rate
it will have taken me 2 days to get this working.
Yep. thats about par for the
course. Perhaps if you ask on the
debian-amd64 some kind soul has unofficial packages you can use.
7:23 p.m.
ld: warning: i386 architecture of input file
`usr/initramfs_data.o' is incompatible with i386:x86-64 output>> This one is
worrisome, maybe I also need to pass LDFLAGS?>> CC
arch/x86_64/kernel/process.o> CC arch/x86_64/kernel/signal.o> AS
arch/x86_64/kernel/entry.o> arch/x86_64/kernel/entry.S: Assembler messages:>
arch/x86_64/kernel/entry.S:204: Error: cannot represent relocation type
BFD_RELOC_X86_64_32S> arch/x86_64/kernel/entry.S:275: Error: cannot represent
relocation type BFD_RELOC_X86_64_32S> arch/x86_64/kernel/entry.S:762: Error: cannot
represent relocation type BFD_RELOC_X86_64_32S> arch/x86_64/kernel/entry.S:815: Error:
cannot represent relocation type BFD_RELOC_X86_64_32S> arch/x86_64/kernel/entry.S:536:
Error: cannot represent relocation type BFD_RELOC_64> arch/x86_64/kernel/entry.S:536:
Error: cannot represent relocation type BFD_RELOC_64> arch/x86_64/kernel/entry.S:785:
Error: cannot represent relocation type BFD_RELOC_64> arch/x86_64/kernel/entry.S:785:
Error: cannot represent relocation type BFD_RELOC_64> make[1]: ***
[arch/x86_64/kernel/entry.o] Error 1> make: *** [arch/x86_64/kernel] Error 2>>
Assembler problem?>> So it looks like my GCC is OK but the assembler and linker
still are not> happy. Any ideas?
Mmmmm... ick. you may need some patches...
http://sourceware.org/ml/binutils/2005-03/msg00850.htmlhttp://sources.redha…
--Richard A. Smith
7:31 p.m.
On Thu, 2005-12-08 at 19:05 -0500, Lee Revell wrote:
(I apologise if anyone finds this thread OT, it is
relevant to Linux
audio development and the kernel people don't want to hear about
toolchain problems)
Never mind, this is actually quite OT and I should take it to the
debian-amd64 list.
Thanks,
Lee
7:50 p.m.
On Thu, 2005-12-08 at 18:23 -0600, Richard Smith wrote:
Yup, my binutils changelog stops two months before that bug was fixed.
Thanks!
Lee
ld: warning:
i386 architecture of input file `usr/initramfs_data.o' is incompatible with
i386:x86-64 output>> This one is worrisome, maybe I also need to pass
LDFLAGS?>> CC arch/x86_64/kernel/process.o> CC
arch/x86_64/kernel/signal.o> AS arch/x86_64/kernel/entry.o>
arch/x86_64/kernel/entry.S: Assembler messages:> arch/x86_64/kernel/entry.S:204: Error:
cannot represent relocation type BFD_RELOC_X86_64_32S> arch/x86_64/kernel/entry.S:275:
Error: cannot represent relocation type BFD_RELOC_X86_64_32S>
arch/x86_64/kernel/entry.S:762: Error: cannot represent relocation type
BFD_RELOC_X86_64_32S> arch/x86_64/kernel/entry.S:815: Error: cannot represent
relocation type BFD_RELOC_X86_64_32S> arch/x86_64/kernel/entry.S:536: Error: cannot
represent relocation type BFD_RELOC_64> arch/x86_64/kernel/entry.S:536: Error: cannot
represent relocation type BFD_RELOC_64> arch/x86_64/kernel/entry.S:785: Error: cannot
represent relocation type BFD_RELOC_64> arch/x86_64/kerne!
l/entry.S:785: Error:
cannot represent relocation type BFD_RELOC_64> make[1]: ***
[arch/x86_64/kernel/entry.o] Error 1> make: *** [arch/x86_64/kernel] Error 2>>
Assembler problem?>> So it looks like my GCC is OK but the assembler and linker
still are not> happy. Any ideas?
Mmmmm... ick. you may need some patches...
http://sourceware.org/ml/binutils/2005-03/msg00850.htmlhttp://sources.redha…
--Richard A. Smith
7:54 p.m.
On Thu, 2005-12-08 at 19:05 -0500, Lee Revell
wrote:> > (I apologise if anyone finds this thread OT, it is relevant to Linux>
> audio development and the kernel people don't want to hear about> >
toolchain problems)>> Never mind, this is actually quite OT and I should take it to
the> debian-amd64 list.
Sorry I couldn't help you more. Cross compile to
Amd64 is not oneI've messed with yet.
--Richard A. Smith
8:05 p.m.
On Thu, 2005-12-08 at 18:54 -0600, Richard Smith wrote:
No problem, you were quite helpful, I just didn't want to bug the list
with a bunch of kernel stuff.
I guess I just assumed it would be easy because so many people have
amd64...
Lee
On Thu,
2005-12-08 at 19:05 -0500, Lee Revell wrote:> > (I apologise if anyone finds this
thread OT, it is relevant to Linux> > audio development and the kernel people
don't want to hear about> > toolchain problems)>> Never mind, this is
actually quite OT and I should take it to the> debian-amd64 list.
Sorry I
couldn't help you more. Cross compile to Amd64 is not oneI've messed with yet.
9 Dec
9 Dec
4:38 a.m.
* Lee Revell <rlrevell(a)joe-job.com> wrote:
> My experince with all the embedded processors I
deal with is
> thatcross compiling almost never "just works". You might try
> gettingcrosstool and building a 64bit toolchain. That will take a
> hour or 2though. Unless you have a screaming machine.
OK, brilliant. Apparently the only way to do this is
to install the
"toolchain-source" package and, yep, BUILD A TOOLCHAIN FROM SOURCE.
Sorry for being slow, but it was sleeping time here in Germany. :-)
Just for the records (You took the thread to debian-amd64 further down
the road):
You don't need a full toolchain for compiling kernel stuff, binutils and
gcc are enough. The kernel doesn't link against glibc. :-)
You could install binutils and gcc into a temporary directory (let's say
/tmp/cross), put /tmp/cross/bin in front of $PATH and you are set.
This way you can just rm -rf /tmp/cross if you want to get rid of it
again.
I am not subscribed to debian-amd64 so I don't know if you were
successful already, but if you want I can send you my script I use for
this kind of tasks per PM.
Christ, I cannot believe what a pain in the ass this
is. At this rate
it will have taken me 2 days to get this working.
I don't think so. Setting up a full toolchain may take a bit longer, but
for compiling kernels you really just need the easy part of it.
Kai
--
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden:
http://mail.yahoo.de
11 Dec
11 Dec
1:22 p.m.
* Lee Revell:
All I am trying to do is compile an x86_64 kernel on
i386 machine. It
dos not work:
This a few helper scripts; building an AMD64 kernel on i386 is not
exactly cross-compiling. Basically, the helper scripts must invoke
"gcc -m64" when no -m32 option is given, and "gcc" if there's an
"-m32" option ("-m64 -m32" does *not* override the -m64). More magic
is required for objcopy, otherwise the compiled kernel will crash on
boot.
The Debian kernel package building infrastructure contains the
necessary scripts AFAIK.
2:31 p.m.
On Sun, 2005-12-11 at 19:21 +0100, Florian Weimer wrote:
* Lee Revell:
Actually I was able to get this fixed. This was a bug in the kernel
build system where it didn't grok biarch toolchains like Ubuntu
provides. Andi Kleen sent me a kernel patch, presumably it will be
fixed in 2.6.15. Check the LKML archives for the past few days for
details.
Lee
All I am trying to do is compile an x86_64 kernel
on i386 machine. It
dos not work:
This a few helper scripts; building an AMD64 kernel on i386 is not
exactly cross-compiling. Basically, the helper scripts must invoke
"gcc -m64" when no -m32 option is given, and "gcc" if there's an
"-m32" option ("-m64 -m32" does *not* override the -m64). More
magic
is required for objcopy, otherwise the compiled kernel will crash on
boot.
The Debian kernel package building infrastructure contains the
necessary scripts AFAIK.
6716
days inactive
6719
days old
linux-audio-dev@lists.linuxaudio.org
26 comments
4 participants
participants (4)
-
Florian Weimer -
Kai Ruemmler -
Lee Revell -
Richard Smith