All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libunwind:  new pacakge
Date: Tue, 25 Jun 2013 23:50:22 +0200	[thread overview]
Message-ID: <20130625235022.75b13738@skate> (raw)
In-Reply-To: <F9C551623D2CBB4C9488801D14F864C639A6F946@ex-mb1.corp.adtran.com>

Dear ANDY KENNEDY,

On Tue, 25 Jun 2013 21:41:44 +0000, ANDY KENNEDY wrote:

> +config BR2_PACKAGE_LIBUNWIND
> +	bool "libunwind"
> +	help
> +	  C API to determine the call-chain of a program.
> +
> +	  Project home:  <http://www.nongnu.org/libunwind/index.html>

No need to indicate "Project home:", just:

	  http://www.nongnu.org/libunwind/index.html

Also:

 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.

 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 || ..."

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-06-25 21:50 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 [this message]
2013-06-25 21:57   ` ANDY KENNEDY
2013-06-25 22:04     ` Thomas Petazzoni
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=20130625235022.75b13738@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 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.