From: Gary Thomas <gary@mlbassoc.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Problems building different versions of perl
Date: Mon, 22 Jul 2013 06:58:41 -0600 [thread overview]
Message-ID: <51ED2C81.1060604@mlbassoc.com> (raw)
In-Reply-To: <51ED1883.90905@mlbassoc.com>
On 2013-07-22 05:33, Gary Thomas wrote:
> In an effort to understand my problem (code built using Poky/Yocto doesn't
> run but the same code built natively on a BeagleBoneBlack running Angstrom does),
> I want to try a previous version of perl. I picked up the recipes from the
> Poky/Yocto tree rev 51cbb5ae7 (5.14.2-r12) and put them in one of my local layers.
> I also set local.conf to have PREFERRED_VERSION_perl = "5.14.2"
>
> Now I'm getting these errors:
>
> NOTE: Resolving any missing task queue dependencies
> NOTE: preferred version 5.14.2 of perl not available (for item perl-module-strict)
> NOTE: versions of perl available: 5.14.3
> NOTE: preferred version 5.14.2 of perl not available (for item perl-module-vars)
> NOTE: versions of perl available: 5.14.3
> NOTE: preferred version 5.14.2 of perl not available (for item perl-module-config)
> NOTE: versions of perl available: 5.14.3
> NOTE: preferred version 5.14.2 of perl not available (for item perl-module-warnings)
> NOTE: versions of perl available: 5.14.3
> NOTE: Preparing runqueue
> ERROR: Multiple .bb files are due to be built which each provide perl (/home/local/poky-multi/meta-amltd/recipes-devtools/perl/perl_5.14.2.bb
> /home/local/poky-multi/meta/recipes-devtools/perl/perl_5.14.3.bb).
> This usually means one provides something the other doesn't and should.
> ERROR: Multiple .bb files are due to be built which each provide libmodule-build-perl (/home/local/poky-multi/meta-amltd/recipes-devtools/perl/perl_5.14.2.bb
> /home/local/poky-multi/meta/recipes-devtools/perl/perl_5.14.3.bb).
> This usually means one provides something the other doesn't and should.
>
> I don't see how I can be told on one line that 5.14.2 isn't available
> but on the next that it will also be built :-(
>
> The odd thing is that this process worked ONCE. I was able to build using
> 5.14.2 with no errors. I tried some stuff on my board and then needed to
> see how 5.14.3 behaved. Now when I want to go back to 5.14.2, I'm stuck
> with these errors and bitbake insists on using 5.14.3. I'm trying to go
> back to 5.14.2-r12 because that's the version that's on the BBB,
>
> How can I move forward?
>
> Thanks
>
> Note: my original problem is described in https://lists.yoctoproject.org/pipermail/yocto/2013-July/017297.html
> but there hasn't been any discussion or replies...
Interestingly, a build using the exact same meta-data does not yield these
warnings/errors and builds perl 5.14.2-r12 as I expected. I've tried various
combinations of 'cleansstate', etc, to no avail.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2013-07-22 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 11:33 Problems building different versions of perl Gary Thomas
2013-07-22 12:58 ` Gary Thomas [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=51ED2C81.1060604@mlbassoc.com \
--to=gary@mlbassoc.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.