This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: How can I build a cross compiler for Digital Unix?
- From: Rupert Wood <rup at kanat dot pair dot com>
- To: "Ioannis E. Venetis" <iev at hpclab dot ceid dot upatras dot gr>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Thu, 26 Sep 2002 06:00:53 -0400 (EDT)
- Subject: Re: How can I build a cross compiler for Digital Unix?
Ioannis Venetis wrote:
> 2 days ago I sent a message with the same subject
> (http://gcc.gnu.org/ml/gcc-help/2002-09/msg00172.html),
> but unfortunately I haven't got any answers yet.
I can't offer much help right now (I know nothing about alpha-osf and
I'm away from my usual build machine) but:
The missing assembler and linker are going to be a problem. You should try
investigating the binutils gas/bfd and ld directories to find out what
alpha-* configurations they support. (Look at the config.* files.) I'd be
surprised if they didn't support any crosses to alpha. If you're still
stuck, might be better to ask on a binutils mailing list. You need both of
these built before you can get much further.
You'll need system include headers and libraries to build against. Easist
to take these from a live alpha system (from /usr/include - including
subdirectories - and selections from /lib and /usr/lib - likely don't need
subdirectories). See '--with-headers' and '--with-libs' in the GCC
configure documentation. You should also add '--without-newlib' unless
you specify both of these.
If you don't have access to an alpha machine to get these, you could
instead target alpha-elf (or whichever binary format OSF uses) and build
newlib as your C library and system headers
(http://sources.redhat.com/newlib/). I've no idea if this will work with
your emulator or not.
Bill Gatliff's FAQ at http://crossgcc.billgatliff.com/ might provide
some general pointers help.
I've no idea why the GCC build failed as it did. You might find a working
configuration for GCC by investigating gas/ld but otherwise you might want
to raise this on the gcc-bugs list. You could also try GCC 3.2.1 or
GCC 3.3 from CVS.
Good luck,
Rup.