Patchwork [0/1] Update automake to version 1.13.2

login
register
mail settings
Submitter Marko Lindqvist
Date May 23, 2013, 8:52 a.m.
Message ID <cover.1369298825.git.cazfi74@gmail.com>
Download mbox
Permalink /patch/50373/
State New
Headers show

Pull-request

git://git.openembedded.org/openembedded-core-contrib cazfi/am13

Comments

Marko Lindqvist - May 23, 2013, 8:52 a.m.
New upstream release, 1.13.2, has reverted some of the 1.13.0 backward
compatibility dropping changes, for the duration of 1.13 series. Unlike
earlier 1.13 releases, it can be used without breaking huge number of
packages.

The following changes since commit aeb704fee8b4ffeaeddcdb36ae4e1d62c264ce42:

  scripts/bitbake: Handle the case where git isn't installed cleanly (2013-05-21 10:06:11 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib cazfi/am13
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=cazfi/am13

Marko Lindqvist (1):
  automake: update to upstream version 1.13.2

 .../prefer-cpio-over-pax-for-ustar-archives.patch  |   37 ++++++++++----------
 .../{automake_1.12.6.bb => automake_1.13.2.bb}     |    4 +--
 2 files changed, 21 insertions(+), 20 deletions(-)
 rename meta/recipes-devtools/automake/{automake_1.12.6.bb => automake_1.13.2.bb} (90%)
Saul Wold - May 23, 2013, 11:03 p.m.
On 05/23/2013 01:52 AM, Marko Lindqvist wrote:
> New upstream release, 1.13.2, has reverted some of the 1.13.0 backward
> compatibility dropping changes, for the duration of 1.13 series. Unlike
> earlier 1.13 releases, it can be used without breaking huge number of
> packages.
>

I have not dug into it too deeply, but I think this update is causing a 
problem with gtk-engines test Makefile, there is a section that has 
$(patsubst incomplete.

 From the Makefile.in that is generated from Makefile.am

$(patsubst.log: $(patsubst
         @p='$(patsubst'; \
         b='$(patsubst'; \
         $(am__check_pre) $(LOG_DRIVER) --test-name "$$f" \
         --log-file $$b.log --trs-file $$b.trs \
         $(am__common_driver_flags) $(AM_LOG_DRIVER_FLAGS) 
$(LOG_DRIVER_FLAGS) -- $(LOG_COMPILE) \

That does not look right!

Sau!


> The following changes since commit aeb704fee8b4ffeaeddcdb36ae4e1d62c264ce42:
>
>    scripts/bitbake: Handle the case where git isn't installed cleanly (2013-05-21 10:06:11 +0100)
>
> are available in the git repository at:
>
>    git://git.openembedded.org/openembedded-core-contrib cazfi/am13
>    http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=cazfi/am13
>
> Marko Lindqvist (1):
>    automake: update to upstream version 1.13.2
>
>   .../prefer-cpio-over-pax-for-ustar-archives.patch  |   37 ++++++++++----------
>   .../{automake_1.12.6.bb => automake_1.13.2.bb}     |    4 +--
>   2 files changed, 21 insertions(+), 20 deletions(-)
>   rename meta/recipes-devtools/automake/{automake_1.12.6.bb => automake_1.13.2.bb} (90%)
>
Marko Lindqvist - May 24, 2013, 10:21 p.m.
Confirmed. Automake update to (any) 1.13.x version breaks gtk-engines
build. I don't know yet if it's automake or gtk-engines bug.


On 24 May 2013 02:03, Saul Wold <sgw@linux.intel.com> wrote:

> On 05/23/2013 01:52 AM, Marko Lindqvist wrote:
>
>> New upstream release, 1.13.2, has reverted some of the 1.13.0 backward
>> compatibility dropping changes, for the duration of 1.13 series. Unlike
>> earlier 1.13 releases, it can be used without breaking huge number of
>> packages.
>>
>>
> I have not dug into it too deeply, but I think this update is causing a
> problem with gtk-engines test Makefile, there is a section that has
> $(patsubst incomplete.
>
> From the Makefile.in that is generated from Makefile.am
>
> $(patsubst.log: $(patsubst
>         @p='$(patsubst'; \
>         b='$(patsubst'; \
>         $(am__check_pre) $(LOG_DRIVER) --test-name "$$f" \
>         --log-file $$b.log --trs-file $$b.trs \
>         $(am__common_driver_flags) $(AM_LOG_DRIVER_FLAGS)
> $(LOG_DRIVER_FLAGS) -- $(LOG_COMPILE) \
>
> That does not look right!
>
> Sau!
>
>
>
>  The following changes since commit aeb704fee8b4ffeaeddcdb36ae4e1d**
>> 62c264ce42:
>>
>>    scripts/bitbake: Handle the case where git isn't installed cleanly
>> (2013-05-21 10:06:11 +0100)
>>
>> are available in the git repository at:
>>
>>    git://git.openembedded.org/**openembedded-core-contrib<http://git.openembedded.org/openembedded-core-contrib>cazfi/am13
>>    http://cgit.openembedded.org/**cgit.cgi/openembedded-core-**
>> contrib/log/?h=cazfi/am13<http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=cazfi/am13>
>>
>> Marko Lindqvist (1):
>>    automake: update to upstream version 1.13.2
>>
>>   .../prefer-cpio-over-pax-for-**ustar-archives.patch  |   37
>> ++++++++++----------
>>   .../{automake_1.12.6.bb => automake_1.13.2.bb}     |    4 +--
>>   2 files changed, 21 insertions(+), 20 deletions(-)
>>   rename meta/recipes-devtools/**automake/{automake_1.12.6.bb =>
>> automake_1.13.2.bb} (90%)
>>
>>
>
>
Radu Moisan - July 3, 2013, 8:16 a.m.
On 05/25/2013 01:21 AM, Marko Lindqvist wrote:
>
>  Confirmed. Automake update to (any) 1.13.x version breaks gtk-engines 
> build. I don't know yet if it's automake or gtk-engines bug.
>

Any updates on this? Do we have a bug filled addressing this problem? I 
found several package which require automake 1.13.x for upgrade and this 
automake issue is blocking them.

Radu
Marko Lindqvist - July 3, 2013, 8:19 a.m.
On 3 July 2013 11:16, Radu Moisan <radu.moisan@intel.com> wrote:
>
> On 05/25/2013 01:21 AM, Marko Lindqvist wrote:
>
>
>  Confirmed. Automake update to (any) 1.13.x version breaks gtk-engines
> build. I don't know yet if it's automake or gtk-engines bug.
>
>
> Any updates on this? Do we have a bug filled addressing this problem? I
> found several package which require automake 1.13.x for upgrade and this
> automake issue is blocking them.

 Sorry I have had no time to work on this. I did file automake bug
report, for which the response is
http://lists.gnu.org/archive/html/bug-automake/2013-06/msg00014.html
meaning we need to patch gtk-engines.


  -ML
Radu Moisan - July 3, 2013, 8:34 a.m.
On 07/03/2013 11:19 AM, Marko Lindqvist wrote:
> On 3 July 2013 11:16, Radu Moisan <radu.moisan@intel.com> wrote:
>> On 05/25/2013 01:21 AM, Marko Lindqvist wrote:
>>
>>
>>   Confirmed. Automake update to (any) 1.13.x version breaks gtk-engines
>> build. I don't know yet if it's automake or gtk-engines bug.
>>
>>
>> Any updates on this? Do we have a bug filled addressing this problem? I
>> found several package which require automake 1.13.x for upgrade and this
>> automake issue is blocking them.
>   Sorry I have had no time to work on this. I did file automake bug
> report, for which the response is
> http://lists.gnu.org/archive/html/bug-automake/2013-06/msg00014.html
> meaning we need to patch gtk-engines.
>

Thanks Marko, I'll take a look over this.

Radu
Marko Lindqvist - Aug. 18, 2013, 5:21 p.m.
On 3 July 2013 11:34, Radu Moisan <radu.moisan@intel.com> wrote:
>
> On 07/03/2013 11:19 AM, Marko Lindqvist wrote:
>>
>> On 3 July 2013 11:16, Radu Moisan <radu.moisan@intel.com> wrote:
>>>
>>> On 05/25/2013 01:21 AM, Marko Lindqvist wrote:
>>>
>>>
>>>   Confirmed. Automake update to (any) 1.13.x version breaks gtk-engines
>>> build. I don't know yet if it's automake or gtk-engines bug.
>>>
>>>
>>> Any updates on this? Do we have a bug filled addressing this problem? I
>>> found several package which require automake 1.13.x for upgrade and this
>>> automake issue is blocking them.
>>
>>   Sorry I have had no time to work on this. I did file automake bug
>> report, for which the response is
>> http://lists.gnu.org/archive/html/bug-automake/2013-06/msg00014.html
>> meaning we need to patch gtk-engines.
>>
>
> Thanks Marko, I'll take a look over this.
>
> Radu

 What's the status now? I see that at least automake has not been
updated yet. I could take a look myself next week.


 - ML