From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] autotools: do not overwrite first include path
Date: Sat, 08 Feb 2020 08:56:40 +0100 [thread overview]
Message-ID: <87y2tdv7ev.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200204131300.GD3101@scaer> (Yann E. MORIN's message of "Tue, 4 Feb 2020 14:13:00 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Heiko, All,
> On 2020-02-04 13:40 +0100, Heiko Thiery spake thusly:
>> The first patch fixes the issue with the autotools package.
>> For a detailed explanation take a look into the commit message.
>>
>> The second patch removes the hooks that were introduced to workaround
>> the issue that is fixed with the first patch.
>>
>> Heiko Thiery (1):
>> remove the hook for creating the m4 directory
>>
>> Michael Walle (1):
>> autotools: do not overwrite first include path
> Series applied to master, thanks! :-)
> I just slightly reword the commit logs with a little bit of extra
> details.
It unfortunately seems to cause some breakage :/
E.G. sdl_mixer fails with an autools-related issues since this got
applied:
libtool: Version mismatch error. This is libtool 2.4.6, but the
libtool: definition of this LT_INIT comes from libtool 2.2.6.
libtool: You should recreate aclocal.m4 with macros from libtool 2.4.6
libtool: and run autoconf again.
http://autobuild.buildroot.net/?reason=sdl_mixer-1.2.12
Care to take a look?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2020-02-08 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 12:40 [Buildroot] [PATCH 0/2] autotools: do not overwrite first include path Heiko Thiery
2020-02-04 12:40 ` [Buildroot] [PATCH 1/2] " Heiko Thiery
2020-02-04 12:40 ` [Buildroot] [PATCH 2/2] remove the hook for creating the m4 directory Heiko Thiery
2020-02-10 3:36 ` Joel Stanley
2020-02-04 13:13 ` [Buildroot] [PATCH 0/2] autotools: do not overwrite first include path Yann E. MORIN
2020-02-08 7:56 ` Peter Korsgaard [this message]
2020-02-08 18:40 ` Yann E. MORIN
2020-02-08 18:58 ` Heiko Thiery
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=87y2tdv7ev.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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