From: hjl@lucon.org (H.J. Lu)
To: ralf@uni-koblenz.de
Cc: ben@proximity.com.au, egcs@cygnus.com
Subject: Re: Building a cross compiler
Date: Mon, 27 Apr 1998 11:10:00 -0000 [thread overview]
Message-ID: <m0yTr6b-000598C@ocean.lucon.org> (raw)
In-Reply-To: <19980427091025.45994@uni-koblenz.de>
>
> On Mon, Apr 27, 1998 at 11:11:37AM +1000, The Red Fox wrote:
>
> > mv libgcc1.a libgcc1.cross || (echo You must find a way to make libgcc1.a;
> > false)
> > mv: libgcc1.a: No such file or directory
> > You must find a way to make libgcc1.a
> > make[1]: *** [libgcc1.cross] Error 1
> > make[1]: Leaving directory `/home/usr_src/egcs-1.0.2/build/gcc'
> > make: *** [cross] Error 2
> >
> > The big question is, how do I find a way to make libgcc1.a?
>
> In general writing libgcc1.a in assembler or just taking it from an
> existing native gcc compile are the two options.
>
The third one is if libgcc1 is written in asm in egcs or it can be
compiled by egcs, you can set OLD_CC to "./xgcc -B./" and compile it
by hand:
# cd egcs/gcc
# make libgcc1.a OLD_CC="./xgcc -B./"
I have done that for Linux/x86. Maybe we should add something to
egcs to do it automatically. It should be easy.
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1998-04-27 11:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-26 18:12 The Red Fox
1998-04-27 0:33 ` ralf
1998-04-27 11:10 ` H.J. Lu [this message]
1998-04-27 11:10 ` ralf
1998-04-27 11:10 ` H.J. Lu
1998-04-28 19:49 ` Todd Vierling
1998-04-27 14:44 ` Ian Lance Taylor
1998-04-28 19:49 ` Jim Wilson
1998-04-29 8:38 ` Joe Buck
1998-04-29 14:48 ` Jim Wilson
1998-05-04 21:55 ` Jeffrey A Law
1998-05-05 23:29 ` The Red Fox
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=m0yTr6b-000598C@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=ben@proximity.com.au \
--cc=egcs@cygnus.com \
--cc=ralf@uni-koblenz.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).