public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "WISD00M at GMX dot NET" <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 05:02:00 -0000	[thread overview]
Message-ID: <20060913050225.16286.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29049-13226@http.gcc.gnu.org/bugzilla/>



------- Comment #25 from WISD00M at GMX dot NET  2006-09-13 05:02 -------
Just for your info: I just tried to compile the two previous official releases
on the same machine to troubleshoot this issue further (using no configure/make
flags WHATSOEVER, building in a separate build directory in both cases): 

gcc 4.0.3 (347231730fb44b609b69226c3e432d80  gcc-core-4.0.3.tar.bz2) and 
gcc 4.1.0 (15efa164579c7cf4a48859ee87d2a1fa  gcc-core-4.1.0.tar.bz2)

(both obtained from gcc mirrors)

While I did succeed compiling gcc 4.0.3 on the same machine (after however
applying the patch mentioned in bug 27023 due to a too recent GNU make
version), compiling gcc 4.1.0 DID indeed cancel at the same point as the two
later releases did:

/root/tmp/gcc-4.1.0/gcc-4.1.0-BUILD/./gcc/xgcc
-B/root/tmp/gcc-4.1.0/gcc-4.1.0-BUILD/./gcc/
-B/usr/local/i686-pc-linux-gnu/bin/ -B/usr/local/i686-pc-linux-gnu/lib/
-isystem /usr/local/i686-pc-linux-gnu/include -isystem
/usr/local/i686-pc-linux-gnu/sys-include -O2 -O2 -g -O2  -DIN_GCC    -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
 -isystem ./include  -I. -I. -I../../gcc-4.1.0/gcc -I../../gcc-4.1.0/gcc/.
-I../../gcc-4.1.0/gcc/../include -I../../gcc-4.1.0/gcc/../libcpp/include   -g0
-finhibit-size-directive -fno-inline-functions -fno-exceptions
-fno-zero-initialized-in-bss -fno-unit-at-a-time  -fno-omit-frame-pointer \
          -c ../../gcc-4.1.0/gcc/crtstuff.c -DCRT_BEGIN \
          -o crtbegin.o
../../gcc-4.1.0/gcc/crtstuff.c:1: sorry, unimplemented: 64-bit mode not
compiled in
make[2]: *** [crtbegin.o] Error 1
make[2]: Leaving directory `/root/tmp/gcc-4.1.0/gcc-4.1.0-BUILD/gcc'
make[1]: *** [all-gcc] Error 2
make[1]: Leaving directory `/root/tmp/gcc-4.1.0/gcc-4.1.0-BUILD'
make: *** [all] Error 2


So, the cause for this really seems to have crept in somewhere in between 4.0.3
and 4.1.0, thus I ask anybody in the know: were there any additional
dependencies (or default assumptions) introduced in either the underlying build
system or alternatively the xgcc/cc1 files during that time line that could
explain the behaviour I'm seeing here?

Thanks for any further pointers


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29049


  parent reply	other threads:[~2006-09-13  5:02 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
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 [this message]
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=20060913050225.16286.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).