public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@cern.ch>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] building the toolchain
Date: Tue, 22 Feb 2000 10:34:23 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678204952@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678204943@msgid-missing>

>>>>> "Jim" = Jim Wilson <wilson@cygnus.com> writes:

Jim> The OS CD-rom does contain a copy of the glibc sources in
Jim> /usr/src.  So you can still do a build, but you essentially have
Jim> to build gcc and glibc at the same time.  I've never done that.
Jim> I'm a novice when it comes to glibc builds, so I can't guarantee
Jim> that I can figure out how to do this.

Hmmm bummer

Well it shouldn't be too hard actually.

First trick is to build gcc for cross compiling like if you were
simply compiling the kernel. Then build glibc with something like
this:

mkdir glibc-build
cd glibc-build
../glibc/configure  --with-headers=/usr/src/linux-ia64/include --disable-profile --disable-sanity-checks --disable-cvs --enable-add-ons=crypt --prefix=<glibc-hack-directory>  --host=ia64-gnu-linux --build=i386-linux
make install

Then afterwards one should be able to configure gcc to pick up the
glibc headers and library.

Jes



  parent reply	other threads:[~2000-02-22 10:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-20 19:32 [Linux-ia64] building the toolchain Tim Riker
2000-02-20 20:18 ` Uros Prestor
2000-02-21  4:00 ` Matt_Domsch
2000-02-21 21:35 ` Jim Wilson
2000-02-22 10:34 ` Jes Sorensen [this message]
2000-02-23  5:07 ` Jim Wilson
2000-02-23  7:10 ` Tim Riker

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-105590678204952@msgid-missing \
    --to=jes.sorensen@cern.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox