From: Tobias Hunger <tobias@fresco.org>
To: gcc-help@gcc.gnu.org
Subject: gcc 3.1 produces bus errors on arm-linux
Date: Wed, 31 Jul 2002 07:51:00 -0000 [thread overview]
Message-ID: <200207311651.26912.tobias@fresco.org> (raw)
-----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-----
next reply other threads:[~2002-07-31 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 7:51 Tobias Hunger [this message]
2002-07-31 7:55 ` Momchil Velikov
2002-07-31 8:01 ` Tobias Hunger
2002-07-31 9:38 ` Tobias Hunger
2002-10-21 6:00 Nick Patavalis
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=200207311651.26912.tobias@fresco.org \
--to=tobias@fresco.org \
--cc=gcc-help@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).