public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rmathew at gmail dot com" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/701] glibc does not compile with gcc-3.4.3 and binutils 2.15 Date: Thu, 21 Jul 2005 18:22:00 -0000 [thread overview] Message-ID: <20050721182207.30721.qmail@sourceware.org> (raw) In-Reply-To: <20050201005245.701.tg42@gmx.de> ------- Additional Comments From rmathew at gmail dot com 2005-07-21 18:22 ------- FWIW, I am guessing that you have compiled your GCC with something like "--with-arch=pentium3" or that you are using the "-march=pentium3" GCC option. This causes "__i686" and "__i686__" to become built-in defines and results in the problem you see. One workaround is to use an explicit "-march=i386 -mtune=pentium3" with GCC while compiling glibc. For example: CC='gcc -march=i386 -mtune=pentium3' /path/to/glibc/configure --prefix=/usr... I hope this helps. -- http://sources.redhat.com/bugzilla/show_bug.cgi?id=701 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
prev parent reply other threads:[~2005-07-21 18:22 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-01 0:53 [Bug libc/701] New: " tg42 at gmx dot de 2005-02-14 12:11 ` [Bug libc/701] " gotom at debian dot or dot jp 2005-02-15 8:36 ` duncan_roe at acslink dot net dot au 2005-07-21 18:22 ` rmathew at gmail dot com [this message]
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=20050721182207.30721.qmail@sourceware.org \ --to=sourceware-bugzilla@sources.redhat.com \ --cc=glibc-bugs@sources.redhat.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).