public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com> To: rodrigc@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: Sun, 27 Jan 2002 17:46:00 -0000 [thread overview] Message-ID: <20020128014609.3226.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/3641; it has been noted by GNATS. From: Daniel Jacobowitz <drow@mvista.com> To: rodrigc@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: bootstrap/3641: can not bootstrap on i386-linux and others without glibc - MD_FALLBACK_FRAME_STATE_FOR Date: Sun, 27 Jan 2002 20:44:37 -0500 Richard's verdict was that we should be going through make install_headers in glibc first instead of worrying about this. On Mon, Jan 28, 2002 at 01:39:57AM -0000, rodrigc@gcc.gnu.org wrote: > Synopsis: can not bootstrap on i386-linux and others without glibc - MD_FALLBACK_FRAME_STATE_FOR > > Responsible-Changed-From-To: unassigned->rodrigc > Responsible-Changed-By: rodrigc > Responsible-Changed-When: Sun Jan 27 17:39:57 2002 > Responsible-Changed-Why: > looking at it > State-Changed-From-To: feedback->analyzed > State-Changed-By: rodrigc > State-Changed-When: Sun Jan 27 17:39:57 2002 > State-Changed-Why: > looking at it > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3641 > -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2002-01-28 1:46 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-27 17:46 Daniel Jacobowitz [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:39 rodrigc 2001-10-29 8:36 Craig Rodrigues 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=20020128014609.3226.qmail@sources.redhat.com \ --to=drow@mvista.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=rodrigc@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: linkBe 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).