[Bug bootstrap/50646] configure detects big endian on little endian system.

2013-11-10 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50646 Andrew Pinski changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug bootstrap/50646] configure detects big endian on little endian system.

2011-10-09 Thread fzvqedi at v dot mintemail.com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50646 --- Comment #6 from Roger Meyer 2011-10-09 23:34:47 UTC --- the host system is aboriginal linux 1.03 armv6l (little endian) using gcc 4.2.1 on qemu somehow configure seems to think that the used compiler is a crosscompiler, but i have no idea why

[Bug bootstrap/50646] configure detects big endian on little endian system.

2011-10-07 Thread sch...@linux-m68k.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50646 --- Comment #5 from Andreas Schwab 2011-10-07 22:30:14 UTC --- *** Bug 50647 has been marked as a duplicate of this bug. ***

[Bug bootstrap/50646] configure detects big endian on little endian system.

2011-10-07 Thread sch...@linux-m68k.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50646 --- Comment #4 from Andreas Schwab 2011-10-07 22:27:41 UTC --- Your bootstrap compiler must be broken, because the test is correctly implemented: a successful run of the test program means little endian. Since the test exited with non-zero exit

[Bug bootstrap/50646] configure detects big endian on little endian system.

2011-10-07 Thread joseph at codesourcery dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50646 --- Comment #3 from joseph at codesourcery dot com 2011-10-07 21:46:20 UTC --- Until comparatively recently, the only thing that cared about host endianness was decimal floating-point support. However, now the lexer cares as well. What is the

[Bug bootstrap/50646] configure detects big endian on little endian system.

2011-10-07 Thread fzvqedi at v dot mintemail.com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50646 --- Comment #2 from Roger Meyer 2011-10-07 20:50:23 UTC --- indeed, it would cause problems. i.e. compile some stuff with wrong endianness and later silently crash. in this specific case here the build stops later on on another error, caused by