From: Ian Lance Taylor <ian@cygnus.com>
To: hjl@lucon.org
Cc: ralf@uni-koblenz.de, ben@proximity.com.au, egcs@cygnus.com
Subject: Re: Building a cross compiler
Date: Mon, 27 Apr 1998 14:44:00 -0000 [thread overview]
Message-ID: <199804272143.RAA01085@subrogation.cygnus.com> (raw)
In-Reply-To: <m0yTr6b-000598C@ocean.lucon.org>
From: hjl@lucon.org (H.J. Lu)
Date: Mon, 27 Apr 1998 09:50:13 -0700 (PDT)
> 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.
We already have such mechanisms.
If you have an assembler version of the file in egcs, set
CROSS_LIBGCC1 to libgcc1-asm.a, and set LIB1ASMSRC and LIB1ASMFUNCS in
your t-* file. For example, see m68k/t-m68kbare, which uses
m68k/lib1sf68.asm.
If the file can be built with egcs, then it isn't necessary at all.
In such a case, set CROSS_LIBGCC1 to the empty string, as in
mips/t-mips.
Ian
next prev parent reply other threads:[~1998-04-27 14:44 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
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 [this message]
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=199804272143.RAA01085@subrogation.cygnus.com \
--to=ian@cygnus.com \
--cc=ben@proximity.com.au \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.org \
--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).