From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] perl-net-ssleay: fix build
Date: Sat, 16 Aug 2014 09:28:04 +0200 [thread overview]
Message-ID: <20140816092804.14c79131@free-electrons.com> (raw)
In-Reply-To: <1408173070-18811-1-git-send-email-francois.perrad@gadz.org>
Dear Francois Perrad,
On Sat, 16 Aug 2014 09:11:10 +0200, Francois Perrad wrote:
> the new option OPTIMIZE needs the same replacement.
>
> see http://autobuild.buildroot.net/results/278f9d121273a16cedc009c0b8df0a8659d8fb73/
>
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
> package/perl-net-ssleay/perl-net-ssleay.mk | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-08-16 7:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 7:11 [Buildroot] [PATCH] perl-net-ssleay: fix build Francois Perrad
2014-08-16 7:28 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-03 13:31 Francois Perrad
2014-07-03 14:34 ` Peter Korsgaard
2014-07-03 18:13 ` 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=20140816092804.14c79131@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox