[oe] Perl modules I can not get to build, libdbd-sqlite-perl libversion-perl

[J. L.]

On Tue, Sep 7, 2010 at 10:39 AM, Tom Rini <tom_rini at mentor.com> wrote:
> J. L. wrote:
>>
>> On Tue, Sep 7, 2010 at 8:24 AM, Tom Rini <tom_rini at mentor.com> wrote:
>>>
>>> Graham Gower wrote:
>>>>
>>>> On 3 September 2010 09:13, J. L. <vwyodapink at gmail.com> wrote:
>>>
>>> [snip]
>>>>>
>>>>> 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!
>>>
>>> I'd just like to add in that while it's great (really, I mean it), you're
>>> reporting problems, if you can reproduce them in vanilla OE with
>>> something
>>> like MACHINE=qemuarm and DISTRO=angstrom-2008.1 (or DISTRO=minimal) or
>>> similar, that will help rule out a lot of concern on our part and give a
>>> testcase we can all easily try out.
>>
>> OK thanks Tom I will try and read more on how to do that. Have not
>> done anything with qemu yet. But what I get now and correct if I am
>> wrong by OE vanilla you mean fresh directly off the dev branch no
>> other sub tree correct? then modify my .conf to to the settings you
>> listed above? If I am way off dont worry about taking the time to
>
> Correct.
>
>> explain in detail I will just read about it. I feel I have become an
>> annoyance on the boards from my lacking knowledge. Would showing the
>> recipe I build for my gumstix help? Its now building but not with
>> everything I want and some programs are broken, but its very close the
>> closest I have gotten so far. Any who thanks for replying and giving
>> me more info on how to help you guys help me. I do appreciate
>> everyones help and input a bunch.
>
> We're happy to have a problem report, really.  It's just that since yes,
> you're working with more than just the vanilla tree we want to be certain
> that the problem is in the vanilla tree and not a conflict in having
> additional overlays and such available.
>
> --
> Tom Rini
> Mentor Graphics Corporation
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Just got done building my image with the vanilla tree as you requested
and I still have basically the same results, the only major difference
is now my gnome image gives a password I have no clue of to root but
my enlightenment image built and worked the same from the overo tree
as the vanilla dev OE tree as well as still failing in the same
manners. The gnome image was the only one that added another issue to
my build. Hope that may help, is there any more I can do to help?
Should I try like once a week building on the overo tree and vanilla
tree and post the differences if any or? Thanks for your time and
pointers

JL