public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: neroden@gcc.gnu.org To: alexsh@hectic.net, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: bootstrap/3437: [vxworks] cross-compile problem because of fixincludes Date: Thu, 27 Mar 2003 20:23:00 -0000 [thread overview] Message-ID: <20030327202151.29845.qmail@sources.redhat.com> (raw) Synopsis: [vxworks] cross-compile problem because of fixincludes State-Changed-From-To: feedback->open State-Changed-By: neroden State-Changed-When: Thu Mar 27 20:21:50 2003 State-Changed-Why: No feedback 3 months, bootstrap problem with old version. But this one looks specific and testable. Does anyone have a Vxworks system, so they can check that fixincludes does the right thing now? http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3437
next reply other threads:[~2003-03-27 20:21 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-27 20:23 neroden [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-14 10:56 giovannibajo 2003-05-14 8:36 Dara Hazeghi 2003-05-01 17:56 fsciarra 2002-11-26 15:46 bangerth 2001-06-27 6:36 bootstrap/3437: vxworks " alexsh
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=20030327202151.29845.qmail@sources.redhat.com \ --to=neroden@gcc.gnu.org \ --cc=alexsh@hectic.net \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --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: 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).