This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Help with Gcc-3.0.3 cross-compile
- From: "Shureih, Tariq" <tariq dot shureih at intel dot com>
- To: "'Alexandre Oliva'" <aoliva at redhat dot com>, Jim Wilson <wilson at redhat dot com>
- Cc: "Shureih, Tariq" <tariq dot shureih at intel dot com>, Joe Buck<jbuck at synopsys dot COM>, smc at us dot ibm dot com, gcc at gcc dot gnu dot org
- Date: Tue, 12 Feb 2002 11:28:30 -0800
- Subject: RE: Help with Gcc-3.0.3 cross-compile
Does that apply even if what I am trying to produce is a tools chain to be
distributed in a "Development" environment that supports both IA32 and IA64?
This is my goal, to provide a root-jail environment which developers can use
to develop and validate code for both IA32 and IA64.
The area that is still vague to me is what Jim had pointed in his last
email.
When I ran configure with --target=ia64-pc-linux-gnu
--prefix=/home/cross-ia64, my intent was to build the include and lib that
will be later used with gcc cross compile.
I didn't think it was going to work, but sure enough, "make all" worked,
didn't make sense, but I didn't question it.
So, if that's not the correct way to produce the headers and libs to be used
with gcc cross compile, where do I get, or how do I build, the "target"
headers and libs.
Last, does redhat or any other linux distributor provide such package? A
cross-ia64 development package that I can install in my redhat 7.1 for
example and have both IA64 and IA32 tool chains?
Again, thank you all for the help.
--
Tariq
-----Original Message-----
From: Alexandre Oliva [mailto:aoliva@redhat.com]
Sent: Monday, February 11, 2002 11:00 PM
To: Jim Wilson
Cc: Shureih, Tariq; Joe Buck; smc@us.ibm.com; gcc@gcc.gnu.org
Subject: Re: Help with Gcc-3.0.3 cross-compile
On Feb 12, 2002, Jim Wilson <wilson@redhat.com> wrote:
>> 5-Built glibc-2.2.5 for cross compile --target=ia64-pc-linux-gnu and
>> prefix=/home/cross-ia64
> You can't compile a cross glibc if you don't have a cross compiler yet,
> so you couldn't have done this at this point.
Also, for glibc, it's not --target, it's --host that you want to
specify, since the glibc you want to build is something that will
*run* (i.e., be hosted on) ia64-pc-linux-gnu, not something that
should generate code for ia64-pc-linux-gnu. --target is pointless for
glibc.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer