Skip to contentSkip to conversation

:gdk-pixbuf: Add --with-x11 when building lsb image

PATCH In review Xiaofeng Yan 5 participants 15 messages Apr 24, 2012 – Apr 27, 2012

lore
Share & tools
lore

Xiaofeng Yan

author
#0 lore raw

cover :gdk-pixbuf: Add --with-x11 when building lsb image

From: Xiaofeng Yan <[email protected]>

LSB Test Suite complain "no library libgdk_pixbuf_xlib-2.0.so.0" \
because of having "--without-x11" for gdk-pixbuf_2.24.1.bb. For passing lsb test I add PACKAGECONFIG support to the recipe and \
have poky-lsb turn on the poky-lsb distro for this recipe.

Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: xiaofeng/2248
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=xiaofeng/2248

Thanks,
Xiaofeng Yan <[email protected]>
---

Xiaofeng Yan (1):
gdk-pixbuf: Add --with-x11 when building lsb image

 meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.24.1.bb |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)
author
#1 lore raw

PATCH 1/1 gdk-pixbuf: Add --with-x11 when building lsb image

From: Xiaofeng Yan <[email protected]>

LSB Test Suite complain "no library libgdk_pixbuf_xlib-2.0.so.0" \
because of having "--without-x11" for gdk-pixbuf_2.24.1.bb. For passing lsb test I add PACKAGECONFIG support to the recipe and \
have poky-lsb turn on the poky-lsb distro for this recipe.

[YOCTO #2284]

Signed-off-by Xiaofeng Yan <[email protected]>
---
 meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.24.1.bb |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)
meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.24.1.bb +2 -1
index e31f717..33627a3 100644
@@ -28,9 +28,10 @@ LIBV = "2.10.0"
 EXTRA_OECONF = "\
   --without-libtiff \
   --with-libpng \
-  --without-x11 \
   --disable-introspection \
 "
+PACKAGECONFIG ??= "${@base_contains('DISTRO', 'poky-lsb', 'poky-lsb', '', d)}"
+PACKAGECONFIG[poky-lsb] = "--with-x11,--without-x11,,"
 
 FILES_${PN} = "${bindir}/gdk-pixbuf-query-loaders \
 	${libdir}/lib*.so.*"
Signature · 1 line
1.7.0.4
#2 lore raw

Re: [PATCH 1/1] gdk-pixbuf: Add --with-x11 when building lsb image

Op 24 apr. 2012, om 07:50 heeft Xiaofeng Yan het volgende geschreven:

Quoted 8 lines

From: Xiaofeng Yan <[email protected]>

LSB Test Suite complain "no library libgdk_pixbuf_xlib-2.0.so.0" \
because of having "--without-x11" for gdk-pixbuf_2.24.1.bb. For passing lsb test I add PACKAGECONFIG support to the recipe and \
have poky-lsb turn on the poky-lsb distro for this recipe.

