Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Prepare recipes for automake-1.13 (batch 1)
Date: Sun, 6 Jan 2013 13:21:18 +0100	[thread overview]
Message-ID: <20130106122118.GG3272@jama> (raw)
In-Reply-To: <1357239255-20959-1-git-send-email-cazfi74@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2334 bytes --]

On Thu, Jan 03, 2013 at 08:54:12PM +0200, Marko Lindqvist wrote:
> This batch is just three patches - most likely just drop in the
> ocean of automake-1.13 problems in meta-openembedded. These are
> kind side-products of trying to get things to work in
> openembedded-core side.
> 
> Below text is about all the work I've done for automake-1.13
> compatibility so far - not all of it is relevant to this batch.

All 3 merged, libmikmod was missing PR bump, but it's not big issue for
this kind of change.

Cheers,

> --------------------------------------------------------------------
> 
> In practice there is three categories of changes in automake-1.13
> that cause packages to break. From that follows that virtually all
> problems fall to three categories, and all packages suffering from
> problem of the same category get virtually identical fix.
> 
> * Long deprecated macros completely removed from automake-1.13,
>   which errors out upon seeing them. For these I add patch,
>   always called obsolete_automake_macros.patch, that replaces
>   obsolete macro with proper one. Most of the patches are just
>   AM_CONFIG_HEADER -> AC_CONFIG_HEADERS change.
> 
> * Trying to run help2man via "missing" when it doesn't exist.
>   Old automake versions allowed "missing" to be used that way,
>   1.13 aborts. I'm just removing the attempt to create manpages
>   that way. Note that it never actually worked anyway -
>   old automake just didn't abort when it failed.
> 
> * TESTS list cannot have $(srcdir) or $(top_srcdir) as part
>   of the path. When it does, it's usually bug in the package,
>   but unfortunately automake prevents it also when it's not.
>   Solution applied here is to simply remove TESTS.
> 
> --------------------------------------------------------------------
> 
> [meta-oe][PATCH 1/3] tslib: replace obsolete automake macros with
> [meta-oe][PATCH 2/3] libmikmod: replace obsolete automake macros
> [meta-oe][PATCH 3/3] libmad: replace obsolete automake macros with
> 
> 
> 
>  - ML
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

      parent reply	other threads:[~2013-01-06 12:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 18:54 Prepare recipes for automake-1.13 (batch 1) Marko Lindqvist
2013-01-03 18:54 ` [meta-oe][PATCH 1/3] tslib: replace obsolete automake macros with working ones Marko Lindqvist
2013-01-03 18:54   ` [meta-oe][PATCH 2/3] libmikmod: " Marko Lindqvist
2013-01-03 18:54     ` [meta-oe][PATCH 3/3] libmad: " Marko Lindqvist
2013-01-06 12:21 ` Martin Jansa [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=20130106122118.GG3272@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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