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

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

[Xiaofeng Yan]

From: Xiaofeng Yan <xiaofeng.yan@windriver.com>

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 <xiaofeng.yan@windriver.com>
---


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(-)

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

[Xiaofeng Yan]

From: Xiaofeng Yan <xiaofeng.yan@windriver.com>

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 <xiaofeng.yan@windriver.com>
---
 meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.24.1.bb |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.24.1.bb b/meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.24.1.bb
index e31f717..33627a3 100644
--- a/meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.24.1.bb
+++ b/meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.24.1.bb
@@ -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.*"
-- 
1.7.0.4

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

[Koen Kooi]

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

> From: Xiaofeng Yan <xiaofeng.yan@windriver.com>
> 
> 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?

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

[Xiaofeng Yan]

[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]

On 2012?04?24? 13:53, Koen Kooi wrote:
> Op 24 apr. 2012, om 07:50 heeft Xiaofeng Yan het volgende geschreven:
>
>> From: Xiaofeng Yan<xiaofeng.yan@windriver.com>
>>
>> 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.

>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>


[-- Attachment #2: Type: text/html, Size: 2525 bytes --]

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

[Koen Kooi]

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

> On 2012年04月24日 13:53, Koen Kooi wrote:
>> Op 24 apr. 2012, om 07:50 heeft Xiaofeng Yan het volgende geschreven:
>> 
>> 
>>> From: Xiaofeng Yan <xiaofeng.yan@windriver.com>
>>> 
>>> 
>>> 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.

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

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

[Richard Purdie]

On Tue, 2012-04-24 at 08:29 +0200, Koen Kooi wrote:
> Op 24 apr. 2012, om 08:12 heeft Xiaofeng Yan het volgende geschreven:
> 
> > On 2012年04月24日 13:53, Koen Kooi wrote:
> >> Op 24 apr. 2012, om 07:50 heeft Xiaofeng Yan het volgende geschreven:
> >> 
> >> 
> >>> From: Xiaofeng Yan <xiaofeng.yan@windriver.com>
> >>> 
> >>> 
> >>> 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.
> 
> 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

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

[Xiaofeng Yan]

On 2012年04月24日 15:29, Richard Purdie wrote:
> On Tue, 2012-04-24 at 08:29 +0200, Koen Kooi wrote:
>> Op 24 apr. 2012, om 08:12 heeft Xiaofeng Yan het volgende geschreven:
>>
>>> On 2012年04月24日 13:53, Koen Kooi wrote:
>>>> Op 24 apr. 2012, om 07:50 heeft Xiaofeng Yan het volgende geschreven:
>>>>
>>>>
>>>>> From: Xiaofeng Yan<xiaofeng.yan@windriver.com>
>>>>>
>>>>>
>>>>> 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.
>> 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 ??
> 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
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

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

[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:
| 
/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

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

[Richard Purdie]

On Tue, 2012-04-24 at 23:02 +0200, Tasslehoff Kjappfot wrote:
> 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).

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

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

[Tasslehoff Kjappfot]

On 04/24/2012 11:44 AM, Richard Purdie wrote:
> On Tue, 2012-04-24 at 23:02 +0200, Tasslehoff Kjappfot wrote:
>> 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).
> 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 :)

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

[Tasslehoff Kjappfot]

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

[PATCH] boost: set python-root correctly

[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(-)

diff --git a/meta/recipes-support/boost/boost.inc b/meta/recipes-support/boost/boost.inc
index c9306df..fbdf292 100644
--- a/meta/recipes-support/boost/boost.inc
+++ b/meta/recipes-support/boost/boost.inc
@@ -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
diff --git a/meta/recipes-support/boost/boost_1.49.0.bb b/meta/recipes-support/boost/boost_1.49.0.bb
index 71fdc48..533cd10 100644
--- a/meta/recipes-support/boost/boost_1.49.0.bb
+++ b/meta/recipes-support/boost/boost_1.49.0.bb
@@ -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"
 
-- 
1.7.9.5

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

[Koen Kooi]

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

> ---
> meta/recipes-support/boost/boost.inc       |    8 +++++++-
> meta/recipes-support/boost/boost_1.49.0.bb |    2 +-
> 2 files changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/recipes-support/boost/boost.inc b/meta/recipes-support/boost/boost.inc
> index c9306df..fbdf292 100644
> --- a/meta/recipes-support/boost/boost.inc
> +++ b/meta/recipes-support/boost/boost.inc
> @@ -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
> diff --git a/meta/recipes-support/boost/boost_1.49.0.bb b/meta/recipes-support/boost/boost_1.49.0.bb
> index 71fdc48..533cd10 100644
> --- a/meta/recipes-support/boost/boost_1.49.0.bb
> +++ b/meta/recipes-support/boost/boost_1.49.0.bb
> @@ -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"

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

regards,

Koen

[PATCH] boost: set python-root correctly

[Tasslehoff Kjappfot]

Signed-off-by: Tasslehoff Kjappfot <tasskjapp@gmail.com>
---
 meta/recipes-support/boost/boost.inc |   10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-support/boost/boost.inc b/meta/recipes-support/boost/boost.inc
index c9306df..5341a8c 100644
--- a/meta/recipes-support/boost/boost.inc
+++ b/meta/recipes-support/boost/boost.inc
@@ -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
-- 
1.7.9.5

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

[Saul Wold]

On 04/24/2012 05:12 PM, Tasslehoff Kjappfot wrote:
>
> Signed-off-by: Tasslehoff Kjappfot<tasskjapp@gmail.com>
> ---
>   meta/recipes-support/boost/boost.inc |   10 ++++++++--
>   1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-support/boost/boost.inc b/meta/recipes-support/boost/boost.inc
> index c9306df..5341a8c 100644
> --- a/meta/recipes-support/boost/boost.inc
> +++ b/meta/recipes-support/boost/boost.inc
> @@ -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


Merged into OE-Core

Thanks
	Sau!

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

[Xiaofeng Yan]

From: Xiaofeng Yan <xiaofeng.yan@windriver.com>

Hi Richard,

This is V2 for fixing bug 2284. I made some modification according to your suggestion.
Please review it again. 

The following was your suggestion:
We should be using the linuxstdbase override and also make it
conditional on x11 being in DISTRO_FEATURES.

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

Thanks,
    Xiaofeng Yan <xiaofeng.yan@windriver.com>
---


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

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