[YOCTO #2284]

Shouldn't this be an 'x11' DISTRO_FEATURE instead?

author
#3 lore raw

Re: [PATCH 1/1] gdk-pixbuf: Add --with-x11 when building lsb image

Quoted 11 lines · Koen Kooi

Op 24 apr. 2012, om 07:50 heeft Xiaofeng Yan het volgende geschreven:

Quoted 8 lines

From: Xiaofeng Yan<[email protected]>

LSB Test Suite complain "no library libgdk_pixbuf_xlib-2.0.so.0" \
because of having "--without-x11" for gdk-pixbuf_2.24.1.bb. For passing lsb test I add PACKAGECONFIG support to the recipe and \
have poky-lsb turn on the poky-lsb distro for this recipe.

[YOCTO #2284]

Shouldn't this be an 'x11' DISTRO_FEATURE instead?

because "--without-x11" is disabled when x11 exists in core-image-sato. Using 'x11' DISTRO_FEATURE instead will change the default set, which will cause enable "--with-x11" when x11 is in DISTRO_FEATURE. LSB Test Suite need this configuration but other image may not need it even if having x11.

Quoted 6 lines

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

#4 lore raw

Re: [PATCH 1/1] gdk-pixbuf: Add --with-x11 when building lsb image

Op 24 apr. 2012, om 08:12 heeft Xiaofeng Yan het volgende geschreven:

Quoted 12 lines · Koen Kooi
Quoted 11 lines

Op 24 apr. 2012, om 07:50 heeft Xiaofeng Yan het volgende geschreven:

Quoted 8 lines

From: Xiaofeng Yan <[email protected]>

LSB Test Suite complain "no library libgdk_pixbuf_xlib-2.0.so.0" \
because of having "--without-x11" for gdk-pixbuf_2.24.1.bb. For passing lsb test I add PACKAGECONFIG support to the recipe and \
have poky-lsb turn on the poky-lsb distro for this recipe.

Quoted 5 lines
Quoted 4 lines
Quoted 2 lines

[YOCTO #2284]

Shouldn't this be an 'x11' DISTRO_FEATURE instead?

because "--without-x11" is disabled when x11 exists in core-image-sato. Using 'x11' DISTRO_FEATURE instead will change the default set, which will cause enable "--with-x11" when x11 is in DISTRO_FEATURE. LSB Test Suite need this configuration but other image may not need it even if having x11.

What use-case is there for having 'x11' in DISTRO_FEATURES but not wanting x11 support in pixbuf?

Regardless of that, poky-lsb distro overrides have no place in oe-core, they should go into their own layer as bbappends.

regards,

Koen

#5 lore raw

Re: [PATCH 1/1] gdk-pixbuf: Add --with-x11 when building lsb image

Quoted 16 lines · Koen Kooi

Op 24 apr. 2012, om 08:12 heeft Xiaofeng Yan het volgende geschreven:

Quoted 14 lines · Koen Kooi
Quoted 13 lines

Op 24 apr. 2012, om 07:50 heeft Xiaofeng Yan het volgende geschreven:

Quoted 10 lines

From: Xiaofeng Yan <[email protected]>

LSB Test Suite complain "no library libgdk_pixbuf_xlib-2.0.so.0" \
because of having "--without-x11" for gdk-pixbuf_2.24.1.bb. For passing lsb test I add PACKAGECONFIG support to the recipe and \
have poky-lsb turn on the poky-lsb distro for this recipe.

[YOCTO #2284]

Quoted 7 lines
Quoted 3 lines
Quoted 2 lines

Shouldn't this be an 'x11' DISTRO_FEATURE instead?

because "--without-x11" is disabled when x11 exists in core-image-sato. Using 'x11' DISTRO_FEATURE instead will change the default set, which will cause enable "--with-x11" when x11 is in DISTRO_FEATURE. LSB Test Suite need this configuration but other image may not need it even if having x11.

What use-case is there for having 'x11' in DISTRO_FEATURES but not wanting x11 support in pixbuf?

Regardless of that, poky-lsb distro overrides have no place in oe-core, they should go into their own layer as bbappends.

We should be using the linuxstdbase override and also make it conditional on x11 being in DISTRO_FEATURES.

As far as I can tell nothing uses/cares about this library apart from lsb right now. If that changes I'm happy to build more of the time but until we need it, its pointless. We should also split it into a separate package.

Cheers,

Richard

author
#6 lore raw

Re: [PATCH 1/1] gdk-pixbuf: Add --with-x11 when building lsb image

Quoted 17 lines · Richard Purdie
Quoted 16 lines · Koen Kooi

Op 24 apr. 2012, om 08:12 heeft Xiaofeng Yan het volgende geschreven:

Quoted 14 lines · Koen Kooi
Quoted 13 lines

Op 24 apr. 2012, om 07:50 heeft Xiaofeng Yan het volgende geschreven:

Quoted 10 lines

From: Xiaofeng Yan<[email protected]>

LSB Test Suite complain "no library libgdk_pixbuf_xlib-2.0.so.0" \
because of having "--without-x11" for gdk-pixbuf_2.24.1.bb. For passing lsb test I add PACKAGECONFIG support to the recipe and \
have poky-lsb turn on the poky-lsb distro for this recipe.

[YOCTO #2284]

Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
Quoted 2 lines

Shouldn't this be an 'x11' DISTRO_FEATURE instead?

because "--without-x11" is disabled when x11 exists in core-image-sato. Using 'x11' DISTRO_FEATURE instead will change the default set, which will cause enable "--with-x11" when x11 is in DISTRO_FEATURE. LSB Test Suite need this configuration but other image may not need it even if having x11.

What use-case is there for having 'x11' in DISTRO_FEATURES but not wanting x11 support in pixbuf?

Regardless of that, poky-lsb distro overrides have no place in oe-core, they should go into their own layer as bbappends.

We should be using the linuxstdbase override and also make it conditional on x11 being in DISTRO_FEATURES.

You mean I should use the following methods in gdk-pixbuf_2.24.1.bb EXTRA_OECONF_append_linuxstdbase = " ${@base_contains('DISTRO_FEATURES', 'x11', '--with-x11', '--without-x11', d)}"

The above variable should be putted into gdk-pixbuf_2.24.1.bb because poky-lsb.conf is parsed before this bb file. right ??

Quoted 15 lines

As far as I can tell nothing uses/cares about this library apart from lsb right now. If that changes I'm happy to build more of the time but until we need it, its pointless. We should also split it into a separate package.

Cheers,

Richard

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

#7 lore raw

Error compiling Boost with Python support on 64-bit host for 32-bit target.

In reply to Xiaofeng Yan

boost.inc:

# To enable python, uncomment the following:
#BOOST_LIBS += "python"
#DEPENDS += "python"
#PYTHON_ROOT = "${STAGING_DIR_HOST}/${prefix}"
#PYTHON_VERSION = "2.5"

If this is uncommented, stuff fails with messages like:

| ...failed gcc.compile.c++ bin.v2/libs/python/build/69ffc88faf507005827aa061bd65b9bd/wrapper.o...
| gcc.compile.c++ bin.v2/libs/python/build/69ffc88faf507005827aa061bd65b9bd/import.o
| In file included from /src/openembedded/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/include/python2.7/Python.h:58:0,
|                  from ./boost/python/detail/wrap_python.hpp:142,
|                  from ./boost/python/detail/prefix.hpp:13,
|                  from ./boost/python/ssize_t.hpp:9,
|                  from ./boost/python/object.hpp:8,
|                  from ./boost/python/import.hpp:8,
|                  from libs/python/src/import.cpp:6:
| /src/openembedded/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/include/python2.7/pyport.h:849:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."

I have problems figuring out how to solve this (other than by reinstalling Ubuntu 32-bit).

- Tasslehoff

#8 lore raw

Re: Error compiling Boost with Python support on 64-bit host for 32-bit target.

Ouch. Didn't mean to make this a part of another thread. Sorry about that.

#9 lore raw

Re: Error compiling Boost with Python support on 64-bit host for 32-bit target.

In reply to Tasslehoff Kjappfot
Quoted 23 lines · Tasslehoff Kjappfot

boost.inc:

# To enable python, uncomment the following:
#BOOST_LIBS += "python"
#DEPENDS += "python"
#PYTHON_ROOT = "${STAGING_DIR_HOST}/${prefix}"
#PYTHON_VERSION = "2.5"

If this is uncommented, stuff fails with messages like:

| ...failed gcc.compile.c++ bin.v2/libs/python/build/69ffc88faf507005827aa061bd65b9bd/wrapper.o...
| gcc.compile.c++
bin.v2/libs/python/build/69ffc88faf507005827aa061bd65b9bd/import.o
| In file included from /src/openembedded/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/include/python2.7/Python.h:58:0,

|                  from ./boost/python/detail/wrap_python.hpp:142,
|                  from ./boost/python/detail/prefix.hpp:13,
|                  from ./boost/python/ssize_t.hpp:9,
|                  from ./boost/python/object.hpp:8,
|                  from ./boost/python/import.hpp:8,
|                  from libs/python/src/import.cpp:6:
|
Quoted 6 lines

/src/openembedded/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/include/python2.7/pyport.h:849:2:
error: #error "LONG_BIT definition appears wrong for platform (bad
gcc/glibc config?)."

I have problems figuring out how to solve this (other than by reinstalling Ubuntu 32-bit).

You have to wonder why its looking in the native sysroot and not the target one. It would probably find better values in the target one...

Cheers,

Richard

#10 lore raw

Re: Error compiling Boost with Python support on 64-bit host for 32-bit target.

Quoted 30 lines · Richard Purdie
Quoted 23 lines · Tasslehoff Kjappfot

boost.inc:

# To enable python, uncomment the following:
#BOOST_LIBS += "python"
#DEPENDS += "python"
#PYTHON_ROOT = "${STAGING_DIR_HOST}/${prefix}"
#PYTHON_VERSION = "2.5"

If this is uncommented, stuff fails with messages like:

| ...failed gcc.compile.c++ bin.v2/libs/python/build/69ffc88faf507005827aa061bd65b9bd/wrapper.o...
| gcc.compile.c++
bin.v2/libs/python/build/69ffc88faf507005827aa061bd65b9bd/import.o
| In file included from /src/openembedded/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/include/python2.7/Python.h:58:0,

|                  from ./boost/python/detail/wrap_python.hpp:142,
|                  from ./boost/python/detail/prefix.hpp:13,
|                  from ./boost/python/ssize_t.hpp:9,
|                  from ./boost/python/object.hpp:8,
|                  from ./boost/python/import.hpp:8,
|                  from libs/python/src/import.cpp:6:
|
Quoted 6 lines

/src/openembedded/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/include/python2.7/pyport.h:849:2:
error: #error "LONG_BIT definition appears wrong for platform (bad
gcc/glibc config?)."

I have problems figuring out how to solve this (other than by reinstalling Ubuntu 32-bit).

Quoted 7 lines

You have to wonder why its looking in the native sysroot and not the target one. It would probably find better values in the target one...

Cheers,

Richard
d-core

I thought so too, but I wasn't able to convince it to do so. Will have to try harder :)

#11 lore raw

PATCH 1/1 boost: set python-root correctly

In reply to Tasslehoff Kjappfot
---
 meta/recipes-support/boost/boost.inc       |    8 +++++++-
 meta/recipes-support/boost/boost_1.49.0.bb |    2 +-
 2 files changed, 8 insertions(+), 2 deletions(-)
meta/recipes-support/boost/boost.inc +7 -1
index c9306df..fbdf292 100644
@@ -42,7 +42,7 @@ BOOST_LIBS = "\
 #BOOST_LIBS += "python"
 #DEPENDS += "python"
 #PYTHON_ROOT = "${STAGING_DIR_HOST}/${prefix}"
-#PYTHON_VERSION = "2.5"
+#PYTHON_VERSION = "2.7"
 
 # Make a package for each library, plus -dev
 PACKAGES = "${PN}-dbg ${BOOST_PACKAGES}"

@@ -123,6 +123,7 @@ BJAM_TOOLS   = "-sTOOLS=gcc \
 		'-sNO_ZLIB=1' \
 		'-sBUILD=release <optimization>space <threading>multi <inlining>on <debug-symbols>off' \
 		'-sPYTHON_VERSION=${PYTHON_VERSION}' \
+		'-sPYTHON_ROOT=${PYTHON_ROOT}' \
 		'--layout=system' \
 		"
 

@@ -140,6 +141,11 @@ do_boostconfig() {
 	then
 		echo 'using gcc : 4.3.1 : ${CXX} : compileflags -DBOOST_SP_USE_PTHREADS -I${includedir} linkflags -L${libdir} ;' >> ${S}/tools/build/v2/user-config.jam
 	fi	
+
+        echo "using python : ${PYTHON_VERSION} : : ${STAGING_INCDIR}/python${PYTHON_VERSION} ;" >> ${S}/tools/build/v2/user-config.jam
+
+        CC="${BUILD_CC}" CFLAGS="${BUILD_CFLAGS}" ./bootstrap.sh --with-toolset=gcc --with-python-root=${PYTHON_ROOT}
+        sed -i '/^using python/d' project-config.jam
 }
 
 addtask do_boostconfig after do_patch before do_configure
meta/recipes-support/boost/boost_1.49.0.bb +1 -1
index 71fdc48..533cd10 100644
@@ -2,7 +2,7 @@ include boost.inc
 
 LIC_FILES_CHKSUM = "file://LICENSE_1_0.txt;md5=e4224ccaecb14d942c71d31bef20d78c"
 
-PR = "${INC_PR}.0"
+PR = "${INC_PR}.1"
 
 SRC_URI += "file://arm-intrinsics.patch"
Signature · 1 line
1.7.9.5
#12 lore raw

Re: [PATCH] boost: set python-root correctly

Op 25 apr. 2012, om 01:14 heeft Tasslehoff Kjappfot het volgende geschreven:

Quoted 46 lines

---

meta/recipes-support/boost/boost.inc       |    8 +++++++-
meta/recipes-support/boost/boost_1.49.0.bb |    2 +-
2 files changed, 8 insertions(+), 2 deletions(-)
meta/recipes-support/boost/boost.inc +1 -1
index c9306df..fbdf292 100644
@@ -42,7 +42,7 @@ BOOST_LIBS = "\
 #BOOST_LIBS += "python"
 #DEPENDS += "python"
 #PYTHON_ROOT = "${STAGING_DIR_HOST}/${prefix}"
-#PYTHON_VERSION = "2.5"
+#PYTHON_VERSION = "2.7"
 
 # Make a package for each library, plus -dev

PACKAGES = "${PN}-dbg ${BOOST_PACKAGES}"

meta/recipes-support/boost/boost.inc +6 -0
@@ -123,6 +123,7 @@ BJAM_TOOLS   = "-sTOOLS=gcc \
 		'-sNO_ZLIB=1' \
 		'-sBUILD=release <optimization>space <threading>multi <inlining>on <debug-symbols>off' \
 		'-sPYTHON_VERSION=${PYTHON_VERSION}' \
+		'-sPYTHON_ROOT=${PYTHON_ROOT}' \
 		'--layout=system' \
 		"
 

@@ -140,6 +141,11 @@ do_boostconfig() {
 	then
 		echo 'using gcc : 4.3.1 : ${CXX} : compileflags -DBOOST_SP_USE_PTHREADS -I${includedir} linkflags -L${libdir} ;' >> ${S}/tools/build/v2/user-config.jam
 	fi	
+
+        echo "using python : ${PYTHON_VERSION} : : ${STAGING_INCDIR}/python${PYTHON_VERSION} ;" >> ${S}/tools/build/v2/user-config.jam
+
+        CC="${BUILD_CC}" CFLAGS="${BUILD_CFLAGS}" ./bootstrap.sh --with-toolset=gcc --with-python-root=${PYTHON_ROOT}
+        sed -i '/^using python/d' project-config.jam
 }

addtask do_boostconfig after do_patch before do_configure

meta/recipes-support/boost/boost_1.49.0.bb +0 -0
index 71fdc48..533cd10 100644
@@ -2,7 +2,7 @@ include boost.inc

LIC_FILES_CHKSUM = "file://LICENSE_1_0.txt;md5=e4224ccaecb14d942c71d31bef20d78c"

meta/recipes-support/boost/boost_1.49.0.bb include boost.inc · line 5

Quoted 2 lines
meta/recipes-support/boost/boost_1.49.0.bb +1 -1
-PR = "${INC_PR}.0"
+PR = "${INC_PR}.1"

Shouldn't the INC_PR in boost.inc be increased instead?

regards,

Koen

#13 lore raw

PATCH 1/1 boost: set python-root correctly

In reply to Tasslehoff Kjappfot
Signed-off-by Tasslehoff Kjappfot <[email protected]>
---
 meta/recipes-support/boost/boost.inc |   10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)
meta/recipes-support/boost/boost.inc +8 -2
index c9306df..5341a8c 100644
@@ -16,7 +16,7 @@ BOOST_VER = "${@"_".join(d.getVar("PV",1).split("."))}"
 BOOST_MAJ = "${@"_".join(d.getVar("PV",1).split(".")[0:2])}"
 BOOST_P = "boost_${BOOST_VER}"
 
-INC_PR = "r2"
+INC_PR = "r3"
 
 SRC_URI = "${SOURCEFORGE_MIRROR}/${BPN}/${BOOST_P}.tar.bz2"
 

@@ -42,7 +42,7 @@ BOOST_LIBS = "\
 #BOOST_LIBS += "python"
 #DEPENDS += "python"
 #PYTHON_ROOT = "${STAGING_DIR_HOST}/${prefix}"
-#PYTHON_VERSION = "2.5"
+#PYTHON_VERSION = "2.7"
 
 # Make a package for each library, plus -dev
 PACKAGES = "${PN}-dbg ${BOOST_PACKAGES}"

@@ -123,6 +123,7 @@ BJAM_TOOLS   = "-sTOOLS=gcc \
 		'-sNO_ZLIB=1' \
 		'-sBUILD=release <optimization>space <threading>multi <inlining>on <debug-symbols>off' \
 		'-sPYTHON_VERSION=${PYTHON_VERSION}' \
+		'-sPYTHON_ROOT=${PYTHON_ROOT}' \
 		'--layout=system' \
 		"
 

@@ -140,6 +141,11 @@ do_boostconfig() {
 	then
 		echo 'using gcc : 4.3.1 : ${CXX} : compileflags -DBOOST_SP_USE_PTHREADS -I${includedir} linkflags -L${libdir} ;' >> ${S}/tools/build/v2/user-config.jam
 	fi	
+
+        echo "using python : ${PYTHON_VERSION} : : ${STAGING_INCDIR}/python${PYTHON_VERSION} ;" >> ${S}/tools/build/v2/user-config.jam
+
+        CC="${BUILD_CC}" CFLAGS="${BUILD_CFLAGS}" ./bootstrap.sh --with-toolset=gcc --with-python-root=${PYTHON_ROOT}
+        sed -i '/^using python/d' project-config.jam
 }
 
 addtask do_boostconfig after do_patch before do_configure
Signature · 1 line
1.7.9.5
Applied
#14 lore raw

Re: [PATCH] boost: set python-root correctly

Quoted 38 lines · Tasslehoff Kjappfot
Signed-off-by Tasslehoff Kjappfot<[email protected]>
---
  meta/recipes-support/boost/boost.inc |   10 ++++++++--
  1 file changed, 8 insertions(+), 2 deletions(-)
meta/recipes-support/boost/boost.inc +3 -2
index c9306df..5341a8c 100644
@@ -16,7 +16,7 @@ BOOST_VER = "${@"_".join(d.getVar("PV",1).split("."))}"
  BOOST_MAJ = "${@"_".join(d.getVar("PV",1).split(".")[0:2])}"
  BOOST_P = "boost_${BOOST_VER}"
 
-INC_PR = "r2"
+INC_PR = "r3"
 
  SRC_URI = "${SOURCEFORGE_MIRROR}/${BPN}/${BOOST_P}.tar.bz2"
 

@@ -42,7 +42,7 @@ BOOST_LIBS = "\
  #BOOST_LIBS += "python"
  #DEPENDS += "python"
  #PYTHON_ROOT = "${STAGING_DIR_HOST}/${prefix}"
-#PYTHON_VERSION = "2.5"
+#PYTHON_VERSION = "2.7"
 
  # Make a package for each library, plus -dev
  PACKAGES = "${PN}-dbg ${BOOST_PACKAGES}"

@@ -123,6 +123,7 @@ BJAM_TOOLS   = "-sTOOLS=gcc \
  		'-sNO_ZLIB=1' \
  		'-sBUILD=release<optimization>space<threading>multi<inlining>on<debug-symbols>off' \
  		'-sPYTHON_VERSION=${PYTHON_VERSION}' \
+		'-sPYTHON_ROOT=${PYTHON_ROOT}' \
  		'--layout=system' \
  		"
 

@@ -140,6 +141,11 @@ do_boostconfig() {
  	then

meta/recipes-support/boost/boost.inc do_boostconfig() { · line 151

Quoted 10 lines
meta/recipes-support/boost/boost.inc +5 -0
  		echo 'using gcc : 4.3.1 : ${CXX} : compileflags -DBOOST_SP_USE_PTHREADS -I${includedir} linkflags -L${libdir} ;'>>  ${S}/tools/build/v2/user-config.jam
  	fi	
+
+        echo "using python : ${PYTHON_VERSION} : : ${STAGING_INCDIR}/python${PYTHON_VERSION} ;">>  ${S}/tools/build/v2/user-config.jam
+
+        CC="${BUILD_CC}" CFLAGS="${BUILD_CFLAGS}" ./bootstrap.sh --with-toolset=gcc --with-python-root=${PYTHON_ROOT}
+        sed -i '/^using python/d' project-config.jam
  }
 
  addtask do_boostconfig after do_patch before do_configure

Merged into OE-Core

Thanks
Sau!