public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ljrittle@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, ljrittle@gcc.gnu.org, nobody@gcc.gnu.org, richard.sanders@newisys.com Subject: Re: other/3265: GCC 3.0 fails to build host=freebsd4.3 target=i386linux Date: Tue, 19 Jun 2001 20:19:00 -0000 [thread overview] Message-ID: <20010620031943.2630.qmail@sourceware.cygnus.com> (raw) Synopsis: GCC 3.0 fails to build host=freebsd4.3 target=i386linux Responsible-Changed-From-To: unassigned->ljrittle Responsible-Changed-By: ljrittle Responsible-Changed-When: Tue Jun 19 20:19:43 2001 Responsible-Changed-Why: Mine. State-Changed-From-To: open->feedback State-Changed-By: ljrittle State-Changed-When: Tue Jun 19 20:19:43 2001 State-Changed-Why: Did you populate the system headers from the target machine as per the easy to read instructions? It looks fairly doubtful since you didn't use --with-headers nor discuss populating @file{@var{prefix}/@var{target}/sys-include} when you reported how to repeat the failure... http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3265&database=gcc
next reply other threads:[~2001-06-19 20:19 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-19 20:19 ljrittle [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-21 13:27 ljrittle 2001-06-19 10:56 richard.sanders
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=20010620031943.2630.qmail@sourceware.cygnus.com \ --to=ljrittle@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=richard.sanders@newisys.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).