From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to choose C library dependencies
Date: Mon, 16 May 2016 23:19:22 +0200 [thread overview]
Message-ID: <20160516231922.7ebb515f@free-electrons.com> (raw)
In-Reply-To: <4904ae0d-f790-063e-a365-675596985f02@mind.be>
Hello,
On Sun, 15 May 2016 01:54:07 +0200, Arnout Vandecappelle wrote:
> > I want to compile ejabberd and run it on my router. I choose erlang package with
> > SMP support and all modules and ejabberd package, does not configure defconfig.
> > Then I run /make ejabberd/, copy ejabberd, erlang and busybox from /target/
> > folder to router and run it.
>
> Buildroot in't really meant for that kind of scenario. That said, it should be
> possible to do it. Basically you must create a toolchain that matches exactly
> with what is already installed on the target.
Or:
1/ Use a statically linked binary.
2/ Use a chroot.
In both cases, you must make sure that the C library uses kernel
headers that are at least as old at the kernel running on your target.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-16 21:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 9:58 [Buildroot] Clarification about init system Marco Trapanese
2016-05-11 7:29 ` Peter Korsgaard
2016-05-14 3:59 ` [Buildroot] How to choose C library dependencies Илья Валеев
2016-05-14 23:54 ` Arnout Vandecappelle
2016-05-16 12:32 ` Илья Валеев
2016-05-16 21:15 ` Arnout Vandecappelle
2016-05-18 19:55 ` Илья Валеев
2016-05-16 21:19 ` Thomas Petazzoni [this message]
2016-05-18 19:57 ` Илья Валеев
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=20160516231922.7ebb515f@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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.