Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libtool: revert a commit which re-introduced an already fixed problem
Date: Wed, 19 Mar 2014 17:23:28 +0100	[thread overview]
Message-ID: <5329C480.5010702@mind.be> (raw)
In-Reply-To: <5329B2A4.9080802@imgtec.com>

On 19/03/14 16:07, Vicente Olivert Riera wrote:
> On 03/19/2014 03:02 PM, Arnout Vandecappelle wrote:
>> On 19/03/14 15:41, Vicente Olivert Riera wrote:
>>> On 03/19/2014 01:50 PM, Arnout Vandecappelle wrote:
[snip]
>>>>    Okay, the issue is that that defconfig enables libtool for the
>>>> target,
>>>> and autoreconf adds $(STAGING_DIR)/usr/share/aclocal to the include
>>>> path.
>>>> So the unpatched libtool will take precedence.
>>>
>>> Hello Arnout,
>>>
>>> do you mean that enabling only BR2_PACKAGE_LIBTOOL and
>>> BR2_PACKAGE_LIBISCSI you can reproduce the failure?
>>
>>   I haven't tried that specifically, but I think yes.
> 
> I have tried it, and the failure is not reproduced with those options
> only. That's why I used the full config file from the autobuild report.

 Yeah, that's because libtool normally comes after iscsi, but in the
autobuild failure gst-plugins-good is built first and that depends on
pulseaudio and that depends on libtool.


> 
>>   But actually, I think the easier solution is to just bump libtool to
>> 2.4.2.444. I'm going to run some tests on that and see how far we get.
> 
> I see, you want to bump to a version with the upstream patch already
> included, so the autoconf won't be triggered because your are not
> patching the m4 file.

 Exactly.

 But unfortunately the .444 "release" is just a git snapshot, without
configure script, so that doesn't solve the problem.

 Possible approaches:

1. Apply the patch to the libtool.m4 in staging as well.

2. Revert to a normal patch, and avoid reconf by touching the generated
files.

3. Ask upstream to create a new release.


 I'll send a patch for (2) and do (3) as well.


 Regards,
 Arnout



-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      reply	other threads:[~2014-03-19 16:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17 17:40 [Buildroot] [PATCH] libtool: revert a commit which re-introduced an already fixed problem Vicente Olivert Riera
2014-03-17 22:08 ` Peter Korsgaard
2014-03-18  7:46   ` Arnout Vandecappelle
2014-03-18 10:44     ` Vicente Olivert Riera
2014-03-18 10:55       ` Vicente Olivert Riera
2014-03-19  7:54       ` Arnout Vandecappelle
2014-03-19  9:40         ` Vicente Olivert Riera
2014-03-19 13:50           ` Arnout Vandecappelle
2014-03-19 14:41             ` Vicente Olivert Riera
2014-03-19 15:02               ` Arnout Vandecappelle
2014-03-19 15:07                 ` Vicente Olivert Riera
2014-03-19 16:23                   ` Arnout Vandecappelle [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=5329C480.5010702@mind.be \
    --to=arnout@mind.be \
    --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