From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Perl modules I can not get to build, libdbd-sqlite-perl libversion-perl
Date: Tue, 07 Sep 2010 08:24:42 -0700 [thread overview]
Message-ID: <4C86593A.7000006@mentor.com> (raw)
In-Reply-To: <AANLkTi=eX15FWkO+Fux8UpNv9tXkTVtkYrd=t3c_==2k@mail.gmail.com>
Graham Gower wrote:
> On 3 September 2010 09:13, J. L. <vwyodapink@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.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-09-07 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 19:48 Perl modules I can not get to build, libdbd-sqlite-perl libversion-perl J. L.
2010-09-02 20:02 ` Frans Meulenbroeks
2010-09-02 23:22 ` J. L.
2010-09-02 23:43 ` J. L.
2010-09-03 0:22 ` Graham Gower
2010-09-07 15:24 ` Tom Rini [this message]
2010-09-07 16:22 ` J. L.
2010-09-07 17:39 ` Tom Rini
2010-09-09 17:41 ` J. L.
2010-09-12 18:11 ` Roman I Khimov
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=4C86593A.7000006@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox