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 v2 1/3] core/pkg-autotools: don't use APPLY_PATCHES for libtool patches
Date: Thu, 18 Aug 2016 23:59:43 +0200	[thread overview]
Message-ID: <20160818235943.715ce4c4@free-electrons.com> (raw)
In-Reply-To: <1471449670-13421-1-git-send-email-romain.naour@gmail.com>

Hello,

On Wed, 17 Aug 2016 18:01:08 +0200, Romain Naour wrote:
> Since [1] <package>-reconfigure target is broken.
> 
> $ make elementary-reconfigure
> Applying buildroot-libtool-v2.4.4.patch using patch:
> Error: duplicate filename 'buildroot-libtool-v2.4.4.patch'
> Conflicting files are:
>   already applied: buildroot/support/libtool/buildroot-libtool-v2.4.4.patch
>   to be applied  : buildroot/support/libtool/buildroot-libtool-v2.4.4.patch
> 
> When a package uses AUTORECONF, the libtool patch can be applied a
> second time on the same ltmain.sh in the same directory as the
> <package>-reconfigure target is called. This is not a problem since
> autoreconf will overwrite the previously patched files. But with the
> check introduced by [1], apply-patches.sh throw an error when the
> package is reconfigured since the libtool patch is already present in
> .applied_patches_list.
> 
> In addition to this, the .applied_patches_list file generated by
> apply-patches.sh while patching ltmain.sh is not in the top-level
> package source directory. Instead a duplicated .applied_patches_list
> is generated beside the patched ltmain.sh which can be in a
> subdirectory.
> 
> As noticed by Arnout Vandecappelle [2], the apply-patches.sh script
> doesn't bring anything for the libtool patches.
> 
> "apply_patches.sh does the following:
> 
> * It handles directories -> not needed here.
> * It handles compressed patches and tarballs -> not needed.
> * It handles series files -> not needed.
> * It handles errors in case of multiple patches -> not needed since
> it's only one patch.
> * It detects errors based on *.rej files -> not needed since it's only
> a single patch so patch exit code is OK.
> * It writes the patch list -> for libtool, this is quite silly because
> it will be written in the directory where ltmain.sh is found, not in the
> top-level directory, so you have these patch lists spread over the
> source tree."
> 
> So use patch directly rather than apply-patches.
> 
> [1] 19241598147e7555dce40b6dd44b28ef22b67ed9
> [2] http://lists.busybox.net/pipermail/buildroot/2016-August/169810.html
> 
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Arnout Vandecappelle <arnout@mind.be>
> ---
> v2: improve the commit log (Arnout)
> ---
>  package/pkg-autotools.mk | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)

Applied to master, thanks.

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

      parent reply	other threads:[~2016-08-18 21:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17 16:01 [Buildroot] [PATCH v2 1/3] core/pkg-autotools: don't use APPLY_PATCHES for libtool patches Romain Naour
2016-08-17 16:01 ` [Buildroot] [PATCH v2 2/3] docs: update legal-notice.txt Romain Naour
2016-08-17 17:19   ` Yann E. MORIN
2016-08-19 14:20   ` Thomas Petazzoni
2016-08-17 16:01 ` [Buildroot] [PATCH v2 3/3] docs: libtool patches are not handled by legal-info infrastructure Romain Naour
2016-08-17 17:22   ` Yann E. MORIN
2016-08-19 21:34   ` Thomas Petazzoni
2016-08-19 21:39     ` Yann E. MORIN
2016-08-18 21:59 ` 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=20160818235943.715ce4c4@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