Home > Error Cannot > Error Cannot Represent Relocation Type Bfd_reloc_x86_64_32s

Error Cannot Represent Relocation Type Bfd_reloc_x86_64_32s

Ken -- das eine Mal als Tragödie, das andere Mal als Farce rlrevell at joe-job Dec9,2005,1:35PM Post #13 of 36 (4415 views) Permalink Re: i386 -> x86_64 cross compile failure (binutils bug?) [In Lee - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo [at] vger More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ rkiddy commented Dec 29, 2013 VirtualBox is telling me: Operating System: Debian (64 bit) Let me know how best to do it and I can get a more verbose description of But the build fails > with: > > $ make ARCH=x86_64 > arch/x86_64/kernel/entry.S:785: Error: cannot represent relocation type BFD_RELOC_64 Ubuntu/Debian provide a biarch gcc, but do not (did not?) provide a this contact form

The Debian FAQ explains the different versions, but who reads it? ;-) To contrast, in both Fedora and Ubuntu, the default download is the image for 64-bit PCs. … -- Nadav Work more with Ubuntu and CentOS. But there's another more serious complication: Currently, OSv's build requires *runing* OSv, for preparing the image, and it's not possible to run a 64-bit guest (OSv) on top of a 32-bit I've done it without all that making a separate binutils non-sense. http://www.gossamer-threads.com/lists/linux/kernel/596722

Ken -- das eine Mal als Tragödie, das andere Mal als Farce kyle at mcmartin Dec9,2005,11:58AM Post #3 of 36 (4404 views) Permalink Re: i386 -> x86_64 cross compile failure (binutils bug?) [In If you use a freshly unmodified tree and apply the appended patch does it work for you? -Andi Pass -m64 by default This might help on distributions that use a 32bit Obviously, the #if _DEBUG ... These asm directives are 64 bit only ?

  1. This is> bullshit.Google seems to suggest that 32->64 is a compile option.http://lists.freebsd.org/pipermail/freebsd-amd64/2004-November/002681.htmlIts 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.htmlUbuntu does not have a
  2. Or is the plan to run an osv machine inside a debian machine inside a Mac just too weird to deal with?
  3. But the build fails > > with: > > > > $ make ARCH=x86_64 > > [...] > > CC init/initramfs.o > > CC init/calibrate.o > > LD init/built-in.o > >
  4. And I repeat, messing with CFLAGS should NOT be necessary.

In addition they don't seem to be very fond of contributing changes back - normally one would expect the distribution maintainer to submit a patch like this if they set up Log in Have an account? What the "project" is that you took the source from, assuming it's an open source project. Only the very early x86-64 distributions set up the gccs like this until it was noticed that a gcc compiled for 64bit targets run noticeable slower on 32bit and needs more

Unfortunately gcc-4.0-x86-64 +deps are an 80MB download but I guess that's better than nothing. I didn't realize when it says "AS foo.o" it really means it's running > CC, not AS. (I had also built a cross compiling gcc, but didn't realize it > was Smith Lee Revell 2005-12-09 00:39:15 UTC PermalinkRaw Message 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 Browse other questions tagged c++ linux gcc assembly or ask your own question.

I can't believe there's no easy way to do it. Smith Lee Revell 2005-12-08 22:38:10 UTC PermalinkRaw Message Post by Richard SmithUgh, there's no way to do this by just installing packages? Thanks! I am tryingto reproduce a problem an x86_64 user at a remote location is having.

Perhaps if you ask on the> debian-amd64 some kind soul has unofficial packages you can use.>http://debian.speedblue.org/Thanks. https://github.com/cloudius-systems/osv/issues/144 If I don't change the CFLAGS I get: $ 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 Smith Lee Revell 2005-12-08 22:17:37 UTC PermalinkRaw Message Post by Richard Smithcross compiling almost never "just works". Personal Open source Business Explore Sign up Sign in Pricing Blog Support Search GitHub This repository Watch 299 Star 2,297 Fork 424 cloudius-systems/osv Code Issues 329 Pull requests 5 Projects

At this rateit will have taken me 2 days to get this working.Yep. weblink I can't believe there's no easy way to do it. Thanks, Lee - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo [at] vger More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the bit is just a way to select a breakpoint for debug or no breakpoint variation of the code for non-debug mode. 2) You would really have to ask whoever wrote the

In this decade, the overwhelming majority of users need the "amd64" image, and yet only a tiny minority will have ever heard the name "amd64" and know they are supposed to 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. That will take a hour or 2though. navigate here You might try getting> crosstool and building a 64bit toolchain.

Unfortunately gcc-4.0-x86-64 +deps are an 80MB download but I guess that's better than nothing. Terms Privacy Security Status Help You can't perform that action at this time. Cancel Delete Close Promote this Tweet Close Block Cancel Block Add a location to your Tweets When you tweet with a location, Twitter stores that location. You can switch location on/off

Unless you have a screaming machine.--Richard A.

As for examples, I'm pretty sure there are tutorials, but changing .quad to .long should fix the immediate error in the title of your post - of course, there are most OSv needs a bunch of Debian packages to be installed (besides the obvious stuff like C compiler, it also needs some less obvious things like ant, qemu-img, etc. That will take a hour or 2Or perhaps try booting the Kanotix64 livecd and compile under that?--Richard A. Smith Lee Revell 2005-12-09 01:07:15 UTC PermalinkRaw Message Post by Richard SmithOn Thu, 2005-12-08 at 19:05 -0500, Lee Revell wrote:> > (I apologise if anyone finds this thread OT, it is

Skip all Welcome home! Ihave their kernel sources and .config. After fixing that,I got a bit farther.LD usr/built-in.old: warning: i386 architecture of input file `usr/initramfs_data.o' is incompatible with i386:x86-64 outputThis one is worrisome, maybe I also need to pass LDFLAGS?CC arch/x86_64/kernel/process.oCC his comment is here This is no doubt a different issue and I will verify that this is not just from something I missed before I squawk.

Remember me · Forgot password? This isbullshit.Lee Richard Smith 2005-12-08 22:13:23 UTC PermalinkRaw Message Ugh, there's no way to do this by just installing packages? So its not worth the trouble. I still need to add "-m64" to the CFLAGS and AFLAGS to get it to work at all, otherwise gcc is invoked in 32 bit mode, and they don't address the

Lee Previous message: [linux-audio-dev] Cross compiling the kernel Next message: [linux-audio-dev] Cross compiling the kernel Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More The bug seems to be that the kernel build system does not grok biarch toolchains - it really insists on a separate toolchain for i386 and x86_64 even though the situation You should not need to mess with the CFLAGS. But the build fails > >with: > > > >$ make ARCH=x86_64 > > [...] > > CC init/initramfs.o > > > > > > I have successfully done this using

May I suspect a compiler installation issue (the compiler and the required dependencies were installed from rpms on top of the existing and newer gcc using rpm -ivh --force options)? Xav - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo [at] vger More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ The 32-bit > > environment sets int, long and pointer to 32 > > bits and generates code that runs on any i386 system. Already have an account?

Back to Top