Re: [OE-core] multilib errors
On Wed, Sep 19, 2012 at 6:03 AM, Paul Eggleton wrote: > I have seen these errors as well. It definitely should be doing these checks Even for lib64-nativesdk-libtool? It's doing multilib processing on nativesdk recipes? -M ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] multilib errors
On Wed, Sep 19, 2012 at 6:31 AM, Paul Eggleton
wrote:
> On Wednesday 19 September 2012 06:26:31 Khem Raj wrote:
>> On Wed, Sep 19, 2012 at 4:03 AM, Paul Eggleton
>>
>> wrote:
>> > I have seen these errors as well. It definitely should be doing these
>> > checks - the warnings occur during the file checksum code but more
>> > broadly they indicate the system will fail to find these files should you
>> > try to build the targets mentioned. Looking more closely, I could be
>> > wrong but it looks to me that BPN is not correct at least in the case of
>> > lib64-build-appliance-image - I think it ought to be
>> > "build-appliance-image" but instead it is "lib64-build-
>> > appliance-image", which means that it can't find the files referred to in
>> > SRC_URI anymore given that they are located in a directory named "build-
>> > appliance-image".
>>
>> IMO when we inherit multilib bbclass then it should also add new
>> ${BPN} based dirs to FILESPATH
>
> BPN-based dirs are already in FILESPATH - that's the issue, BPN itself is not
> the expected value.
>
Thats what I meant with 'new BPN'
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] multilib errors
On Wednesday 19 September 2012 06:26:31 Khem Raj wrote:
> On Wed, Sep 19, 2012 at 4:03 AM, Paul Eggleton
>
> wrote:
> > I have seen these errors as well. It definitely should be doing these
> > checks - the warnings occur during the file checksum code but more
> > broadly they indicate the system will fail to find these files should you
> > try to build the targets mentioned. Looking more closely, I could be
> > wrong but it looks to me that BPN is not correct at least in the case of
> > lib64-build-appliance-image - I think it ought to be
> > "build-appliance-image" but instead it is "lib64-build-
> > appliance-image", which means that it can't find the files referred to in
> > SRC_URI anymore given that they are located in a directory named "build-
> > appliance-image".
>
> IMO when we inherit multilib bbclass then it should also add new
> ${BPN} based dirs to FILESPATH
BPN-based dirs are already in FILESPATH - that's the issue, BPN itself is not
the expected value.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] multilib errors
On Wed, Sep 19, 2012 at 4:03 AM, Paul Eggleton
wrote:
> I have seen these errors as well. It definitely should be doing these checks -
> the warnings occur during the file checksum code but more broadly they
> indicate
> the system will fail to find these files should you try to build the targets
> mentioned. Looking more closely, I could be wrong but it looks to me that BPN
> is not correct at least in the case of lib64-build-appliance-image - I think
> it ought to be "build-appliance-image" but instead it is "lib64-build-
> appliance-image", which means that it can't find the files referred to in
> SRC_URI anymore given that they are located in a directory named "build-
> appliance-image".
IMO when we inherit multilib bbclass then it should also add new
${BPN} based dirs to FILESPATH
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] multilib errors
On Wednesday 19 September 2012 02:37:35 McClintock Matthew-B29882 wrote: > Is anyone else seeing: > > WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI > entry trailingslash.patch: file could not be found > WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI > entry prefix-manpage-fix.patch: file could not be found > WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI > entry rename-with-sysroot.patch: file could not be found > WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI > entry use-sysroot-in-libpath.patch: file could not be found > WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI > entry fix-final-rpath.patch: file could not be found > WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI > entry avoid_absolute_paths_for_general_utils.patch: file could not be > found > WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI > entry fix-rpath.patch: file could not be found > WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI > entry respect-fstack-protector.patch: file could not be found > WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI > entry norm-rpath.patch: file could not be found > WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI > entry prefix.patch: file could not be found > WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI > entry fixinstall.patch: file could not be found > WARNING: Unable to get checksum for lib64-build-appliance-image > SRC_URI entry Yocto_Build_Appliance.vmx: file could not be found > WARNING: Unable to get checksum for lib64-build-appliance-image > SRC_URI entry Yocto_Build_Appliance.vmxf: file could not be found > > With multilib enabled? Have not debuged but it looks like something is > parsing SRC_URI for recipes under multilib when it should not be. I have seen these errors as well. It definitely should be doing these checks - the warnings occur during the file checksum code but more broadly they indicate the system will fail to find these files should you try to build the targets mentioned. Looking more closely, I could be wrong but it looks to me that BPN is not correct at least in the case of lib64-build-appliance-image - I think it ought to be "build-appliance-image" but instead it is "lib64-build- appliance-image", which means that it can't find the files referred to in SRC_URI anymore given that they are located in a directory named "build- appliance-image". Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] multilib errors
Is anyone else seeing: WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI entry trailingslash.patch: file could not be found WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI entry prefix-manpage-fix.patch: file could not be found WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI entry rename-with-sysroot.patch: file could not be found WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI entry use-sysroot-in-libpath.patch: file could not be found WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI entry fix-final-rpath.patch: file could not be found WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI entry avoid_absolute_paths_for_general_utils.patch: file could not be found WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI entry fix-rpath.patch: file could not be found WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI entry respect-fstack-protector.patch: file could not be found WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI entry norm-rpath.patch: file could not be found WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI entry prefix.patch: file could not be found WARNING: Unable to get checksum for lib64-nativesdk-libtool SRC_URI entry fixinstall.patch: file could not be found WARNING: Unable to get checksum for lib64-build-appliance-image SRC_URI entry Yocto_Build_Appliance.vmx: file could not be found WARNING: Unable to get checksum for lib64-build-appliance-image SRC_URI entry Yocto_Build_Appliance.vmxf: file could not be found With multilib enabled? Have not debuged but it looks like something is parsing SRC_URI for recipes under multilib when it should not be. -M ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
