Skip to contentSkip to conversation

New warning

DISCUSSION Gary Thomas 3 participants 3 messages Oct 2, 2012 – Oct 3, 2012

lore
Share & tools
lore
#0 lore raw

I'm getting these new warnings, even with a build from scratch. This is from poky master rev 7c39c87d52c20e47cf90275a16e4517a296c8388

WARNING: The recipe is trying to install files into a shared area when those files already exist. Those files are:
/home/local/p81_build/tmp/sysroots/cobra3530p81/usr/include/python2.7/pyconfig.h /home/local/p81_build/tmp/sysroots/cobra3530p81/usr/lib/libpython2.7.so /home/local/p81_build/tmp/sysroots/cobra3530p81/usr/lib/libpython2.7.so.1.0 /home/local/p81_build/tmp/sysroots/cobra3530p81/usr/lib/python2.7/config/Makefile

Do they hurt anything? Why am I getting them now, what's changed, etc?

Thanks

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw
Quoted 10 lines · Gary Thomas

I'm getting these new warnings, even with a build from scratch. This is from poky master rev 7c39c87d52c20e47cf90275a16e4517a296c8388

WARNING: The recipe is trying to install files into a shared area when those files already exist. Those files are:

    /home/local/p81_build/tmp/sysroots/cobra3530p81/usr/include/python2.7/pyconfig.h
    /home/local/p81_build/tmp/sysroots/cobra3530p81/usr/lib/libpython2.7.so
    /home/local/p81_build/tmp/sysroots/cobra3530p81/usr/lib/libpython2.7.so.1.0
    /home/local/p81_build/tmp/sysroots/cobra3530p81/usr/lib/python2.7/config/Makefile

Do they hurt anything? Why am I getting them now, what's changed, etc?

I fixed the code that was supposed to be generate these messages and we started seeing them. Its a new type of check added relatively recently but was accidentally disabled in its original commit.

The python recipe does something particularly evil, the do_compile pokes file into STAGING_DIR_* directly for various reasons.

The do_install then does save off the files correctly but there is an overwrite situation occurring there and I don't consider the recipe to be doing something particularly nice.

So there is an issue there, it won't break your build but we should really do something better.

Cheers,

Richard

#2 lore raw
Quoted 19 lines · Richard Purdie
Quoted 10 lines · Gary Thomas

I'm getting these new warnings, even with a build from scratch. This is from poky master rev 7c39c87d52c20e47cf90275a16e4517a296c8388

WARNING: The recipe is trying to install files into a shared area when those files already exist. Those files are:

    /home/local/p81_build/tmp/sysroots/cobra3530p81/usr/include/python2.7/pyconfig.h
    /home/local/p81_build/tmp/sysroots/cobra3530p81/usr/lib/libpython2.7.so
    /home/local/p81_build/tmp/sysroots/cobra3530p81/usr/lib/libpython2.7.so.1.0
    /home/local/p81_build/tmp/sysroots/cobra3530p81/usr/lib/python2.7/config/Makefile

Do they hurt anything? Why am I getting them now, what's changed, etc?

I fixed the code that was supposed to be generate these messages and we started seeing them. Its a new type of check added relatively recently but was accidentally disabled in its original commit.

The python recipe does something particularly evil, the do_compile pokes file into STAGING_DIR_* directly for various reasons.

Quoted 7 lines

The do_install then does save off the files correctly but there is an overwrite situation occurring there and I don't consider the recipe to be doing something particularly nice.

So there is an issue there, it won't break your build but we should really do something better.

yeah probably we need two stage approach may be a python-initial and then real python.

Quoted 8 lines

Cheers,

Richard

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky