From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libunwind: new pacakge
Date: Wed, 26 Jun 2013 00:04:30 +0200 [thread overview]
Message-ID: <20130626000430.502a306a@skate> (raw)
In-Reply-To: <F9C551623D2CBB4C9488801D14F864C639A6F98F@ex-mb1.corp.adtran.com>
Dear ANDY KENNEDY,
On Tue, 25 Jun 2013 21:57:14 +0000, ANDY KENNEDY wrote:
> > 1) Did you check that it builds fine with uClibc? This kind of library
> > tend to use some funky C library features, sometimes not available in
> > uClibc.
>
> Nope, I didn't.
Then just do a build with a uClibc toolchain. If you don't want to wait
for the toolchain to build, you can use
http://autobuild.buildroot.org/toolchains/tarballs/br-arm-basic-2013.05-1.tar.bz2
as an external toolchain. It's a basic ARM uClibc toolchain (with no
option enabled: no WCHAR, no largefile, no IPv6, no RPC, no locales).
> > 2) The libunwind code seems to contain some architecture-specific
> > code. While aarch64, arm, mips, ppc, sh, x86 and x86-64 are supported,
> > some other architectures that Buildroot supports are not supported. So
> > maybe this package should have a "depends on BR2_aarch64 || BR2_arm ||
> > BR2_armeb || ..."
>
> That is possible as well. I'm really not devoted to owning this
> package that much. I was merely attempting to push it back as I
> added it to our usage of BuildRoot. To that end, shall I abandon
> the process (as I clearly am not willing to do it justice)?
No, you shouldn't abandon the process. Your contributions are very
welcome! I think you're very close to have something that can be
merged, just keep sending new revisions of your patch that takes into
account the comments from contributors.
> It is no skin off my nose whether it gets put into BuildRoot, I was
> only pushing it back as I didn't know it was there until someone else
> I work with pointed out that this *seems* to be the basic library GDB
> is based off of, thus could be useful in our embedded system.
Yes, it would certainly be useful.
Best regards,
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-06-25 22:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 21:41 [Buildroot] [PATCH] libunwind: new pacakge ANDY KENNEDY
2013-06-25 21:50 ` Thomas Petazzoni
2013-06-25 21:57 ` ANDY KENNEDY
2013-06-25 22:04 ` Thomas Petazzoni [this message]
2013-06-27 20:32 ` ANDY KENNEDY
2013-06-26 15:26 ` Sven Neumann
2013-06-25 21:59 ` Yann E. MORIN
2013-07-28 16:22 ` 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=20130626000430.502a306a@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