From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] building the toolchain
Date: Mon, 21 Feb 2000 21:35:15 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678204951@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678204943@msgid-missing>
Will the ftp site disappear in the near future?
No.
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:
It looks like a good start. Unfortunately, since you did not report any
actual error, all I can do is guess at what might be the problem. Bug reports
are much more useful if they actually contain info about the bug.
My guess is that the build failed while trying to compile gcc's libgcc.a
library because stdio.h was missing.
To fix this problem, you want to use the additional configure options
--with-headers=<path> --with-libs=<path>
where <path> is a directory name containing ia64-linux header files and
libraries respectively. If you have an ia64-linux machine, you can just
copy the /usr/include and /lib directories to someplace on the machine where
you are building the cross compiler, and then point the options at the
copied directories.
Unfortunately, I just took a look at the OS CD-rom from LinuxWorld, and
discovered that /usr/include and /lib are empty. This means there is no easy
way to build a working toolchain. I don't know why these weren't included
in the public release.
The OS CD-rom does contain a copy of the glibc sources in /usr/src. So you
can still do a build, but you essentially have to build gcc and glibc at
the same time. I've never done that. I'm a novice when it comes to glibc
builds, so I can't guarantee that I can figure out how to do this.
Jim
next prev parent reply other threads:[~2000-02-21 21:35 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 [this message]
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-105590678204951@msgid-missing \
--to=wilson@cygnus.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