From: Marc Ferland <ferlandm@sonatest.com>
To: "Paul D. DeRocco" <pderocco@ix.netcom.com>
Cc: yocto@yoctoproject.org
Subject: Re: Can't find guile-2.0
Date: Tue, 19 Mar 2013 17:28:01 -0400 [thread overview]
Message-ID: <87r4jbcc66.fsf@sonatest.com> (raw)
In-Reply-To: <56C806C0B65D44ADA7D6314F4051E91E@PAULD> (Paul D. DeRocco's message of "Tue, 12 Mar 2013 23:53:47 -0700")
"Paul D. DeRocco" <pderocco@ix.netcom.com> writes:
>> From: Burton, Ross
>>
>> On 12 March 2013 18:20, Paul D. DeRocco
>> <pderocco@ix.netcom.com> wrote:
>> > It says "attempted 145 tasks of which 145 didn't need to be
>> > rerun". So it thinks it's already there.
>>
>> Indeed. Something is breaking - you'll have to mail the whole
>> configure log from autogen to attempt to debug this.
>
> One thing that I notice is that in my build/tmp/work/i686-linux, I have two
> directories, autogen-native-5.12-r2 and autogen-native-5.12-r3. The first is
> from my successful out-of-the-box build of a week ago; the second is from my
> current failed build. What I did in between was to add the
> openembedded-core/meta and meta-openembedded/meta-oe layers in order to
> include Samba. The two logs deviate at line 275 where the old successful one
> says "checking whether with-libguile was specified... no" and the new failed
> one says "checking for i686-linux-pkg-config... no". I suspect something in
> the OE stuff appended to a recipe, which is leading to the problem.
>
Same thing here. Everything was building fine until I added the meta-oe
layer.
Does one of you have a workaround for this?
Thanks,
Marc
next prev parent reply other threads:[~2013-03-19 21:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 9:28 Can't find guile-2.0 Paul D. DeRocco
2013-03-12 21:20 ` Burton, Ross
2013-03-13 1:20 ` Paul D. DeRocco
2013-03-13 4:38 ` Burton, Ross
2013-03-13 6:53 ` Paul D. DeRocco
2013-03-19 21:28 ` Marc Ferland [this message]
2013-03-20 10:18 ` Burton, Ross
2013-03-20 18:11 ` Paul D. DeRocco
2013-03-20 18:53 ` Burton, Ross
2013-03-20 19:43 ` Paul D. DeRocco
2013-03-20 19:50 ` Burton, Ross
2013-03-20 20:06 ` Paul D. DeRocco
2013-03-20 20:15 ` Ross Burton
2013-03-20 20:35 ` Paul D. DeRocco
2013-03-20 20:40 ` Ross Burton
2013-03-20 20:45 ` Paul D. DeRocco
2013-03-20 20:55 ` Ross Burton
2013-03-21 6:48 ` Paul D. DeRocco
2013-03-21 9:53 ` Burton, Ross
2013-03-21 19:10 ` Paul D. DeRocco
2013-03-21 20:01 ` Paul D. DeRocco
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=87r4jbcc66.fsf@sonatest.com \
--to=ferlandm@sonatest.com \
--cc=pderocco@ix.netcom.com \
--cc=yocto@yoctoproject.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.