public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org To: apbianco@redhat.com, rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, sefer@hotmail.com Subject: Re: bootstrap/4989: Bootstrap on Linux x86 fails. Date: Tue, 01 Jan 2002 16:00:00 -0000 [thread overview] Message-ID: <20020102000024.30465.qmail@sources.redhat.com> (raw) Synopsis: Bootstrap on Linux x86 fails. State-Changed-From-To: open->feedback State-Changed-By: rodrigc State-Changed-When: Tue Jan 1 16:00:23 2002 State-Changed-Why: apbianco@redhat.com sent this e-mail out before, but it looks like it got garbled and inserted into the Fix section of this PR. Are you still getting the same problem? Can you follow these instructions and give us your feedback? Thanks. ====== I haven't bootstrapped in a long time, but I would suspect a lot of people are doing that on x86 (with all the language support you're requesting.) If this persists, you should send email to java@gcc.gnu.org, since the Boehm GC is a part of the GCC Java runtime. Note that the pre-processor might have changed recently in order to be more compliant, although I couldn't find evidences of it -- this error mode has been in effect for a while. So it could be a configuration problem where you end up with an improperly #define'ed macro. Could you try the same libtool invokation along with the `-E' flag and post the results? Thank you. We'll see what really gets cpp upset. ====================================================== http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4989
next reply other threads:[~2002-01-02 0:00 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-01 16:00 rodrigc [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-01-21 20:56 rodrigc 2001-12-03 7:56 sefer
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=20020102000024.30465.qmail@sources.redhat.com \ --to=rodrigc@gcc.gnu.org \ --cc=apbianco@redhat.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=sefer@hotmail.com \ /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).