All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Seidel <jensseidel@users.sf.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: autopoint || touch config.rpath
Date: Wed, 7 Apr 2010 17:44:46 +0200	[thread overview]
Message-ID: <20100407154445.GA9625@merkur.sol.de> (raw)
In-Reply-To: <1270305838.4237.23.camel@mattotaupa>

Hi Paul,

I'm sorry for replying so late.

Originally you wrote
(http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-March/018796.html):

> Now I am getting the following error message during `configure`.
> configure.ac:35: required file `./config.rpath' not found

To be honest I had trouble reproducing it without bitbake. Probably I should
take the time to learn it ...

Nevertheless according to my autotools knowledge this comes from ommitting
autopoint, which installs this file and is by default called from
autoreconf.
Have you tried removing the line EXTRA_AUTORECONF = "--exclude=autopoint"
in [2]?

But --exclude=autopoint is no valid option for version 2.65. Mhm ...

Try also to use the option -v of autoreconf, some warnings are only visible
in verbose mode (such as sometimes:
"autoreconf: configure.ac: not running autopoint: --install not given").

> So `autogen.sh` needs to be run and I just found the following
> hint.
>
>        do_configure_prepend() {
>               sh autogen.sh
>        }
>
> But this fails with the error that C programs cannot be executed.

This fails because this already starts configure without crosscompiling
options. Set the environment variable "NOCONFIGURE=yes" before calling
autogen.sh. Does it help?

On Sat, Apr 03, 2010 at 04:43:58PM +0200, Paul Menzel wrote:
> Am Samstag, den 03.04.2010, 15:51 +0200 schrieb Jens Seidel:
> > On Sat, Apr 03, 2010 at 01:20:20PM +0200, Paul Menzel wrote:
> > > Am Freitag, den 02.04.2010, 21:44 +0200 schrieb Paul Menzel:
> > > > Am Freitag, den 02.04.2010, 11:28 -0700 schrieb Khem Raj:
> > > > > On Fri, Apr 2, 2010 at 8:59 AM, Paul Menzel <paulepanter@users.sourceforge.net> wrote:
> > Let me short summarize:
> > 
> > automake is a tool to generate Makefile templates (called Makefile.in) from
> > Makefile.am files. Normally a tgz ball ships already these generated files
> > (that's dictated by GNU). Nevertheless these files are often not committed
> > into version control systems and a script autogen.sh or better autoreconf is
> > used to generate Makefile.in by calling automake. But autoreconf calls even
> > more: e.g. autoconf (which generated configure) and now also autopoint.
> > autopoint generated the gettext infrastructure (the translation system to

s/generated/generates/

> > support foreign languages) by copying all non config dependent gettext files
> > (such as Makefile.in.in, some scripts, ...) into po and m4 macros. That's

should be (sorry):
(such as Makefile.in.in, some scripts, m4 macros, ...) into the directory po/.

> > also a good thing as this avoids committing generated files.
 
> Thank you for this great summary. I am still clueless about
> `config.rpath` though.

Yep, try the hints above.
 
> Correct. Though as far as I understood it using `inherit autotools` OE
> is using its own commands to set up the environment using
> `autotools.bbclass` and there you will find the following line [2]
> causing problems [3].
> 
>     EXTRA_AUTORECONF = "--exclude=autopoint"
> 
> Nobody knows why this was added in the first place, but if you try to

What about git? Try git blame, git log.

I suggest to just remove it if it works without!

autopoint has dependance to cvs: it requires the client as it
ships a local CVS repository to handle various gettext versions (if a
package mentions it needs only version x.y of gettext, autopoint copies only
this version (no newer one) into the directory to verify that x.y. is indeed
sufficient). Maybe autopoint was excluded to avoid this dependence, there
were some similar problems in Debian (http://bugs.debian.org/432270) and
Gentoo, where CVS was not added as requirement for gettext (which ships
autopoint).

> configure Enna [4] for example it will fail as I reported [5]. Other
> packages seem to be affected too.
> 
> The argument is called in this line [6].
> 
>     oenote Executing autoreconf --verbose --install --force ${EXTRA_AUTORECONF} $acpaths
>     autoreconf -Wcross --verbose --install --force ${EXTRA_AUTORECONF} $acpaths || oefatal "autoreconf execution failed."
> 
> I cannot reproduce this using the provided files by Enna in my local
> environment.
 
> [1] http://cgit.openembedded.org/cgit.cgi/openembedded/tree/classes/autotools.bbclass
> [2] http://cgit.openembedded.org/cgit.cgi/openembedded/tree/classes/autotools.bbclass#n38
> [3] http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-March/018818.html
> [4] http://enna.geexbox.org/
> [5] http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-March/018796.html
> [6] http://cgit.openembedded.org/cgit.cgi/openembedded/tree/classes/autotools.bbclass#n136




  reply	other threads:[~2010-04-07 16:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-28 17:18 [PATCH] enna: Move to own recipe folder and update to enna hg Paul Menzel
2010-03-30 13:20 ` [PATCH v2] " Paul Menzel
2010-04-02 15:59   ` [PATCH v3] enna: Move to own recipe folder and update to new Enna hg repository Paul Menzel
2010-04-02 18:28     ` Khem Raj
2010-04-02 19:44       ` Paul Menzel
2010-04-03 11:20         ` autopoint || touch config.rpath (was: [PATCH v3] enna: Move to own recipe folder and update to new Enna hg repository.) Paul Menzel
2010-04-03 13:51           ` Jens Seidel
2010-04-03 14:43             ` autopoint || touch config.rpath Paul Menzel
2010-04-07 15:44               ` Jens Seidel [this message]
2010-04-08  8:01                 ` Richard Purdie
2010-04-02 21:18       ` [PATCH v3] enna: Move to own recipe folder and update to new Enna hg repository Martin Jansa
2010-04-02 22:56         ` Setting `PV` in recipes using SCM repositories (was: [PATCH v3] enna: Move to own recipe folder and update to new Enna hg repository.) Paul Menzel
2010-04-04  8:43           ` Setting `PV` in recipes using SCM repositories Marco Cavallini
2010-04-03 11:03         ` [PATCH v4] enna: Move to own recipe folder and update to new Enna hg repository Paul Menzel

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=20100407154445.GA9625@merkur.sol.de \
    --to=jensseidel@users.sf.net \
    --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.