From: Jaap de Jong <jaap.dejong@nedap.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: machinename with dash in it
Date: Tue, 9 Apr 2013 08:23:19 +0200 [thread overview]
Message-ID: <5163B3D7.2000400@nedap.com> (raw)
In-Reply-To: <20130408201539.GD2470@jama>
On 04/08/2013 10:15 PM, Martin Jansa wrote:
> On Mon, Apr 08, 2013 at 09:53:34PM +0200, Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Op 08-04-13 15:17, Martin Jansa schreef:
>>> On Mon, Apr 08, 2013 at 02:28:51PM +0200, Jaap de Jong wrote:
>>>> Hi All, something strange happens with my machinename with a dash in
>>>> it: x-y If I bitbake some image it will end up that netbase is not
>>>> found. Inspection of build/tmp-angstrom_v2012_12-eglibc/work shows 2
>>>> variants of x-y: one with a dash and one where the dash is replaced by
>>>> an underscore: x-y and x_y In x-y only netbase is found, rest of the
>>>> machinespecific packages are in x_y
>>> MACHINE_ARCH is MACHINE with s/-/_/g (because rpm had issues with -) so
>>> it's expected.
>>>
>>>> Creating the image fails with the message that netbase is not found...
>>>> Any ideas?
>>> It's probably caused by
>>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=4102 do manual cleanup
>>> described there and it should work fine.
>> The root cause was this one:
>> https://git.linaro.org/gitweb?p=openembedded/meta-linaro.git;a=commit;h=30f353c072336ad764e9528ae3c508adb28fa4ad
> Heh, I was expecting that all MACHINEs in PACKAGE_ARCH died long time
> ago.
>
Thanks for the hint, this is fixed now.
(I have a new error though....)
Jaap
prev parent reply other threads:[~2013-04-09 6:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 12:28 machinename with dash in it Jaap de Jong
2013-04-08 13:17 ` Martin Jansa
2013-04-08 19:53 ` Koen Kooi
2013-04-08 20:15 ` Martin Jansa
2013-04-09 6:23 ` Jaap de Jong [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=5163B3D7.2000400@nedap.com \
--to=jaap.dejong@nedap.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 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.