From: Tim Riker <TimR@CalderaSystems.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] building the toolchain
Date: Sun, 20 Feb 2000 19:32:11 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678204943@msgid-missing> (raw)
ftp://ftp.cygnus.com/private/intel/
Contains the sources for the ia64 toolchain (gcc, gas, etc) Note that
www.cygnus.com has been swallowed up by redhat.com. Will the ftp site
disappear in the near future?
I've been trying to build and use these tools. I believe I am missing
some step along the way. I'm starting with the cross compiler and
attempting to build a new kernel. Here's what I've done:
rm -rf patches src local build
tar xzf patches.tgz
tar xzf src.tgz
patch -d src/gas/config/ < patches/patch.001
patch -d src/gcc/config/ia64/ < patches/patch.002
patch -d src/gcc/config/ia64/ < patches/patch.003
patch -d src/gcc/config/ia64/ < patches/patch.004
patch -d src/libgloss/ia64/ < patches/patch.005
patch -d src/gcc/config/ia64/ < patches/patch.006
patch -d src/ < patches/patch.007
patch -d src/gcc/config/ia64/ < patches/patch.008
patch -d src/opcodes/ < patches/patch.009
mkdir install
prefix=`pwd`/install
mkdir build
cd build
../src/configure --prefix=$prefix --target=ia64-cygnus-linux
make
PS: I'll be hanging on #ia64@irc.openprojects.net if anyone wants to
chat there.
--
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.
next reply other threads:[~2000-02-20 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-20 19:32 Tim Riker [this message]
2000-02-20 20:18 ` [Linux-ia64] building the toolchain Uros Prestor
2000-02-21 4:00 ` Matt_Domsch
2000-02-21 21:35 ` Jim Wilson
2000-02-22 10:34 ` Jes Sorensen
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-105590678204943@msgid-missing \
--to=timr@calderasystems.com \
--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