From: Zack Weinberg <zack@codesourcery.com>
To: Dan Kegel <dank@kegel.com>
Cc: Andrew Pinski <pinskia@physics.uc.edu>,
Peter Barada <peter@baradas.org>,
wilson@tuliptree.org, gcc@gcc.gnu.org
Subject: Re: cross-compilation documentation
Date: Sun, 22 Jun 2003 20:27:00 -0000 [thread overview]
Message-ID: <87znkadj94.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <3EF5FACA.9020400@kegel.com> (Dan Kegel's message of "Sun, 22 Jun 2003 11:51:54 -0700")
Dan Kegel <dank@kegel.com> writes:
> Zack Weinberg wrote:
>> Andrew Pinski <pinskia@physics.uc.edu> writes:
>>>RCS file: /cvs/gcc/gcc/gcc/config/rs6000/linux.h,v
>>> -#ifdef IN_LIBGCC2
>>>+#if defined (IN_LIBGCC2) && !defined (inhibit_libc)
>>> #include <signal.h>
>>> ...
>> For what it's worth, that looks like the right fix to this immediate
>> problem. We want to decouple libgcc build from compiler build for
>> other reasons, but that's sufficiently invasive that it's probably a
>> 3.5 item at this point (the way I wanna do it, it needs bootstrap to
>> run at top level, and it involves moving a lot of files).
>
> If this is the right way to go, then you need to patch
> not just rs6000, but also just about every other architecture,
> don't you?
Yes, probably. But Dan raises a valid point. I wonder if it would
make sense to disable the unwind library entirely when inhibit_libc
is true. The trouble with that is I don't know what unwind-related
things are lurking in corners of glibc.
zw
next prev parent reply other threads:[~2003-06-22 19:08 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 0:36 Dan Kegel
2003-06-18 14:58 ` Joel Sherrill
2003-06-22 17:10 ` Dan Kegel
2003-06-19 0:00 ` Jim Wilson
2003-06-22 17:12 ` Dan Kegel
2003-06-22 17:19 ` Andrew Pinski
2003-06-22 17:21 ` Dan Kegel
2003-06-22 17:35 ` Peter Barada
2003-06-22 17:50 ` Andrew Pinski
2003-06-22 17:56 ` Jan-Benedict Glaw
2003-06-22 18:07 ` Zack Weinberg
2003-06-22 20:15 ` Dan Kegel
2003-06-22 20:27 ` Zack Weinberg [this message]
2003-06-22 20:36 ` Peter Barada
2003-06-22 21:10 ` Daniel Jacobowitz
2003-06-23 3:06 ` Dan Kegel
2003-06-23 4:08 ` Jan-Benedict Glaw
2003-06-23 4:22 ` Dan Kegel
2003-06-23 9:10 ` Peter Barada
2003-06-23 12:20 ` Dan Kegel
2003-06-23 12:15 ` Peter Barada
2003-06-23 12:20 ` Dan Kegel
2003-06-23 14:14 ` Peter Barada
2003-06-23 15:38 ` Hans-Peter Nilsson
2003-06-23 16:04 ` Dan Kegel
2003-06-23 16:11 ` Hans-Peter Nilsson
2003-06-23 15:57 ` Dan Kegel
2003-06-23 13:01 ` Daniel Jacobowitz
2003-06-23 14:14 ` Peter Barada
2003-06-23 14:50 ` Daniel Jacobowitz
2003-06-23 14:10 ` Daniel Jacobowitz
2003-06-22 18:41 ` Daniel Jacobowitz
2003-06-22 17:30 ` Jan-Benedict Glaw
-- strict thread matches above, loose matches on Subject: below --
2004-05-29 6:25 Dan Kegel
2004-05-29 6:57 ` Zack Weinberg
2004-06-01 16:35 ` Dan Kegel
2004-06-01 17:38 ` Dave Korn
2004-06-01 17:45 ` Peter Barada
2003-06-22 17:43 Dara Hazeghi
2003-06-22 17:49 ` Andrew Pinski
2003-06-22 17:53 ` Jan-Benedict Glaw
2003-06-24 5:26 ` Jim Wilson
2003-06-22 19:36 ` Dara Hazeghi
2003-06-27 12:13 ` Gerald Pfeifer
2003-06-22 17:49 ` Jan-Benedict Glaw
2001-11-13 16:21 Cross-compilation documentation Joseph S. Myers
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=87znkadj94.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=dank@kegel.com \
--cc=gcc@gcc.gnu.org \
--cc=peter@baradas.org \
--cc=pinskia@physics.uc.edu \
--cc=wilson@tuliptree.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).