public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dhazeghi at yahoo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/12746] configure fails to find out whether a system has ANSI C header files Date: Sat, 08 Nov 2003 19:46:00 -0000 [thread overview] Message-ID: <20031108194657.11874.qmail@sources.redhat.com> (raw) In-Reply-To: <20031023164944.12746.falemagn@studenti.unina.it> ------- Additional Comments From dhazeghi at yahoo dot com 2003-11-08 19:46 ------- I don't quite understand the problem here. GCC doesn't try and run conftest, it only tries to build (compile and like) it. Where build!=host, this should be perfectly acceptable. If it can't compile a program using ANSI C headers, how can it compile the whole of gcc? Where is the problem? Thanks. -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Keywords| |build http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12746
next prev parent reply other threads:[~2003-11-08 19:46 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-10-23 17:28 [Bug bootstrap/12746] New: " falemagn at studenti dot unina dot it 2003-11-08 19:46 ` dhazeghi at yahoo dot com [this message] 2003-11-12 16:09 ` [Bug bootstrap/12746] " falemagn at studenti dot unina dot it 2003-11-14 7:45 ` dhazeghi at yahoo dot com 2003-11-14 19:42 ` neroden at gcc dot gnu dot org 2003-11-17 11:26 ` falemagn at studenti dot unina dot it 2003-11-17 11:30 ` falemagn at studenti dot unina dot it 2004-04-07 0:59 ` neroden at gcc dot gnu dot org 2004-07-07 3:40 ` pinskia at gcc dot gnu dot org
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=20031108194657.11874.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).