From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] enabling libc.a generation
Date: Fri, 04 May 2012 21:55:42 +0200 [thread overview]
Message-ID: <4FA4343E.1090003@mind.be> (raw)
In-Reply-To: <4F9FA29F.90309@scalemp.com>
On 05/01/12 10:45, Eial Czerwacki wrote:
> as for libc.so, here is the relevant output:
> sh-4.1# find . -name "libc*"
> ./lib/libcrypt.so.0
> ./lib/libc.so.0
> ./lib/libcrypt-0.9.32.so
> ./usr/include/bits/libc-lock.h
> ./usr/lib/libcurses.a
Right, so no libc.so or libc.a...
These files are copied into or removed from the target fs depending on
the status of the BR2_HAVE_DEVFILES option. This option must be
enabled, otherwise it is impossible to select the BR2_PACKAGE_GCC_TARGET
option.
However, the copying of libc.so and libc.a happens at the time the
cross-toolchain is built. If you enable BR2_HAVE_DEVFILES afterwards,
it will have no effect. Perhaps you didn't do a clean build after
reconfiguring buildroot?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2012-05-04 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 6:24 [Buildroot] enabling libc.a generation Eial Czerwacki
2012-05-01 8:28 ` Arnout Vandecappelle
2012-05-01 8:45 ` Eial Czerwacki
2012-05-04 19:55 ` Arnout Vandecappelle [this message]
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=4FA4343E.1090003@mind.be \
--to=arnout@mind.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox