Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: enna: do_configure failed: automake: unknown warning category `cross'
Date: Sun, 28 Mar 2010 19:31:21 +0200	[thread overview]
Message-ID: <1269797481.8018.80.camel@mattotaupa> (raw)
In-Reply-To: <hon5i2$8iq$1@dough.gmane.org>

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

Am Sonntag, den 28.03.2010, 10:55 +0200 schrieb Koen Kooi:
> On 27-03-10 23:54, Paul Menzel wrote:
> > I am trying to write the recipe for Enna [1].
> 
> [..]
> 
> > Now I am getting the following error message during `configure`.
> > 
> >         […]
> 
> >         configure.ac:35: required file `./config.rpath' not found
> 
> > Any hint is appreciated.
> 
> do_configure_prepend() {
> 	autopoint || touch config.rpath
> }

Thanks that worked!

Sorry for the next question. Is that workaround needed because of not
having Automake 1.11.1? Or is the recommended fix, that upstream ships
`config.rpath`?

[…]


Thanks,

Paul

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2010-03-28 17:34 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 [this message]
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
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=1269797481.8018.80.camel@mattotaupa \
    --to=paulepanter@users.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox