From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: qemuarm: configure of bison fails, claims to need flex [SOLVED?]
Date: Tue, 27 Nov 2012 14:54:59 +0000 [thread overview]
Message-ID: <1354028099.21863.100.camel@ted> (raw)
In-Reply-To: <alpine.DEB.2.02.1211270512010.16369@oneiric>
On Tue, 2012-11-27 at 05:19 -0500, Robert P. J. Day wrote:
> On Tue, 27 Nov 2012, Robert P. J. Day wrote:
>
> >
> > trying to build absolutely stock qemuarm image with current oe-core,
> > got:
> >
> > ERROR: Task 800
> > (virtual:native:/home/rpjday/OE/dist/layers/oe-core/meta/recipes-devtools/bison/bison_2.5.1.bb,
> > do_configure) failed with exit code '1'
> >
> > and the log file claimed that bison needed flex. i'm doing it all
> > over again from scratch just to make sure it wasn't something silly
> > i did, i'll report back if i can reproduce it.
>
> ah, i see where i did something unapproved -- to test what i could
> add to the ASSUME_PROVIDED list, i added this to my local.conf:
>
> ASSUME_PROVIDED += "m4 quilt"
>
> which caused the configure step for bison to fail, claiming that it
> needed flex. should i have expected that? am i misunderstanding the
> rationale for ASSUME_PROVIDED?
You are misunderstanding the syntax. Were you not meaning m4-native and
quilt-native?
Cheers,
Richard
prev parent reply other threads:[~2012-11-27 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 9:29 qemuarm: configure of bison fails, claims to need flex Robert P. J. Day
2012-11-27 10:19 ` qemuarm: configure of bison fails, claims to need flex [SOLVED?] Robert P. J. Day
2012-11-27 14:41 ` Chris Larson
2012-11-27 14:54 ` Richard Purdie [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=1354028099.21863.100.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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.