On Wed, Aug 21, 2013 at 8:46 PM, Victor Kamensky <[email protected]> wrote: > Just to clarify a bit: > > some preexisting layers in Zi's setup also had > python_2.7.3.bbappend with syntax like this > > [kamensky@kamensky-w530 081913_1]$ cat > meta-linaro/meta-bigendian/recipes-devtools/python/python_2.7.3.bbappend > FILESEXTRAPATHS := "${THISDIR}/${PN}" > > SRC_URI += "file://python_ffi_armeb_be8.patch" > > We are wondering why > meta-virtualization/recipes-devtools/python/python_2.7.3.bbappend > redefines FILESPATH in such unusual way, which results that another layer > modification got wiped out. Also it seems that > meta-virtualization/recipes-devtools/python/python/01-use-proper-tools-for-cross-build.patch > patch > already exist in OE defined layer > (poky/meta/recipes-devtools/python/python/01-use-proper-tools-for-cross-build.patch). > With your python_2.7.3.bbappend you make it pick up yours. It is highly > unusual for OE system. Patches are different just a bit: > > [kamensky@kamensky-w530 081913_1]$ diff > meta-virtualization/recipes-devtools/python/python/01-use-proper-tools-for-cross-build.patch > poky/meta/recipes-devtools/python/python/01-use-proper-tools-for-cross-build.patch > 122,124c122,124 > < + lib_dirs = [ os.getenv( "STAGING_LIBDIR" ) ] > < + inc_dirs = [ os.getenv( "STAGING_INCDIR" ) ] > < + lib_dirs += os.getenv('LIBRARY_PATH', '').split(os.pathsep) > --- >> + lib_dirs = [ os.getenv("STAGING_LIBDIR"), >> os.getenv("STAGING_BASELIBDIR") ] >> + inc_dirs = [ os.getenv("STAGING_INCDIR") ] >> + > > If you are unhappy with OE provided > 01-use-proper-tools-for-cross-build.patch patch patch you > could come up with new patch on top of it, but not instead.
The patch is simply a cleanup which hasn't been done it, it isn't used and hasn't been for a while. > > Does this python_2.7.3.bbappend even really needed or it is artifact > of some things in the past? As I mentioned in my first reply: "That being said, we've talked about it before, and it should be we can remove as it isn't necessary anymore." Fixing the old style include path was the quickest thing to do at the time, I've already purged the bbappend locally here, and will make the change in the layer shortly. Cheers, Bruce > > Thanks, > Victor > > On 21 August 2013 16:22, Zi Shen Lim <[email protected]> wrote: >> Hi, >> >> After adding meta-virtualization layer into bblayers.conf, I'm not >> able to build packages. >> Looks like the search path is broken [1]. >> >> As a quick workaround, I removed >> meta-virtualization/recipes-devtools/python/python_2.7.3.bbappend. >> That resolved the issue. >> >> Suggestions? >> >> Thanks, >> z >> >> [1] http://pastebin.com/BmK4QnnE > _______________________________________________ > meta-virtualization mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/meta-virtualization -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" _______________________________________________ meta-virtualization mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-virtualization
