From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] cannot compile a program within a uclibc build chroot
Date: Thu, 01 Nov 2012 11:14:49 +0100 [thread overview]
Message-ID: <50924B99.5080605@mind.be> (raw)
In-Reply-To: <50921F41.6040502@scalemp.com>
On 11/01/12 08:05, Eial Czerwacki wrote:
> 09:03:00 $ find root -name "libc*"
> find: root/lost+found: Permission denied
> root/usr/include/bits/libc-lock.h
> _root/usr/lib/libc.a_
> root/usr/lib/libcrypt_pic.a
> root/usr/lib/libc_pic.a
> root/usr/lib/libcurses.a
> root/usr/lib/libcrypt.a
>
> from what I can understand, although I've marked it to be static as possible, not all packages can be linked to static
> libs, gcc is an example as it needs libc.so.0 rather than libc.a
(it's actually as (from binutils), not gcc).
Good catch! With PREFER_STATIC, buildroot's uClibc doesn't install in the target.
I'll post an untested patch as a follow-up, can you test it?
Note: the other part of the problem is that binutils sets --enable-shared
unconditionally. But there may be other reasons for that.
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
next prev parent reply other threads:[~2012-11-01 10:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 15:11 [Buildroot] cannot compile a program within a uclibc build chroot Eial Czerwacki
2012-10-31 22:09 ` Arnout Vandecappelle
2012-11-01 6:01 ` Eial Czerwacki
2012-11-01 6:10 ` Baruch Siach
2012-11-01 6:18 ` Eial Czerwacki
2012-11-01 6:58 ` Baruch Siach
2012-11-01 7:05 ` Eial Czerwacki
2012-11-01 10:14 ` Arnout Vandecappelle [this message]
2012-11-01 10:15 ` [Buildroot] [PATCH] uClibc: install libc.so even if BR2_PREFER_STATIC_LIB is enabled Arnout Vandecappelle
2012-11-01 11:28 ` Eial Czerwacki
2012-11-02 22:17 ` Thomas Petazzoni
2012-11-03 23:28 ` Arnout Vandecappelle
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=50924B99.5080605@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