From: Piotr Adam Zolnierczuk <pzolnier@indiana.edu>
To: buildroot@busybox.net
Subject: [Buildroot] static libgcc_s
Date: Wed, 28 Feb 2007 10:51:02 -0500 [thread overview]
Message-ID: <45E5A4E6.3010508@indiana.edu> (raw)
Hi,
I am trying to compile a flash bootloader for a AT91SAM9260EK board on
my Linux box.
When I use gnuarm.org precompiled toolchain (gcc-3.4.3) it works fine,
but when I use my own toolchain
(build by buildroot rev 17875, gcc-4.1.1) it complains about missing
gcc_s (the bootloader wants to use __divsi3 routine).
My toolchain properly builds libgcc_s.so, but for some reasons it does
not build libgcc_s.a. Otherwise the toolchain is fine: builds kernel,
rootfs etc.
Any ideas how can I "force" buildroot to build a static version of libgcc_s?
Thanks
Piotr
next reply other threads:[~2007-02-28 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 15:51 Piotr Adam Zolnierczuk [this message]
2007-02-28 18:37 ` [Buildroot] static libgcc_s Thomas Lundquist
2007-02-28 21:45 ` Erik Andersen
2007-03-01 0:48 ` Piotr Adam Zolnierczuk
2007-03-01 6:13 ` Ulf Samuelsson
2007-03-01 14:42 ` Zolnierczuk, Piotr
2007-03-01 15:58 ` Ulf Samuelsson
2007-03-01 16:20 ` Piotr Adam Zolnierczuk
2007-03-01 16:55 ` Ulf Samuelsson
[not found] <mailman.1.1172692802.12481.buildroot@uclibc.org>
2007-02-28 20:41 ` Zolnierczuk, Piotr
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=45E5A4E6.3010508@indiana.edu \
--to=pzolnier@indiana.edu \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.