From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] lightning: Added package
Date: Tue, 12 Aug 2014 12:10:15 +0300 [thread overview]
Message-ID: <20140812091015.GB20528@tarshish> (raw)
In-Reply-To: <53E625E3.7030707@crapouillou.net>
Hi Paul,
On Sat, Aug 09, 2014 at 03:45:07PM +0200, Paul Cercueil wrote:
> Le 06/08/2014 05:12, Baruch Siach a ?crit :
> >On Wed, Aug 06, 2014 at 01:00:10AM +0200, Paul Cercueil wrote:
> >>+ifeq ($(BR2_PACKAGE_BINUTILS),y)
> >>+LIGHTNING_DEPENDENCIES += binutils
> >>+LIGHTNING_CONF_OPT += --enable-disassembler
> >>+endif
> >
> >Have you tested external toolchains?
>
> No I did not, as I don't use one. Furthermore, I only tested the package on
> mipsel, the list of archs specified in this package is taken from
> lightning's web page and may be incorrect (hopefully not).
You can easily test external toolchains using the minimal configs at
http://autobuild.buildroot.net/toolchains/configs/. You'll also find a few
mipsel variants there.
If this package is not compatible with external toolchain (and so I suspect)
then it should depend on BR2_TOOLCHAIN_BUILDROOT.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2014-08-12 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 23:00 [Buildroot] [PATCH 1/2] binutils: Also install libopcodes in staging Paul Cercueil
2014-08-05 23:00 ` [Buildroot] [PATCH 2/2] lightning: Added package Paul Cercueil
2014-08-06 3:12 ` Baruch Siach
2014-08-09 13:45 ` Paul Cercueil
2014-08-12 9:10 ` Baruch Siach [this message]
2014-08-12 16:53 ` Thomas Petazzoni
2015-01-02 18:16 ` Thomas Petazzoni
2015-01-02 18:15 ` [Buildroot] [PATCH 1/2] binutils: Also install libopcodes in staging 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=20140812091015.GB20528@tarshish \
--to=baruch@tkos.co.il \
--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