All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@tuliptree.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Building IA-64 toolchain
Date: Wed, 07 May 2003 15:14:17 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705654@msgid-missing> (raw)

On Wed, 2003-05-07 at 12:03, navin wrote:
> 	I am doing a project on compilers.I have to build gcc for ia64.I 
> did build the binutils .In that case i didn't get any compilation errors.
> HOSTMACHINE=i386 pentium
> TARGETMACHINE=ia64

Gcc includes libraries that require access to the standard C library in
order to build.  You must provide the standard C library yourself
somehow.  You have not done this.

If you only want a compiler for building the kernel, then you don't need
any libraries.  In that case, you are already done.  What you have is
good enough to build a kernel.

If you need a complete gcc build, then you will need a C library.  If
you have access to a running ia64-linux system, the easy way to do this
is to copy the IA-64 linux /usr/include and /usr/lib to the x86 machine,
and then configure using --with-headers= and --with-libs= pointing at
the IA-64 header and library directories respectively.

An alternative method is to try to build gcc and glibc in parallel. 
This is not easy.  Offhand, I don't know how to do it, as I have never
tried to do this.

>  --without-headers

There is no such configure option.  The headers are required, and there
is no way to get around this.

> In file included from ../../gcc-3.2/gcc/libgcc2.c:37:
> ../../gcc-3.2/gcc/tsystem.h:63:19: stdio.h: No such file or directory
> ../../gcc-3.2/gcc/tsystem.h:66:23: sys/types.h: No such file or directory
> In file included from 

The standard C library header files are missing.

Jim



             reply	other threads:[~2003-05-07 15:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07 15:14 Jim Wilson [this message]
2003-05-07 15:20 ` [Linux-ia64] Building IA-64 toolchain Jim Wilson
2003-05-07 16:15 ` navin
2003-05-07 17:41 ` David Mosberger
2003-05-07 17:52 ` navin
2003-05-07 18:05 ` David Mosberger
2003-05-07 18:14 ` Randolph Chung
2003-05-08  8:33 ` navin
2003-05-08 17:24 ` Jim Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ia64-105590723705654@msgid-missing \
    --to=wilson@tuliptree.org \
    --cc=linux-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.