public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wanderer at rsu dot ru" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/19656] libstdc++ testsuite results differ if bootstrap gcc 4.0 using some gcc 4.0 version or early (gcc 3.4.3) gcc version at FreeBSD Date: Mon, 31 Jan 2005 16:59:00 -0000 [thread overview] Message-ID: <20050131165924.7342.qmail@sourceware.org> (raw) In-Reply-To: <20050127125831.19656.wanderer@rsu.ru> ------- Additional Comments From wanderer at rsu dot ru 2005-01-31 16:59 ------- I found problem: At FreeBSD intl.h placed in /usr/local/include and gcc 3.4.* not search by default /usr/local/include for system headers (I check this for system compiler gcc version 3.4.2 [FreeBSD] 20040728 and gcc 3.4.3) gcc/intl/configure check intl.h by run test with command line: gcc -o conftest -g -O2 conftest.c 1>&5 and fail. As result if gcc 4.0 bootstrap using gcc 3.4.* we have gcc 4.0 with disabled intl support :((( -- What |Removed |Added ---------------------------------------------------------------------------- CC| |ljrittle at gcc dot gnu dot | |org, pinskia at gcc dot gnu | |dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19656
next prev parent reply other threads:[~2005-01-31 16:59 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-27 13:00 [Bug libstdc++/19656] New: " wanderer at rsu dot ru 2005-01-27 13:04 ` [Bug libstdc++/19656] " wanderer at rsu dot ru 2005-01-27 13:09 ` wanderer at rsu dot ru 2005-01-27 13:25 ` pinskia at gcc dot gnu dot org 2005-01-28 23:33 ` ljrittle at gcc dot gnu dot org 2005-01-29 0:04 ` wanderer at rsu dot ru 2005-01-29 23:49 ` wanderer at rsu dot ru 2005-01-31 15:05 ` wanderer at rsu dot ru 2005-01-31 16:59 ` wanderer at rsu dot ru [this message] 2005-01-31 18:45 ` wanderer at rsu dot ru 2005-02-21 21:28 ` wanderer at rsu dot ru [not found] <bug-19656-333@http.gcc.gnu.org/bugzilla/> 2008-01-26 23:50 ` rguenth 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=20050131165924.7342.qmail@sourceware.org \ --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).