Re: Perl modules I can not get to build, libdbd-sqlite-perl libversion-perl

[Graham Gower <graham.gower@gmail.com>]

On 3 September 2010 09:13, J. L. <vwyodapink@gmail.com> wrote:
> Also if it would help I can post the image recipe I have made that I
> am trying to build.
>
> In case this explains anymore about the overo branch for you this was
> posted by steve sakoman who I believe is the maintainer of the branch
> about the difference which to me reads as its just the configuration
> files. If I am wrong please correct me.
> http://old.nabble.com/Re%3A-Is-Overo-OE-branch-a-fork--p25065128.html
>
> The main reason I posted these recipes was due to the fact that I have
> tried everything that has been mentioned to me before about how to
> read the errors and from what the errors read I do not understand why
> installing the files on the build machine does not help with the one,

Its possible the recipe needs to depend on some foo-native package. If
this is the case, then it can fail even if you have installed the
things on your build host manually because they are not in OE's
staging area.

Sometimes dependencies are not listed in the recipe because the build
order has always caused the dependency to be present on those
configurations that have been tested. The following things may expose
missing dependencies in a recipe by altering the build order:

 * Increasing BB_NUMBER_THREADS.
 * Building on a host that no one else is using.
 * Variations in your machine/distro/local conf files as compared with
those that have been tested recently by developers.
 * Recent changes to recipes which your problematic recipe depends on.
 * Recent recipe changes to recipes that depend upon your problematic recipe.
 * Radioactive decay of a bismuth-210 atom 3km underneath the house of
your server manufacturer's CTO's Aunt Mavis' family home in Tuvalu.



> and the other is honestly above me at the moment as I do not grasp
> using devshell yet and how to work with in there, let alone properly
> lay out a program recipe and then patch it to work properly. Once I
> grasp things more I hope to be a help and not such a hindrance, I
> welcome any tips links or anything to point to how to fix either and I
> will try more on more with those pointers and if successful post the
> results and maybe a patch or post the failure.

Read the OE manual. Read the Bitbake manual. Read .bb files. Read
.conf files. Read .bbclass files. Read Bitbake sources. Send patches.
Add time. Repeat. == expert!

-Graham