From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] uclibc config changes and cross-compiler
Date: Mon, 24 Jan 2011 17:02:56 +0100 [thread overview]
Message-ID: <20110124170256.4cbf2e10@surf> (raw)
In-Reply-To: <AANLkTi=e=ncL_G+F0iH5Dia+N2iBHi=x8EA9bsw6=uhO@mail.gmail.com>
On Fri, 21 Jan 2011 10:46:48 +0300
Sergey Naumov <sknaumov@gmail.com> wrote:
> Does anybody know whether changes in uclibc.conf when cross-compiler
> is already built can lead to unrunnable programs?
I don't think there is an uclibc.conf file, but I assume you're talking
about uClibc .config file.
> For example, we made a toolchain with certain uclibc features. Then we
> decided to add/remove some programs from our build so we need
> additional/no longer need some uclibc features. Is it safe to rebuild
> only uclibc in this case, or we also have to rebuild compiler?
I am not an uClibc expert, but my understanding is that uClibc does not
provide ABI compatibility between versions and configurations.
Therefore, you cannot assume that programs compiled against version
A/configuration A of uClibc will work properly with version
B/configuration B of uClibc.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2011-01-24 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 7:46 [Buildroot] uclibc config changes and cross-compiler Sergey Naumov
2011-01-24 16:02 ` Thomas Petazzoni [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=20110124170256.4cbf2e10@surf \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox