* gcc 3.1 produces bus errors on arm-linux
@ 2002-10-21 6:00 Nick Patavalis
0 siblings, 0 replies; 5+ messages in thread
From: Nick Patavalis @ 2002-10-21 6:00 UTC (permalink / raw)
To: tobias; +Cc: gcc-help
Hi,
I was scanning mailing lists for something related to my problem, and
came upon a posting by Tobias Hunger at the gcc-help mailing list (31
Jul 2002, http://gcc.gnu.org/ml/gcc-help/2002-07/msg00296.html)
The problem I'm witnessing is exactly the same as the one described in
the above-mentioned post (trying to run any binary that requires a
glibc 2.2.[35] compiled with gcc 3.1, causes a segfault; static
binaries work fine). Since from the followups at the list I could not
see any resolution, I tought I'd write to ask if any progress has been
made with this.
Thanks in advance
/npat
Nick Patavalis
inAccess Networks S.A.
--
A commune is where people join together to share their lack of wealth.
-- Richard M. Stallman
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: gcc 3.1 produces bus errors on arm-linux
2002-07-31 7:51 Tobias Hunger
2002-07-31 7:55 ` Momchil Velikov
@ 2002-07-31 9:38 ` Tobias Hunger
1 sibling, 0 replies; 5+ messages in thread
From: Tobias Hunger @ 2002-07-31 9:38 UTC (permalink / raw)
To: gcc-help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I just tried the normal, unpatched gcc 3.1.1 code. Same problem:-( glibc
compiles, everything using it gives a bus error on my sharp Zaurus.
- --
Gruss,
Tobias
- ------------------------------------------------------------
Tobias Hunger The box said: 'Windows 95 or better'
tobias@fresco.org So I installed Linux.
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9SBKFv0FZW3NyoqURAo2QAKCS1dDox5XGOq3dKKY2GlbMHNYZjgCfSsri
QbCsJ1PrP0KPq8l6YIb5RjU=
=3fJU
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: gcc 3.1 produces bus errors on arm-linux
2002-07-31 7:55 ` Momchil Velikov
@ 2002-07-31 8:01 ` Tobias Hunger
0 siblings, 0 replies; 5+ messages in thread
From: Tobias Hunger @ 2002-07-31 8:01 UTC (permalink / raw)
To: Momchil Velikov; +Cc: gcc-help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 31 July 2002 16:55, Momchil Velikov wrote:
> >>>>> "Tobias" == Tobias Hunger <tobias@fresco.org> writes:
>
> Tobias> configure -target=arm-linux --host=i686-linux \
> ^^
> You actually configured like this or a typo?
Sorry, cut'n'paste error. I of course used --target.
- --
Gruss,
Tobias
- ------------------------------------------------------------
Tobias Hunger The box said: 'Windows 95 or better'
tobias@fresco.org So I installed Linux.
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9R/u4v0FZW3NyoqURAtrPAJ9Vb6Psg/DVWz5lbGxSEdPTFjVQYACffDwi
gBfa1NL9bottSnpgF+0Lwu0=
=9o7b
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: gcc 3.1 produces bus errors on arm-linux
2002-07-31 7:51 Tobias Hunger
@ 2002-07-31 7:55 ` Momchil Velikov
2002-07-31 8:01 ` Tobias Hunger
2002-07-31 9:38 ` Tobias Hunger
1 sibling, 1 reply; 5+ messages in thread
From: Momchil Velikov @ 2002-07-31 7:55 UTC (permalink / raw)
To: Tobias Hunger; +Cc: gcc-help
>>>>> "Tobias" == Tobias Hunger <tobias@fresco.org> writes:
Tobias> configure -target=arm-linux --host=i686-linux \
^^
You actually configured like this or a typo?
~velco
^ permalink raw reply [flat|nested] 5+ messages in thread
* gcc 3.1 produces bus errors on arm-linux
@ 2002-07-31 7:51 Tobias Hunger
2002-07-31 7:55 ` Momchil Velikov
2002-07-31 9:38 ` Tobias Hunger
0 siblings, 2 replies; 5+ messages in thread
From: Tobias Hunger @ 2002-07-31 7:51 UTC (permalink / raw)
To: gcc-help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
I successfully managed to build a crosscompiling gcc from i686-linux to
arm-linux.
Using the sources from here:
ftp://ftp.de.debian.org/debian/pool/main/g/gcc-3.1/gcc-3.1_3.1.1ds2.orig.tar.gz
ftp://ftp.de.debian.org/debian/pool/main/g/gcc-3.1/gcc-3.1_3.1.1ds2-0pre3.diff.gz
I used these configure options to build a cross-gcc:
configure -target=arm-linux --host=i686-linux \
--build=i686-linux \
--prefix=/path \
--enable-languages=c \
--disable-threads \
--disable-shared
Then I build glibc (sources from today's CVS), using these configure args:
configure \
--host arm-linux --build i686-linux \
--disable-profile \
--enable-add-ons \
--prefix=/usr \
--infodir=/usr/share/info \
--libdir=/lib \
--mandir=/usr/share/man \
--enable-shared \
--with-headers=/path/linux/include
This gives me a nice little libc that I then install to my Zaurus. ldconfig
finds them all right. Any application I start from that moment on gives me a
Bus error. I tried diffrent versions of glibc (2.2.4 and 2.2.5), all show the
same behaviour. I further tried diffrent optimization flags (-march=rmv4
- -mtune=strongarm1100 -mapcs-32 -fexpensive-optimizations -fomit-frame-pointer
- -O3 down to no extra flags at all). The same sources of glibc work fine with
the gcc-2.95.x toolchains you can download. So my guess is that gcc 3.1(.1)
produces buggy code. How can I further debug this? Any ideas?
- --
Gruss,
Tobias
- ------------------------------------------------------------
Tobias Hunger The box said: 'Windows 95 or better'
tobias@fresco.org So I installed Linux.
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9R/lrv0FZW3NyoqURAnSxAJ49uOZQU+Ci5mcT7fCA0tWC7ultZgCfX23u
y/7MPgNrr/7AJa7xgzzoXKo=
=Dzfj
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2002-10-21 13:00 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-10-21 6:00 gcc 3.1 produces bus errors on arm-linux Nick Patavalis
-- strict thread matches above, loose matches on Subject: below --
2002-07-31 7:51 Tobias Hunger
2002-07-31 7:55 ` Momchil Velikov
2002-07-31 8:01 ` Tobias Hunger
2002-07-31 9:38 ` Tobias Hunger
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).