public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Craig Rodrigues <rodrigc@mediaone.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: bootstrap/3641: can not bootstrap on i386-linux and others without glibc - MD_FALLBACK_FRAME_STATE_FOR
Date: Mon, 29 Oct 2001 08:36:00 -0000	[thread overview]
Message-ID: <20011029163602.5525.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR bootstrap/3641; it has been noted by GNATS.

From: Craig Rodrigues <rodrigc@mediaone.net>
To: gcc-gnats@gnu.org
Cc: Daniel Jacobowitz <drow@mvista.com>, gcc-bugs@gcc.gnu.org
Subject: Re: bootstrap/3641: can not bootstrap on i386-linux and others without glibc - MD_FALLBACK_FRAME_STATE_FOR
Date: Mon, 29 Oct 2001 11:32:16 -0500

 On Mon, Oct 29, 2001 at 10:59:45AM -0500, Daniel Jacobowitz wrote:
 > (if there's a better way to add info to a GNATS bug than Reply To All,
 > without having a GNATS account, it would be nice if it was mentioned
 > somewhere obvious.)
 
 To append info to a GNATS entry, make sure you CC:
 gcc-gnats@gcc.gnu.org, and make sure that the Subject:
 field of your e-mail contains the GNATS ID for the Problem Report,
 ie.
 
 "Subject:  Re: Re: bootstrap/3641: can not bootstrap on....."
 
 If you can figure out a good place to put this in documentation,
 I'll write a patch for it.
 
 > I talked to Richard Henderson about this, and for my problem (which
 > involved glibc 2.2.3 or 2.2.4) the correct solution was to make a
 > libc-headers package instead of modifying GCC.  That probably doesn't
 > help you.  I have a patch to hardcode the data structures in question
 > if you want it.
 
 
 There is a patch very similar to what you are talking about,
 but meant to address the problem of bootstrapping on
 older versions of glibc.
 
 I submitted this patch, to detect the existence of ucontext.h
 in the configure script:
 
 http://gcc.gnu.org/ml/gcc-patches/2001-10/msg01543.html
 
 The next part of the patch, which I have not tested yet is
 here:
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=4068&database=gcc
 
 Does that patch look like it would work for your problem?
 -- 
 Craig Rodrigues        
 http://www.gis.net/~craigr    
 rodrigc@mediaone.net          


             reply	other threads:[~2001-10-29  8:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-29  8:36 Craig Rodrigues [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 17:36 Daniel Jacobowitz
2003-05-14 17:30 drow
2003-05-14  8:46 Dara Hazeghi
2002-01-27 17:46 Daniel Jacobowitz
2002-01-27 17:39 rodrigc
2001-10-28 20:35 rodrigc
2001-07-10 16:56 dan

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=20011029163602.5525.qmail@sourceware.cygnus.com \
    --to=rodrigc@mediaone.net \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).