public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: badrian@ss.pub.ro
Cc: gcc-help@gcc.gnu.org
Subject: Re: cross-compiling
Date: Tue, 14 Mar 2000 13:34:00 -0000	[thread overview]
Message-ID: <200003142126.WAA01272@loewis.home.cs.tu-berlin.de> (raw)
In-Reply-To: <004a01bf8dc2$3e83a550$3725558d@cs.pub.ro>

> When cross-compiling gcc , is it OK to provide an empty libgcc1.a that
> was created using the tools already existing on the host machine?

Since libgcc.a won't be used for *building* gcc (unless build!=host),
then yes, that is ok. I don't know what you mean by "empty", though -
if it does not have any functions, but the target relies on functions
in it, then the cross-compiler won't work (specifically, binaries
compiled with it won't link).

Regards,
Martin

WARNING: multiple messages have this Message-ID

From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: badrian@ss.pub.ro
Cc: gcc-help@gcc.gnu.org
Subject: Re: cross-compiling
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <200003142126.WAA01272@loewis.home.cs.tu-berlin.de> (raw)
Message-ID: <20000401000000.WM4r_AiGg47zM20BVPhgaMZJ2OS_4Fiuf5pqtWJRXKM@z> (raw)
In-Reply-To: <004a01bf8dc2$3e83a550$3725558d@cs.pub.ro>

> When cross-compiling gcc , is it OK to provide an empty libgcc1.a that
> was created using the tools already existing on the host machine?

Since libgcc.a won't be used for *building* gcc (unless build!=host),
then yes, that is ok. I don't know what you mean by "empty", though -
if it does not have any functions, but the target relies on functions
in it, then the cross-compiler won't work (specifically, binaries
compiled with it won't link).

Regards,
Martin

  reply	other threads:[~2000-03-14 13:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-14  6:31 cross-compiling Dragos Badea
2000-03-14 13:34 ` Martin v. Loewis [this message]
2000-04-01  0:00   ` cross-compiling Martin v. Loewis
2000-04-01  0:00 ` cross-compiling Dragos Badea
2001-11-16 14:58 Cross-compiling Tamas Nagy
     [not found] <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAWJVBon0D1RG D/gAQYJErt8KAAAAQAAAA1bv9CcLIbEetA/SPF24/aAEAAAAA@web.de>
2001-11-16 15:02 ` Cross-compiling Andrea 'Fyre Wyzard' Bocci
2004-04-27  9:30 Cross-Compiling Michael Becker
2004-04-27 13:32 ` Cross-Compiling Ian Lance Taylor

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=200003142126.WAA01272@loewis.home.cs.tu-berlin.de \
    --to=martin@loewis.home.cs.tu-berlin.de \
    --cc=badrian@ss.pub.ro \
    --cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).