public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dan@debian.org
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/3641: can not bootstrap on i386-linux and others without glibc - MD_FALLBACK_FRAME_STATE_FOR
Date: Tue, 10 Jul 2001 16:56:00 -0000 [thread overview]
Message-ID: <20010710234634.16917.qmail@sourceware.cygnus.com> (raw)
>Number: 3641
>Category: bootstrap
>Synopsis: can not bootstrap on i386-linux and others without glibc - MD_FALLBACK_FRAME_STATE_FOR
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Jul 10 16:56:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: dan@debian.org
>Release: gcc-3.0
>Organization:
>Environment:
>Description:
MD_FALLBACK_FRAME_STATE_FOR wants to be able to unwind
the stack through signal frames, so it uses <signal.h> and <sys/ucontext.h>
to find the sigcontext's members. If you do not have a libc for your target, libgcc can not be compiled, because those headers are not found.
It's easy to work around this by adding #ifndef inhibit_libc, but the compiled
copies are included in a glibc built with that compiler (currently), and
so stick around. I should not have to rebuild glibc a second time just to get
this correct. Would hardcoding the necessary offsets or structures be an
acceptable alternative to including the header files? If so, I can make a patch.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-07-10 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 16:56 dan [this message]
2001-10-28 20:35 rodrigc
2001-10-29 8:36 Craig Rodrigues
2002-01-27 17:39 rodrigc
2002-01-27 17:46 Daniel Jacobowitz
2003-05-14 8:46 Dara Hazeghi
2003-05-14 17:30 drow
2003-05-14 17:36 Daniel Jacobowitz
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=20010710234634.16917.qmail@sourceware.cygnus.com \
--to=dan@debian.org \
--cc=gcc-gnats@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).