From: Daniel Jacobowitz <drow@false.org>
To: gcc@gcc.gnu.org
Subject: Re: Cross Compiling
Date: Mon, 16 Aug 1999 18:42:00 -0000 [thread overview]
Message-ID: <19990816214530.A2623@them.org> (raw)
In-Reply-To: <23299.934841798@upchuck.cygnus.com>
On Mon, Aug 16, 1999 at 04:16:38PM -0600, Jeffrey A Law wrote:
> In message < 19990816180939.A588@them.org >you write:
> > Is there any way to configure which will not require the libraries?
> > For instance, if you have no library for the target system?
> No. The autoconf mechanisms for libiberty, libstdc++, libf2c, libobjc
> require system libraries.
Hm, but is it possible to build a target C compiler without a target
libiberty (obviously you'd need a host libiberty but that isn't a
problem)?
> > Will libgcc build with just the headers for the target?
> Yes.
>
>
> jeff
>
>
>
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| dan@debian.org | | dmj+@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
WARNING: multiple messages have this Message-ID
From: Daniel Jacobowitz <drow@false.org>
To: gcc@gcc.gnu.org
Subject: Re: Cross Compiling
Date: Tue, 31 Aug 1999 23:20:00 -0000 [thread overview]
Message-ID: <19990816214530.A2623@them.org> (raw)
Message-ID: <19990831232000.bfQzIblMPD2aHsJkMi9UBOaJJ3tVND-UerF1uFUBmnA@z> (raw)
In-Reply-To: <23299.934841798@upchuck.cygnus.com>
On Mon, Aug 16, 1999 at 04:16:38PM -0600, Jeffrey A Law wrote:
> In message < 19990816180939.A588@them.org >you write:
> > Is there any way to configure which will not require the libraries?
> > For instance, if you have no library for the target system?
> No. The autoconf mechanisms for libiberty, libstdc++, libf2c, libobjc
> require system libraries.
Hm, but is it possible to build a target C compiler without a target
libiberty (obviously you'd need a host libiberty but that isn't a
problem)?
> > Will libgcc build with just the headers for the target?
> Yes.
>
>
> jeff
>
>
>
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| dan@debian.org | | dmj+@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
next prev parent reply other threads:[~1999-08-16 18:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-16 13:29 Jonathan Bartlett
1999-08-16 13:40 ` Jeffrey A Law
1999-08-16 15:07 ` Daniel Jacobowitz
1999-08-16 15:12 ` Mumit Khan
1999-08-31 23:20 ` Mumit Khan
1999-08-16 15:21 ` Jeffrey A Law
1999-08-16 18:42 ` Daniel Jacobowitz [this message]
1999-08-22 14:44 ` Philip Blundell
1999-08-31 23:20 ` Philip Blundell
1999-08-31 23:20 ` Daniel Jacobowitz
1999-08-31 23:20 ` Jeffrey A Law
1999-08-31 23:20 ` Daniel Jacobowitz
1999-08-31 23:20 ` Jeffrey A Law
1999-08-31 23:20 ` Jonathan Bartlett
-- strict thread matches above, loose matches on Subject: below --
2005-03-01 20:52 cross compiling Daniel Kegel
2005-03-01 6:54 vivek sukumaran
2004-09-05 11:26 Cross compiling Paul A. Kerr
2004-09-05 11:35 ` Andrew Walrond
2000-03-09 13:30 POUGET Patrick
2000-03-09 17:33 ` Alexandre Oliva
1999-10-11 12:01 Larbi El Hajjaoui
1999-10-31 23:35 ` Larbi El Hajjaoui
1998-04-21 17:38 Cross Compiling Jerry Alexandratos
1998-04-20 12:05 Jerry Alexandratos
1998-04-21 13:29 ` Jim Wilson
1998-04-21 19:10 ` H.J. Lu
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=19990816214530.A2623@them.org \
--to=drow@false.org \
--cc=gcc@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).