public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/29049] possible problem: building gcc >= 4.2 on i686 GNU/Linux|SMP (non-64bit) platform fails
Date: Wed, 13 Sep 2006 00:57:00 -0000 [thread overview]
Message-ID: <20060913005652.6622.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29049-13226@http.gcc.gnu.org/bugzilla/>
------- Comment #18 from joseph at codesourcery dot com 2006-09-13 00:56 -------
Subject: Re: New: possible problem: building gcc >= 4.2
on i686 GNU/Linux|SMP (non-64bit) platform fails
On Tue, 12 Sep 2006, WISD00M at GMX dot NET wrote:
> ./xgcc -B./ -B/usr/local/i686-pc-linux-gnu/bin/ -isystem
> /usr/local/i686-pc-linux-gnu/include -isystem
> /usr/local/i686-pc-linux-gnu/sys-include -L/root/gcc-build/gcc/../ld -O2
> -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
> -Wold-style-definition -isystem ./include -I. -I.
> -I../../gcc-4.2-20060906/gcc -I../../gcc-4.2-20060906/gcc/.
> -I../../gcc-4.2-20060906/gcc/../include
> -I../../gcc-4.2-20060906/gcc/../libcpp/include
> -I../../gcc-4.2-20060906/gcc/../libdecnumber -I../libdecnumber -g0
> -finhibit-size-directive -fno-inline-functions -fno-exceptions
> -fno-zero-initialized-in-bss -fno-toplevel-reorder -fno-omit-frame-pointer \
> -c ../../gcc-4.2-20060906/gcc/crtstuff.c -DCRT_BEGIN \
> -o crtbegin.o
If you rerun this manually with -v added to the compiler options, what is
the full output?
What are the contents of configargs.h in the gcc build directory?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29049
next prev parent reply other threads:[~2006-09-13 0:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 23:48 [Bug other/29049] New: " WISD00M at GMX dot NET
2006-09-12 23:53 ` [Bug other/29049] " pinskia at gcc dot gnu dot org
2006-09-12 23:53 ` WISD00M at GMX dot NET
2006-09-12 23:54 ` WISD00M at GMX dot NET
2006-09-12 23:54 ` WISD00M at GMX dot NET
2006-09-12 23:55 ` WISD00M at GMX dot NET
2006-09-12 23:56 ` WISD00M at GMX dot NET
2006-09-12 23:57 ` WISD00M at GMX dot NET
2006-09-12 23:58 ` WISD00M at GMX dot NET
2006-09-13 0:10 ` WISD00M at GMX dot NET
2006-09-13 0:12 ` WISD00M at GMX dot NET
2006-09-13 0:14 ` WISD00M at GMX dot NET
2006-09-13 0:24 ` WISD00M at GMX dot NET
2006-09-13 0:27 ` pinskia at gcc dot gnu dot org
2006-09-13 0:30 ` WISD00M at GMX dot NET
2006-09-13 0:36 ` WISD00M at GMX dot NET
2006-09-13 0:44 ` WISD00M at GMX dot NET
2006-09-13 0:51 ` WISD00M at GMX dot NET
2006-09-13 0:57 ` joseph at codesourcery dot com [this message]
2006-09-13 1:11 ` WISD00M at GMX dot NET
2006-09-13 1:11 ` WISD00M at GMX dot NET
2006-09-13 1:16 ` WISD00M at GMX dot NET
2006-09-13 2:56 ` hjl at lucon dot org
2006-09-13 3:16 ` WISD00M at GMX dot NET
2006-09-13 3:24 ` WISD00M at GMX dot NET
2006-09-13 5:02 ` WISD00M at GMX dot NET
2006-09-13 5:46 ` hjl at lucon dot org
2006-09-13 6:20 ` WISD00M at GMX dot NET
2006-09-13 15:03 ` hjl at lucon dot org
2006-10-24 8:19 ` pinskia at gcc dot gnu dot org
2007-08-02 1:14 ` lauras at gcc dot gnu dot org
2007-08-02 1:14 ` lauras 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=20060913005652.6622.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: link
Be 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).