From: Bjorn De Sutter <brdsutte@frodo.elis.rug.ac.be>
To: gdb@sources.redhat.com
Subject: problems cross-compiling gcc + uClibc + gdb
Date: Fri, 18 Apr 2003 00:32:00 -0000 [thread overview]
Message-ID: <Pine.OSF.3.91.1030418021220.35616A-100000@frodo.elis.rug.ac.be> (raw)
Hi,
on an i386 linux system, I've cross-compiled gcc and newlib as follows:
../gcc-3.2.2/configure --prefix=/home/brdsutte/embedded/build-gcc --enable-target-optspace --with-newlib --target=arm-elf
gmake all install
Then, I've build uClibc with CROSS=arm-elf- as follows:
make KERNEL_SOURCE=/home/brdsutte/embedded/linux TARGET_ARCH=arm
the linux kernel I used for that compilation (i.e. who's headers are
used during the compilation of uClibc) was a standard linux 2.4.19,
patched with patch-2.4.19-rmk7 for the arm, and then configured for
arm-integrator
I then compiled gdb as follows:
../gdb+dejagnu-20030417/configure --prefix=/home/brdsutte/embedded/build-gdb --target=arm-elf
gmake all install
When I run a hello world program that I compiled with arm-elf-gcc using
arm-elf-gdb, everything works all right, but when I compile the same
program with arm-uclibc-gcc, trying to run the program results in the
following:
[brdsutte@elrond vb]$ arm-linux-run b.out
sim: unknown SWI encountered - 900036 - ignoring
One of the differences between the two version of the programs is that
the newlib version only contains system calls swi 0x00123456, while
the uClibc version contains system calls such as swi 0x00900001
Is there a way to have gdb handle these system calls, or do I need to
change the way system calls are implemented in uClibc?
I am not on this mailing list, so please respond to my emailaddress as
well.
Thanks in advance,
Bjorn De Sutter
Postdoctoral Fellow of the Fund for Scientific Research -- Flanders
affiliated with Ghent University, currently at IBM TJ Watson Research Lab
brdsutte@elis.ugent.be http://www.elis.ugent.be/~brdsutte/
next reply other threads:[~2003-04-18 0:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 0:32 Bjorn De Sutter [this message]
2003-04-18 0:46 ` Daniel Jacobowitz
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=Pine.OSF.3.91.1030418021220.35616A-100000@frodo.elis.rug.ac.be \
--to=brdsutte@frodo.elis.rug.ac.be \
--cc=gdb@sources.redhat.com \
/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).