Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lzo: security bump to version 2.07
Date: Fri, 27 Jun 2014 20:36:13 +0200	[thread overview]
Message-ID: <20140627203613.09a7b284@free-electrons.com> (raw)
In-Reply-To: <877g42la16.fsf@dell.be.48ers.dk>

Dear Peter Korsgaard,

On Fri, 27 Jun 2014 16:08:53 +0200, Peter Korsgaard wrote:

>  >>>> lzo 2.07 Patching libtool
> 
>  > Applying buildroot-libtool-v2.4.patch using patch: patching file ltmain.sh
>  > Hunk #1 FAILED at 1416.
>  > Hunk #2 FAILED at 2962.
>  > Hunk #3 succeeded at 7964 with fuzz 2 (offset 1281 lines).
>  > Hunk #4 succeeded at 10554 (offset 1297 lines).
>  > 2 out of 4 hunks FAILED -- saving rejects to file ltmain.sh.rej
>  > Patch failed!  Please fix buildroot-libtool-v2.4.patch!
> 
>  > Should I rephrase the comment?
> 
> Yes, please. I guess it is because it uses a too new libtool version?

The libtool script bundled with this package uses "libtool 2.4.2.418",
which we have identified (with Hadrien) as requiring a different patch
that other libtool versions, including libtool 2.4.2. That's something
we will try to work out with Hadrien.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2014-06-27 18:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27  4:32 [Buildroot] [PATCH] lzo: security bump to version 2.07 Baruch Siach
2014-06-27 11:07 ` Peter Korsgaard
2014-06-27 11:26   ` Baruch Siach
2014-06-27 14:08     ` Peter Korsgaard
2014-06-27 18:36       ` Thomas Petazzoni [this message]

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=20140627203613.09a7b284@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