From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] autotool.bbclass: Remove `EXTRA_AUTORECONF = "--exclude=autopoint"`.
Date: Tue, 30 Mar 2010 14:38:33 +0200 [thread overview]
Message-ID: <hosrca$7qu$1@dough.gmane.org> (raw)
In-Reply-To: <1269949824.4103.38.camel@mattotaupa>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 30-03-10 13:50, Paul Menzel wrote:
> In commit 0f235b0f42575bfb50dd891cf44aa08c2e404a67 [1] `autotools.bbclass` was imported from BitKeeper. According to rwhitby on IRC the original author of `autotool.bbclass` cannot be found out anymore, so the reason why Autopoint has to be excluded not known.
>
> Having `EXTRA_AUTORECONF = "--exclude=autopoint"` in `autotools.bbclass` forces the usage of same hacks to prevent failure of `do_configure` [2].
>
> configure.ac:35: required file `./config.rpath' not found
>
> I ran a build from scratch with `EXTRA_AUTORECONF = "--exclude=autopoint"` from `autotools.bbclass` and did not see any regressions.
I wonder if we only should run autopoint if there are AM_GNU_GETTEXT*
macros in configure.{in,ac}, or does autopoint take care of that
automagically?
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLsfDIMkyGM64RGpERAr5dAKCl8GLU8pRCw+IkXw4cWyoII2S27wCguWQG
IdFWfa67U2/EDL5UZu5+4Sc=
=7vtE
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-03-30 12:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-27 22:54 enna: do_configure failed: automake: unknown warning category `cross' Paul Menzel
2010-03-28 6:40 ` Thomas Zimmermann
2010-03-28 7:46 ` Paul Menzel
2010-03-28 8:55 ` Koen Kooi
2010-03-28 17:31 ` Paul Menzel
2010-03-28 19:32 ` Koen Kooi
2010-03-30 11:50 ` [PATCH] autotool.bbclass: Remove `EXTRA_AUTORECONF = "--exclude=autopoint"` Paul Menzel
2010-03-30 12:38 ` Koen Kooi [this message]
2010-03-30 12:51 ` Phil Blundell
2010-03-30 18:15 ` Khem Raj
2010-03-31 13:31 ` Koen Kooi
2010-03-31 17:04 ` Khem Raj
2010-04-09 14:19 ` Enrico Scholz
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='hosrca$7qu$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.