public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Todd Vierling <tv@pobox.com>
To: ralf@uni-koblenz.de
Cc: "H.J. Lu" <hjl@lucon.org>, ben@proximity.com.au, egcs@cygnus.com
Subject: Re: Building a cross compiler
Date: Tue, 28 Apr 1998 19:49:00 -0000	[thread overview]
Message-ID: <Pine.NEB.3.96.980428205453.15282A-100000@like.duh.org> (raw)
In-Reply-To: <19980427192843.21650@uni-koblenz.de>

On Mon, 27 Apr 1998 ralf@uni-koblenz.de wrote:

: > I have done that for Linux/x86. Maybe we should add something to
: > egcs to do it automatically. It should be easy.
: 
: What functions from libgcc1.a are being used on Intel?  Could they somehow
: be eleminated?  Life is so much sweeter without having to deal with
: libgcc1.a.

None.  No Linux or *BSD based i386 system requires libgcc1.a at all.  The
instructions are all handled internally.  Unfortunately, there's no
``t-linux'' in config/i386 to override LIBGCC1 and CROSS_LIBGCC1 with
"libgcc1.null".

I've brought this up on this list before.  Perhaps I should search archives?

-- 
-- Todd Vierling (Personal tv@pobox.com; Bus. todd_vierling@xn.xerox.com)


  parent reply	other threads:[~1998-04-28 19:49 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 [this message]
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=Pine.NEB.3.96.980428205453.15282A-100000@like.duh.org \
    --to=tv@pobox.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).