This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: i686 Multilib Question


"Armin K." <krejzi@email.com> writes:

> I have currently i686 system (Linux From Scratch) and I would like to
> bootstrap multilib compiler on that one. The problem is, I don't have
> any working multilib compiler, only i686 one. And I don't know where
> to start.
>
> I have tried first enabling multilib and all targets in binutils, then
> statically compiling gcc.
>
> I ran into problems in bootstrap stage and tought it was a bug. A more
> detailed report about this can be found in bug report
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53662
>
> Has anyone managed to bootstrap multilib compiler using i686 one? I
> would like to have i686 compiler, but also I want to be able to use
> -m64 which is done by multilib right? I am aware that I need multilib
> binutils, static gcc to compile multilib glibc and use it to bootstrap
> full gcc with shared libraries and such. Am I right? But I am unable
> to accomplish that. Could anyone guide me in right direction? Google
> does not help very much. And yes, I want this. I don't want to install
> or build 64 bit operating system.

In order to build a GCC that can build 64-bit binaries, you need to have
a 64-bit C library and 64-bit binutils installed.  Do you?

There is a shell script config.guess in the top level GCC directory.
When you run it, does it print x86_64-unknown-linux-gnu or
i686-unknown-linux-gnu?  If it prints i686, that suggests that uname -m
on your system prints i686, and that suggests that your kernel is not
running in 64-bit mode.

Ian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]