From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-03-18
Date: Thu, 19 Mar 2015 13:23:09 +0100 [thread overview]
Message-ID: <20150319132309.285f72de@free-electrons.com> (raw)
In-Reply-To: <550AB83E.5050400@imgtec.com>
Dear Vicente Olivert Riera,
On Thu, 19 Mar 2015 12:51:26 +0100, Vicente Olivert Riera wrote:
> Yes, I agree with that. Perhaps you could ask lua-periphery upstream and
> tell them to not do that :P
Well, you can create a c-periphery package, which lua-periphery depends
on, and then pass the appropriate C_PERIPHERY / C_PERIPHERY_LIB values
when building lua-periphery.
Maybe Fran?ois could have a look into this?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-19 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-03-18 Thomas Petazzoni
2015-03-19 10:17 ` Vicente Olivert Riera
2015-03-19 10:30 ` Baruch Siach
2015-03-19 11:51 ` Vicente Olivert Riera
2015-03-19 12:23 ` Thomas Petazzoni [this message]
2015-03-19 20:30 ` François Perrad
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=20150319132309.285f72de@free-electrons.com \
--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.