From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] package.bbclass: when running 'file', be explicit about the path to the magic
Date: Mon, 01 Mar 2010 08:51:00 -0500 [thread overview]
Message-ID: <4B8BC644.9090801@balister.org> (raw)
In-Reply-To: <b6ebd0a51003010542r136a7572n1a947161c196fff8@mail.gmail.com>
On 03/01/2010 08:42 AM, Chris Larson wrote:
> Ugh, lovely. Okay, I'll take care of it today, sorry for the hassle.
It is Monday after all :)
Philip
>
> On Mon, Mar 1, 2010 at 2:47 AM, Koen Kooi<k.kooi@student.utwente.nl> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 01-03-10 10:45, Graeme Gregory wrote:
>>> On Mon, Mar 01, 2010 at 10:35:36AM +0100, Koen Kooi wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> I think I know what's happening.
>>>>
>>>> On my (debian) buildhost I have file 4.26. (Re)building file-native 5.04
>>>> gives me:
>>>>
>>>> ./staging/x86_64-linux/usr/share/misc/magic.mgc
>>>>
>>>> Graeme has file 5.03 on his buildhost and has
>>>>
>>>> ./staging/x86_64-linux/usr/share/file/magic
>>>>
>>>> So it seems that the buildhost contamination also affects file-native :(
>>>>
>>> Its not contamination, its just simply that file 5.XX moved its magic
>>> file to /usr/share/misc/
>>>
>>> Im still building 4.21 for some reason so dont see this.
>>
>> Bitbake 1.8.x? I'm using bitbake master from git, that has a different
>> sorting algo AIUI.
>>
>> regards,
>>
>> Koen
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.5 (Darwin)
>>
>> iD8DBQFLi40oMkyGM64RGpERAjEIAJ4+rW+07FQBjx9std0w7ZE1tYcdtQCgtgI6
>> X6RRtXw6ttRVlMSfzyUAUBk=
>> =QSlm
>> -----END PGP SIGNATURE-----
>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>
>
>
prev parent reply other threads:[~2010-03-01 13:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 18:47 [PATCH] package.bbclass: when running 'file', be explicit about the path to the magic Chris Larson
2010-03-01 9:17 ` Koen Kooi
2010-03-01 9:35 ` Koen Kooi
2010-03-01 9:45 ` Graeme Gregory
2010-03-01 9:47 ` Koen Kooi
2010-03-01 13:42 ` Chris Larson
2010-03-01 13:51 ` Philip Balister [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=4B8BC644.9090801@balister.org \
--to=philip@balister.org \
--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