public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "robert dot schweikert at abaqus dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/13747] New: latest 3.4 snapshot (20040114) fails to build on x86_64 with SUSE 9.0 Date: Mon, 19 Jan 2004 21:17:00 -0000 [thread overview] Message-ID: <20040119211717.13747.robert.schweikert@abaqus.com> (raw) The current version of gcc on the system: -> gcc --version gcc (GCC) 3.3.1 (SuSE Linux) -> make --version GNU Make 3.80 -> autoconf --version autoconf (GNU Autoconf) 2.57 The configure script was run as follows -> ./configure --prefix=/scratch/wdir/rjschwei/local The process produced the following output: creating cache ./config.cache checking host system type... x86_64-unknown-linux-gnu checking target system type... x86_64-unknown-linux-gnu checking build system type... x86_64-unknown-linux-gnu checking for a BSD compatible install... /usr/bin/install -c checking for x86_64-unknown-linux-gnu-ar... no checking for ar... ar checking for x86_64-unknown-linux-gnu-as... no checking for as... as checking for x86_64-unknown-linux-gnu-dlltool... no checking for dlltool... dlltool checking for x86_64-unknown-linux-gnu-ld... /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.1/../../../../x86_64-suse-linux/bin/ld checking for x86_64-unknown-linux-gnu-configno checking for nm... nm checking for x86_64-unknown-linux-gnu-ranlib... no checking for ranlib... ranlib checking for x86_64-unknown-linux-gnu-windres... no checking for windres... windres checking for x86_64-unknown-linux-gnu-objcopy... no checking for objcopy... objcopy checking for x86_64-unknown-linux-gnu-objdump... no checking for objdump... objdump checking for x86_64-unknown-linux-gnu-ar... no checking for ar... ar checking for x86_64-unknown-linux-gnu-as... no checking for as... as checking for x86_64-unknown-linux-gnu-dlltool... no checking for dlltool... dlltool checking for x86_64-unknown-linux-gnu-ld... no checking for ld... ld checking for x86_64-unknown-linux-gnu-nm... no checking for nm... nm checking for x86_64-unknown-linux-gnu-ranlib... no checking for ranlib... ranlib checking for x86_64-unknown-linux-gnu-windres... no checking for windres... windres checking whether to enable maintainer-specific portions of Makefiles... no updating cache ./config.cache creating ./config.status creating Makefile nfigure:3931: checking for x86_64-unknown-linux-gnu-windres configure:3964: checking for windres configure:4031: checking whether to enable maintainer-specific portions of Makefiles running make results in the following failure: configure: loading cache ./config.cache configure: error: `CC' has changed since the previous run: configure: former value: gcc configure: current value: /var/wdir/rjschwei/local/gcc-3.4-20040114/gcc/xgcc -B/var/wdir/rjschwei/local/gcc-3.4-20040114/gcc/ -B/scratch/wdir/rjschwei/local/x86_64-unknown-linux-gnu/bin/ -B/scratch/wdir/rjschwei/local/x86_64-unknown-linux-gnu/lib/ -isystem /scratch/wdir/rjschwei/local/x86_64-unknown-linux-gnu/include -isystem /scratch/wdir/rjschwei/local/x86_64-unknown-linux-gnu/sys-include configure: error: `CFLAGS' has changed since the previous run: configure: former value: -g -O2 configure: current value: -O2 -g -O2 configure: error: `CPPFLAGS' was not set in the previous run configure: error: `LDFLAGS' was not set in the previous run configure: error: `target_alias' was set to `x86_64-unknown-linux-gnu' in the previous run configure: error: changes in the environment can compromise the build configure: error: run `make distclean' and/or `rm ./config.cache' and start over make: *** [configure-target-libiberty] Error 1 I can provide the whole build log if needed. Robert -- Summary: latest 3.4 snapshot (20040114) fails to build on x86_64 with SUSE 9.0 Product: gcc Version: 3.4.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: robert dot schweikert at abaqus dot com CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13747
next reply other threads:[~2004-01-19 21:17 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-19 21:17 robert dot schweikert at abaqus dot com [this message] 2004-01-19 21:43 ` [Bug bootstrap/13747] " dhazeghi at yahoo dot com 2004-01-20 3:44 ` pinskia at gcc dot gnu dot org 2004-01-20 8:26 ` dhazeghi at yahoo dot com 2004-01-20 9:01 ` ch dot ehrlicher at gmx dot de 2004-01-20 16:10 ` [Bug bootstrap/13747] latest 3.4 snapshot (20040114) fails to build with SUSE 8.x/9.0 dhazeghi at yahoo dot com 2004-01-21 16:04 ` ch dot ehrlicher at gmx dot de 2004-01-21 16:10 ` [Bug bootstrap/13747] fail to build in source directory pinskia at gcc dot gnu dot org 2004-01-21 20:43 ` ch dot ehrlicher at gmx dot de 2004-01-21 20:52 ` bangerth at dealii dot org 2004-01-22 16:16 ` robert dot schweikert at abaqus dot com 2004-01-22 16:28 ` pinskia at gcc dot gnu dot org 2004-01-22 16:43 ` robert dot schweikert at abaqus dot com 2004-01-22 16:57 ` pinskia at gcc dot gnu dot org 2004-01-22 21:13 ` robert dot schweikert at abaqus dot com 2004-01-22 22:03 ` dhazeghi at yahoo dot com 2004-02-03 16:07 ` robert dot schweikert at abaqus dot com 2004-02-03 16: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=20040119211717.13747.robert.schweikert@abaqus.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).