From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] using buildroot to statically build uclibc
Date: Sat, 12 Sep 2015 16:06:05 +0200 [thread overview]
Message-ID: <55F4314D.80606@mind.be> (raw)
In-Reply-To: <CAEjFr-Zk4HTs7NPYOtheUzGbHVtZmmAb5daRR_MrW4yS22daGA@mail.gmail.com>
On 11-09-15 11:50, Doha Ehab wrote:
> Hello ,
> I am trying to statically build uclibc using buildroot to use it to cross
> compile mpich . when I generate uclibc toolchain using make menuconfig the
> executables in output/usr/host/bin are dynamically linked .
output/usr/host/bin contains executables for the host. These are linked
dynamically and have an rpath setting to make sure the correct libraries are
found in output/usr/host/lib.
The executables on the target (output/target and output/images) should be
statically linked.
There is no way in buildroot to link the host binaries statically.
Regards,
Arnout
> do I have to build uclibc from output/build/toolchain folder in order to get the
> statically linked executables .
> I'm new to this if I'm missing something kindly direct me .
>
> Regards,
> Doha
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
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: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-09-12 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 9:50 [Buildroot] using buildroot to statically build uclibc Doha Ehab
2015-09-11 13:36 ` Thomas Petazzoni
2015-09-12 9:57 ` Doha Ehab
2015-09-12 14:06 ` Arnout Vandecappelle [this message]
2015-09-12 16:53 ` Doha Ehab
2015-09-13 21:23 ` Thomas Petazzoni
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=55F4314D.80606@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