Re: [yocto] Help with building app recipe

2014-05-22 Thread Diego Sueiro
Folks,

I'm trying to accomplish this in a 64bits host machine. But I'm getting
errors the following error on compile task:

| In file included from
/snip/tmp/sysroots/x86_64-linux/usr/include/python3.3m/Python.h:50:0,
|  from ../../git/src/qpython_priv.h:22,
|  from moc_qpython_priv.cpp:9:
| /snip/sysroots/x86_64-linux/usr/include/python3.3m/pyport.h:820:2:
error: #error LONG_BIT definition appears wrong for platform (bad
gcc/glibc config?).
|  #error LONG_BIT definition appears wrong for platform (bad gcc/glibc
config?).
|   ^


Searching on Google it says that this is a known bug when trying to
cross-compile Python stuff for 32bits machines on 64bits hosts.

It seems that the guys from Buildroot could get this solved:
http://lists.busybox.net/pipermail/buildroot/2011-August/045257.html
I'm trying to find the magical patch to how to get this fixed.

Also found this link too:
http://blog.devork.be/2009/02/compiling-32-bit-python-on-amd64.html

But I'm not quite sure how to get this fixed on Yocto. Should it need to be
fixed on the pyotherside, or python3, or python3-native recipe?


Any directions are appreciated.



Regards,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.brhttp://www.embarcados.com.br/?utm_source=assinatura_diegoutm_medium=e-mailutm_campaign=Assinatura%20Email%20Diego

/*long live rock 'n roll*/


On Sat, May 17, 2014 at 2:18 AM, Khem Raj raj.k...@gmail.com wrote:

 On Fri, May 16, 2014 at 5:33 AM, Neuer User auslands...@gmx.de wrote:
  If I change the sed line to #!/usr/bin/env python3, that would
  probably work then. But would it break something else?

 would be fine.
 --
 ___
 yocto mailing list
 yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Help with building app recipe

2014-05-16 Thread Anders Darander
* Neuer User auslands...@gmx.de [140516 13:24]:

 require recipes-qt/qt5/qt5.inc
 


 It is WIP, so e.g. the license is stil wrong.

 The package depends on Qt5 and Python3.

In that case, I would have expected to see 

inherit python3native qmake5 

in your recipe.

 I am currently experiencing two (rather small) problems:

 1.) the configure step does not find python3-config. It is located in
 tmp/sysroots/i686-linux/usr/bin/python3-native

I haven't used python3 in combination with OE yet. Though, this should
likely have been handled by
inherit python3native

Cheers,
Anders

-- 
Anders Darander
ChargeStorm AB / eStorm AB
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Help with building app recipe

2014-05-16 Thread Neuer User
Am 16.05.2014 14:04, schrieb Anders Darander:
 * Neuer User auslands...@gmx.de [140516 13:24]:
 
 require recipes-qt/qt5/qt5.inc
 
 
 
 It is WIP, so e.g. the license is stil wrong.
 
 The package depends on Qt5 and Python3.
 
 In that case, I would have expected to see 
 
 inherit python3native qmake5 
 
 in your recipe.
 
 I am currently experiencing two (rather small) problems:
 
 1.) the configure step does not find python3-config. It is located in
 tmp/sysroots/i686-linux/usr/bin/python3-native
 
 I haven't used python3 in combination with OE yet. Though, this should
 likely have been handled by
 inherit python3native
 
 Cheers,
 Anders
 

Great, that helped with no 1.). Still a lot to learn for me.

No 2. is still open, though. Is that a problem of my recipe or rather a
generic problem of the python3 recipe? I could patch the python3 recipe,
so that it changes the interpreter line to python3.

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Help with building app recipe

2014-05-16 Thread Neuer User
Am 16.05.2014 14:16, schrieb Neuer User:
 Am 16.05.2014 14:04, schrieb Anders Darander:
 
 Great, that helped with no 1.). Still a lot to learn for me.
 
 No 2. is still open, though. Is that a problem of my recipe or rather a
 generic problem of the python3 recipe? I could patch the python3 recipe,
 so that it changes the interpreter line to python3.
 

Hmm the python3-native recipe has this install function:

--
do_install() {
install -d ${D}${libdir}/pkgconfig
oe_runmake 'DESTDIR=${D}' install
if [ -e ${WORKDIR}/sitecustomize.py ]; then
install -m 0644 ${WORKDIR}/sitecustomize.py
${D}/${libdir}/python${PYTHON_MAJMIN}
fi
install -d ${D}${bindir}/${PN}
install -m 0755 Parser/pgen ${D}${bindir}/${PN}

# Make sure we use /usr/bin/env python
for PYTHSCRIPT in `grep -rIl ${bindir}/${PN}/python
${D}${bindir}/${PN}`; do
sed -i -e '1s|^#!.*|#!/usr/bin/env python|' $PYTHSCRIPT
done
}
--


If I change the sed line to #!/usr/bin/env python3, that would
probably work then. But would it break something else?

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Help with building app recipe

2014-05-16 Thread Khem Raj
On Fri, May 16, 2014 at 5:33 AM, Neuer User auslands...@gmx.de wrote:
 If I change the sed line to #!/usr/bin/env python3, that would
 probably work then. But would it break something else?

would be fine.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto