SDK confusion Was: [oe] [meta-oe] gdb-cross-canadian: build gdb with python support

SDK confusion Was: [oe] [meta-oe] gdb-cross-canadian: build gdb with python support

[Martin Jansa]

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

On Fri, Feb 03, 2012 at 08:28:08AM +0100, Martin Jansa wrote:
> On Thu, Feb 02, 2012 at 11:11:27AM +0100, Eric Bénard wrote:
> > Hi Martin,
> > 
> > Le Thu, 2 Feb 2012 10:17:26 +0100,
> > Martin Jansa <martin.jansa@gmail.com> a écrit :
> > > OE @ ~ $ ls /OE/shr-core/tmp/sysroots/x86_64-oesdk-linux-nativesdk/usr/local/
> > > oecore-x86_64-arm
> > > OE @ ~ $ ls /OE/shr-core/tmp/sysroots/x86_64-nativesdk-oesdk-linux/usr/local/
> > > oecore-x86_64-x86_64
> > > 
> > using Angstrom I don't have the same directories here :
> > [ebenard@eb-e6520 setup-scripts]$ ls
> > build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-nativesdk-angstromsdk-linux/usr/local/
> > angstrom-eglibc-x86_64-armv5te
> 
> I usually don't build SDKs, so I'm not really not familiar with
> oesdk-linux-nativesdk and nativesdk-oesdk-linux differences :/
> 
> But I'll try your patch for oe-core
> http://patchwork.openembedded.org/patch/17129/
> with oe-core only (and distroless) and if it behaves the same I'll
> report on oe-core ML.

It fails the same when building from scratch for qemuarm in distroless
oe-core:

bitbake -k gdb-cross-canadian-arm
...
| checking whether to use python... /OE/oe-core/tmp-eglibc/work/x86_64-nativesdk-oesdk-linux/gdb-cross-canadian-arm-7.3.1-r5.1/python
| checking for python2.7... no
| configure: error: no usable python found at /OE/oe-core/tmp-eglibc/work/x86_64-nativesdk-oesdk-linux/gdb-cross-canadian-arm-7.3.1-r5.1/python
...

from config.log
configure:10465: checking whether to use python
configure:10467: result: /OE/oe-core/tmp-eglibc/work/x86_64-nativesdk-oesdk-linux/gdb-cross-canadian-arm-7.3.1-r5.1/python
configure:10685: checking for python2.7
configure:10703: x86_64-oesdk-linux-gcc  --sysroot=/OE/oe-core/tmp-eglibc/sysroots/x86_64-nativesdk-oesdk-linux -o conftest -isystem/OE/oe-core/tmp-eglibc/sysroots/x86_64-oesdk-linux-nativesdk/usr/local/oecore-x86_64-arm/sysroots/x86_64-oesdk-linux/usr/include -O2 -pipe -isystem/OE/oe-core/tmp-eglibc/sysroots/x86_64-oesdk-linux-nativesdk/usr/local/oecore-x86_64-arm/sysroots/x86_64-oesdk-linux/usr/include  -I/OE/oe-core/tmp-eglibc/sysroots/x86_64-nativesdk-oesdk-linux/usr/local/oecore-x86_64-arm/sysroots/x86_64-oesdk-linux/usr/include/python2.7/  -L/OE/oe-core/tmp-eglibc/sysroots/x86_64-oesdk-linux-nativesdk/usr/local/oecore-x86_64-arm/sysroots/x86_64-oesdk-linux/usr/lib/armv5te-oe-linux-gnueabi -Wl,-rpath-link,/OE/oe-core/tmp-eglibc/sysroots/x86_64-oesdk-linux-nativesdk/usr/local/oecore-x86_64-arm/sysroots/x86_64-oesdk-linux/usr/lib/armv5te-oe-linux-gnueabi -Wl,-rpath,/usr/local/oecore-x86_64-arm/sysroots/x86_64-oesdk-linux/usr/lib/armv5te-oe-linux-gnueabi -Wl,-O1 -L/OE/oe-core/tmp-eglibc/sysroots/x86_64-oesdk-linux-nativesdk/usr/local/oecore-x86_64-arm/sysroots/x86_64-oesdk-linux/lib -Wl,-rpath-link,/OE/oe-core/tmp-eglibc/sysroots/x86_64-oesdk-linux-nativesdk/usr/local/oecore-x86_64-arm/sysroots/x86_64-oesdk-linux/lib -Wl,-rpath,/usr/local/oecore-x86_64-arm/sysroots/x86_64-oesdk-linux/lib -Wl,-O1 conftest.c -lncurses -lz -lm    -L/OE/oe-core/tmp-eglibc/sysroots/x86_64-nativesdk-oesdk-linux/usr/local/oecore-x86_64-arm/sysroots/x86_64-oesdk-linux/usr/lib/armv5te-oe-linux-gnueabi/python2.7/config/config -lpthread -ldl -lutil -lm -lpython2.7 >&5
conftest.c:91:20: fatal error: Python.h: No such file or directory

OE @ ~/oe-core/tmp-eglibc $ find sysroots/ -name python2.7
sysroots/x86_64-linux/usr/bin/python2.7
sysroots/x86_64-linux/usr/lib/python2.7
sysroots/x86_64-linux/usr/include/python2.7
sysroots/qemuarm/usr/lib/python2.7
sysroots/x86_64-nativesdk-oesdk-linux/usr/local/oecore-x86_64-x86_64/sysroots/x86_64-oesdk-linux/usr/lib/python2.7
sysroots/x86_64-nativesdk-oesdk-linux/usr/local/oecore-x86_64-x86_64/sysroots/x86_64-oesdk-linux/usr/include/python2.7

in x86_64-oesdk-linux there are only gcc+binutils crosssdk
binutils-crosssdk-2.22-r2  gcc-crosssdk-4.6.2+svnr181430-r22  gcc-crosssdk-initial-4.6.2+svnr181430-r22  gcc-crosssdk-intermediate-4.6.2+svnr181430-r22
the rest is in 
x86_64-nativesdk-oesdk-linux

gdb-cross-canadian-arm is only package were exec_prefix points to oecore-x86_64-arm
./gdb-cross-canadian-arm-7.3.1-r5.1/temp/run.do_configure.1688
export exec_prefix="/usr/local/oecore-x86_64-arm/sysroots/x86_64-oesdk-linux/usr"

while all nativesdk packages are using oecore-x86_64-x86_64
./python-nativesdk-2.7.2-r0.5/temp/run.do_configure.14043
export exec_prefix="/usr/local/oecore-x86_64-x86_64/sysroots/x86_64-oesdk-linux/usr"

So I think that using exec_prefix/libdir is wrong to when cross-canadian-arm is looking 
for nativesdk headers/libs. Don't know what are correct variables to use...

Cheers,

> 
> Cheers,
> 
> > 
> > > OE @ ~ $ find /OE/shr-core/tmp/sysroots/x86_64-oesdk-linux-nativesdk/usr/local/ -name python2.7
> > > OE @ ~ $ find /OE/shr-core/tmp/sysroots/x86_64-nativesdk-oesdk-linux/usr/local/ -name python2.7
> > > /OE/shr-core/tmp/sysroots/x86_64-nativesdk-oesdk-linux/usr/local/oecore-x86_64-x86_64/sysroots/x86_64-oesdk-linux/usr/lib/python2.7
> > > /OE/shr-core/tmp/sysroots/x86_64-nativesdk-oesdk-linux/usr/local/oecore-x86_64-x86_64/sysroots/x86_64-oesdk-linux/usr/include/python2.7
> > > 
> > strange :
> > $ find build/tmp-angstrom_2010_x-eglibc/sysroots/ -name python2.7
> > build/tmp-angstrom_2010_x-eglibc/sysroots/at91sam9m10g45ek/usr/include/python2.7
> > build/tmp-angstrom_2010_x-eglibc/sysroots/at91sam9m10g45ek/usr/lib/python2.7
> > build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-nativesdk-angstromsdk-linux/usr/local/angstrom-eglibc-x86_64-armv5te/sysroots/x86_64-angstromsdk-linux/usr/include/python2.7
> > build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-nativesdk-angstromsdk-linux/usr/local/angstrom-eglibc-x86_64-armv5te/sysroots/x86_64-angstromsdk-linux/usr/lib/python2.7
> > build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/bin/python2.7
> > build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/include/python2.7
> > build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/lib/python2.7
> > 
> > Eric
> > -- 
> > http://eukrea.com/en/news/104-2012
> > 
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 
> -- 
> Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com



-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: [oe] SDK confusion Was: [meta-oe] gdb-cross-canadian: build gdb with python support

[Eric Bénard]

Hi Martin,

Le Fri, 3 Feb 2012 10:41:05 +0100,
Martin Jansa <martin.jansa@gmail.com> a écrit :
> in x86_64-oesdk-linux there are only gcc+binutils crosssdk
> binutils-crosssdk-2.22-r2  gcc-crosssdk-4.6.2+svnr181430-r22  gcc-crosssdk-initial-4.6.2+svnr181430-r22  gcc-crosssdk-intermediate-4.6.2+svnr181430-r22
> the rest is in 
> x86_64-nativesdk-oesdk-linux
> 
> gdb-cross-canadian-arm is only package were exec_prefix points to oecore-x86_64-arm
> ./gdb-cross-canadian-arm-7.3.1-r5.1/temp/run.do_configure.1688
> export exec_prefix="/usr/local/oecore-x86_64-arm/sysroots/x86_64-oesdk-linux/usr"
> 
> while all nativesdk packages are using oecore-x86_64-x86_64
> ./python-nativesdk-2.7.2-r0.5/temp/run.do_configure.14043
> export exec_prefix="/usr/local/oecore-x86_64-x86_64/sysroots/x86_64-oesdk-linux/usr"
> 
here is the big difference when using Angstrom :
python-nativesdk-2.7.2-r0.5/temp/run.do_configure.30951:73:export
exec_prefix="/usr/local/angstrom-eglibc-x86_64-armv7a/sysroots/x86_64-angstromsdk-linux/usr"
I don't yet know where this difference comes from.

Eric
-- 
http://eukrea.com/en/news/104-2012

Re: [oe] SDK confusion Was: [meta-oe] gdb-cross-canadian: build gdb with python support

[Martin Jansa]

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

On Fri, Feb 03, 2012 at 11:20:37AM +0100, Eric Bénard wrote:
> Hi Martin,
> 
> Le Fri, 3 Feb 2012 10:41:05 +0100,
> Martin Jansa <martin.jansa@gmail.com> a écrit :
> > in x86_64-oesdk-linux there are only gcc+binutils crosssdk
> > binutils-crosssdk-2.22-r2  gcc-crosssdk-4.6.2+svnr181430-r22  gcc-crosssdk-initial-4.6.2+svnr181430-r22  gcc-crosssdk-intermediate-4.6.2+svnr181430-r22
> > the rest is in 
> > x86_64-nativesdk-oesdk-linux
> > 
> > gdb-cross-canadian-arm is only package were exec_prefix points to oecore-x86_64-arm
> > ./gdb-cross-canadian-arm-7.3.1-r5.1/temp/run.do_configure.1688
> > export exec_prefix="/usr/local/oecore-x86_64-arm/sysroots/x86_64-oesdk-linux/usr"
> > 
> > while all nativesdk packages are using oecore-x86_64-x86_64
> > ./python-nativesdk-2.7.2-r0.5/temp/run.do_configure.14043
> > export exec_prefix="/usr/local/oecore-x86_64-x86_64/sysroots/x86_64-oesdk-linux/usr"
> > 
> here is the big difference when using Angstrom :
> python-nativesdk-2.7.2-r0.5/temp/run.do_configure.30951:73:export
> exec_prefix="/usr/local/angstrom-eglibc-x86_64-armv7a/sysroots/x86_64-angstromsdk-linux/usr"
> I don't yet know where this difference comes from.

I also don't really understand using oecore-x86_64-x86_64 when building
for qemuarm

