From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain: add support for glibc
Date: Fri, 23 Aug 2013 06:48:45 +0200 [thread overview]
Message-ID: <20130823064845.2ec4800d@skate> (raw)
In-Reply-To: <52169E42.2040904@mind.be>
Dear Arnout Vandecappelle,
On Fri, 23 Aug 2013 01:26:58 +0200, Arnout Vandecappelle wrote:
> > I don't know for sure, but the package aren't that complex, so I don't
> > think merging would be very difficult.
> >
> > If I had to merge them, where should I put the common code?
>
> I was thinking to have just one glibc package, with a choice to select
> eglibc or glibc.
Well, I still would like the libc selection to be uClibc/glibc/eglibc
in the choice in toolchain/toolchain-buildroot/Config.in. But I guess I
can probably make BR2_TOOLCHAIN_BUILDROOT_LIBC be equal to "glibc" in
both the glibc and eglibc case, which would be sufficient to make the
toolchain building logic use the "glibc" and "glibc-configure" targets
for both the eglibc and glibc selections.
Want me to rework the patch in this direction?
Note that later on, if we support several versions of glibc and eglibc,
then package/glibc/Config.in would look like:
if BR2_TOOLCHAIN_BUILDROOT_EGLIBC
... versions of eglibc ...
endif
if BR2_TOOLCHAIN_BUILDROOT_GLIBC
... versions of glibc ...
endif
> >> Shouldn't this lib be installed as well for a gdb without gdbserver?
> >> I.e., shouldn't the condition be ifeq ($(BR2_PACKAGE_GDB),y)?
> >
> > That's a good question, I don't know. At the moment, the ct-ng backend,
> > the external backend and the eglibc .mk file all copy libthread_db.so
> > when gdbserver is enabled.
>
> To be tested but it'd surprise me if gdb didn't need it.
I agree, it would have to be tested.
Thanks for your feedback,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-08-23 4:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-18 17:36 [Buildroot] [PATCH] toolchain: add support for glibc Thomas Petazzoni
2013-08-21 21:45 ` Arnout Vandecappelle
2013-08-22 21:26 ` Thomas Petazzoni
2013-08-22 23:26 ` Arnout Vandecappelle
2013-08-23 4:48 ` Thomas Petazzoni [this message]
2013-08-28 20:16 ` Arnout Vandecappelle
2013-08-29 7:38 ` Thomas Petazzoni
2013-08-29 15:54 ` Arnout Vandecappelle
2013-08-30 7:46 ` Thomas Petazzoni
2013-08-21 21:52 ` Arnout Vandecappelle
2013-08-22 19:42 ` 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=20130823064845.2ec4800d@skate \
--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