Last part should be TARGET_ARCH from
conf/bitbake.conf:SDK_NAME = "oecore-${SDK_ARCH}-${TARGET_ARCH}"

but TARGET_ARCH is defined couple of times:
conf/bitbake.conf:TARGET_ARCH = "${TUNE_ARCH}"

classes/native.bbclass:TARGET_ARCH = "${BUILD_ARCH}"
classes/crosssdk.bbclass:TARGET_ARCH = "${SDK_ARCH}"
classes/nativesdk.bbclass:TARGET_ARCH = "${SDK_ARCH}"

So it looks like TARGET_ARCH from bitbake.conf wins for you and here
it's using TARGET_ARCH = "${SDK_ARCH}" from nativesdk.bbclass

With following modification I was able to configure and build it fine,
but seems like your oecore-x86_64-arm correct and oecore-x86_64-x86_64
should be used only e.g. for qemux86-64 not qemuarm

Cheers,

diff --git a/meta/recipes-devtools/gdb/gdb-cross-canadian.inc b/meta/recipes-devtools/gdb/gdb-cross-canadian.inc
index b5746ce..bac63b7 100644
--- a/meta/recipes-devtools/gdb/gdb-cross-canadian.inc
+++ b/meta/recipes-devtools/gdb/gdb-cross-canadian.inc
@@ -10,12 +10,18 @@ RDEPENDS += "python-nativesdk-core python-nativesdk-lang python-nativesdk-re \

 EXTRA_OECONF_append = "--with-python=${WORKDIR}/python"

+NATIVESDK_NAME = "oecore-${SDK_ARCH}-${SDK_ARCH}"
+NATIVESDK_PATH = "/usr/local/${NATIVESDK_NAME}"
+NATIVESDK_PATHNATIVE = "${NATIVESDK_PATH}/sysroots/${SDK_SYS}"
+NATIVESDK_LIBDIR = "${NATIVESDK_PATHNATIVE}${libdir_nativesdk}"
+NATIVESDK_INCLUDEDIR = "${NATIVESDK_PATHNATIVE}${includedir_nativesdk}"
+
 do_configure_prepend() {
 cat > ${WORKDIR}/python << EOF
 #! /bin/sh
 case "\$2" in
-        --includes) echo "-I${STAGING_DIR}/${HOST_ARCH}-nativesdk${HOST_VENDOR}-${HOST_OS}${exec_prefix}/include/python${PYTHON_BASEVERSION}/" ;;
-        --ldflags) echo "-L${STAGING_DIR}/${HOST_ARCH}-nativesdk${HOST_VENDOR}-${HOST_OS}${libdir}/python${PYTHON_BASEVERSION}/config/config -lpthread -ldl -lutil -lm -lpython${PYTHON_BASEVERSION}" ;;
+        --includes) echo "-I${STAGING_DIR}/${HOST_ARCH}-nativesdk${HOST_VENDOR}-${HOST_OS}${NATIVESDK_INCLUDEDIR}/python${PYTHON_BASEVERSION}/" ;;
+        --ldflags) echo "-L${STAGING_DIR}/${HOST_ARCH}-nativesdk${HOST_VENDOR}-${HOST_OS}${NATIVESDK_LIBDIR}/python${PYTHON_BASEVERSION}/config -lpthread -ldl -lutil -lm -lpython${PYTHON_BASEVERSION}" ;;
         --exec-prefix) echo "/usr" ;;
         *) exit 1 ;;
 esac

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: [oe] SDK confusion Was: [meta-oe] gdb-cross-canadian: build gdb with python support

[Eric Bénard]

Le Fri, 3 Feb 2012 12:44:51 +0100,
Martin Jansa <martin.jansa@gmail.com> a écrit :
> I also don't really understand using oecore-x86_64-x86_64 when building
> for qemuarm
> 
I may be totally wrong but isn't that what is expected : building a gdb
which will run on the SDK_ARCH (ie x86_64 in my case), so isn't python
expected to run on the x86_64 and target x86_64 (and not arm) ?

Eric
-- 
http://eukrea.com/en/news/104-2012