Re: [yocto] Questions regarding adding a new llvm based cross-compiler
On 16 October 2014 18:46, Cody P Schafer wrote: > Hi all, > > I'm working on creating a layer for the rust compiler (which uses > llvm) and was wondering if there were any best practices and/or > examples people could point me at. I can't really offer much help on the LLVM side, but I can say this will be really useful work. I'm slowly learning Rust and researching how it can be used for embedded development and it will be excellent to have a rust compiler working as part of OpenEmbedded/Yocto. If you need any testing of this layer once it's created, just let me know. Cheers, -- Paul Barker Email: p...@paulbarker.me.uk http://www.paulbarker.me.uk -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] PCEngines APU1c
Am 11.10.2014 um 18:52 schrieb Albert K: > Dear all, > > May I know if anyone has a BSP for PCEngines APU1c ? Thanks. > > Regards. > Probably ask Pascal Dornier from PC engines directly. Although, he mostly only focuses on the hardware, but he might at least know... -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] PCEngines APU1c
Hi, I did ask in the PCengines forum but no reply as yet. On Fri, Oct 17, 2014 at 5:46 PM, Neuer User wrote: > Am 11.10.2014 um 18:52 schrieb Albert K: >> Dear all, >> >> May I know if anyone has a BSP for PCEngines APU1c ? Thanks. >> >> Regards. >> > > Probably ask Pascal Dornier from PC engines directly. Although, he > mostly only focuses on the hardware, but he might at least know... > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Updating daisy -> Python.h not found
Hi
Because of shellshock I decided to update my daisy repo to latest
revision (old version was from about June).
Everybody know: "NEVER EVER CHANGE A RUNNING SYSTEM" :-)
Well, I needed to because of shellshock. And now I need to try to repair
everything that broke (currently at 7 packages).
One that I am completely stuck with is a custom recipe (which of course
worked nicely before the repo sync). This is the recipe:
pyotherside.bb:
---
SUMMARY = "Python3 bindings for Qt5"
DESCRIPTION = "New framework for including python interpreter into Qt5 apps"
HOMEPAGE = "http://thp.io/2011/pyotherside/";
LICENSE = "MIT"
LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
PV = "1.3+git${SRCPV}"
SRCREV = "f870396346bec40b1bb64f95e27d4e3dafeda799"
SRC_URI = "git://github.com/thp/pyotherside.git;branch=master;protocol=git"
S = "${WORKDIR}/git/"
DEPENDS = "qtdeclarative python3 python3-native"
RDEPENDS_${PN} = "qtdeclarative-qmlplugins"
inherit python3native
require recipes-qt/qt5/qt5.inc
I did need to bbappend the original python3 recipe with this here (just
the last part is changed), because python-config used python2.7 instead
of 3.3:
python3-native_3.3.3.bbappend:
--
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 python3
for PYTHSCRIPT in `grep -rIl ${bindir}/${PN}/python
${D}${bindir}/${PN}`; do
sed -i -e '1s|^#!.*|#!/usr/bin/env python3|' $PYTHSCRIPT
done
}
Unfortunately, after upgrading daisy I get the following error during
compilation:
In file included from ../../git/src/pyotherside_plugin.cpp:19:0:
../../git/src/qpython_priv.h:22:20: fatal error: Python.h: No such file
or directory
#include "Python.h"
^
compilation terminated.
In file included from ../../git/src/qml_python_bridge.h:22:0,
from ../../git/src/qpython.cpp:19:
../../git/src/pyobject_converter.h:24:20: fatal error: Python.h: No such
file or directory
#include "Python.h"
^
compilation terminated.
make[1]: *** [pyotherside_plugin.o] Error 1
make[1]: *** Waiting for unfinished jobs
make[1]: *** [qpython.o] Error 1
In file included from ../../git/src/qpython_imageprovider.cpp:19:0:
../../git/src/qpython_priv.h:22:20: fatal error: Python.h: No such file
or directory
#include "Python.h"
^
compilation terminated.
In file included from ../../git/src/qml_python_bridge.h:22:0,
from ../../git/src/qpython_priv.cpp:19:
../../git/src/pyobject_converter.h:24:20: fatal error: Python.h: No such
file or directory
#include "Python.h"
^
compilation terminated.
make[1]: *** [qpython_priv.o] Error 1
make[1]: *** [qpython_imageprovider.o] Error 1
../../git/src/global_libpython_loader.cpp:25:0: warning: "_GNU_SOURCE"
redefined [enabled by default]
#define _GNU_SOURCE
^
:0:0: note: this is the location of the previous definition
../../git/src/global_libpython_loader.cpp:31:12: warning: unused
parameter 'size' [-Wunused-parameter]
static int load_python_globally_callback(struct dl_phdr_info *info,
size_t size, void *data)
^
make[1]: Leaving directory
`/home/ubuntu/yocto/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/pyotherside/1.3+gitAUTOINC+f870396346-r0/build/src'
make: *** [sub-src-make_first] Error 2
ERROR: oe_runmake failed
WARNING: exit code 1 from a shell command.
Does anybody have any idea, why Python.h is no longer found?
$ find tmp/work -name "Python.h"
tmp/work/i686-linux/python3-native/3.3.3-r0.0/sysroot-destdir/home/ubuntu/yocto/build/tmp/sysroots/i686-linux/usr/include/python3.3m/Python.h
tmp/work/i686-linux/python3-native/3.3.3-r0.0/Python-3.3.3/Include/Python.h
tmp/work/i686-linux/python-native/2.7.3-r0.1/Python-2.7.3/Include/Python.h
tmp/work/i686-linux/python-native/2.7.3-r0.1/image/home/ubuntu/yocto/build/tmp/sysroots/i686-linux/usr/include/python2.7/Python.h
tmp/work/i686-linux/python-native/2.7.3-r0.1/sysroot-destdir/home/ubuntu/yocto/build/tmp/sysroots/i686-linux/usr/include/python2.7/Python.h
tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/python3/3.3.3-r0.0/package/usr/include/python3.3m/Python.h
tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/python3/3.3.3-r0.0/sysroot-destdir/usr/include/python3.3m/Python.h
tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/python3/3.3.3-r0.0/packages-split/python3-dev/usr/include/python3.3m/Python.h
tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/python/2.7.3-r0.3/Python-2.7.3/Include/Python.h
tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/python/2.7.3-r0.3/package/usr/include/python2.7/Python.h
tmp/work/
Re: [yocto] Updating daisy -> Python.h not found
Hi there,
On Friday 17 October 2014 12:00:23 Neuer User wrote:
> Because of shellshock I decided to update my daisy repo to latest
> revision (old version was from about June).
>
> Everybody know: "NEVER EVER CHANGE A RUNNING SYSTEM" :-)
> Well, I needed to because of shellshock. And now I need to try to repair
> everything that broke (currently at 7 packages).
>
> One that I am completely stuck with is a custom recipe (which of course
> worked nicely before the repo sync). This is the recipe:
>
> pyotherside.bb:
> ---
> SUMMARY = "Python3 bindings for Qt5"
> DESCRIPTION = "New framework for including python interpreter into Qt5 apps"
> HOMEPAGE = "http://thp.io/2011/pyotherside/";
> LICENSE = "MIT"
> LIC_FILES_CHKSUM =
> "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
>
> PV = "1.3+git${SRCPV}"
>
> SRCREV = "f870396346bec40b1bb64f95e27d4e3dafeda799"
>
> SRC_URI = "git://github.com/thp/pyotherside.git;branch=master;protocol=git"
>
> S = "${WORKDIR}/git/"
>
> DEPENDS = "qtdeclarative python3 python3-native"
> RDEPENDS_${PN} = "qtdeclarative-qmlplugins"
>
> inherit python3native
>
> require recipes-qt/qt5/qt5.inc
>
>
> I did need to bbappend the original python3 recipe with this here (just
> the last part is changed), because python-config used python2.7 instead
> of 3.3:
>
> python3-native_3.3.3.bbappend:
> --
> 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 python3
> for PYTHSCRIPT in `grep -rIl ${bindir}/${PN}/python
> ${D}${bindir}/${PN}`; do
> sed -i -e '1s|^#!.*|#!/usr/bin/env python3|' $PYTHSCRIPT
> done
> }
>
>
> Unfortunately, after upgrading daisy I get the following error during
> compilation:
>
> In file included from ../../git/src/pyotherside_plugin.cpp:19:0:
> ../../git/src/qpython_priv.h:22:20: fatal error: Python.h: No such file
> or directory
> #include "Python.h"
> ^
> compilation terminated.
> In file included from ../../git/src/qml_python_bridge.h:22:0,
> from ../../git/src/qpython.cpp:19:
> ../../git/src/pyobject_converter.h:24:20: fatal error: Python.h: No such
> file or directory
> #include "Python.h"
> ^
> compilation terminated.
> make[1]: *** [pyotherside_plugin.o] Error 1
> make[1]: *** Waiting for unfinished jobs
> make[1]: *** [qpython.o] Error 1
> In file included from ../../git/src/qpython_imageprovider.cpp:19:0:
> ../../git/src/qpython_priv.h:22:20: fatal error: Python.h: No such file
> or directory
> #include "Python.h"
> ^
> compilation terminated.
> In file included from ../../git/src/qml_python_bridge.h:22:0,
> from ../../git/src/qpython_priv.cpp:19:
> ../../git/src/pyobject_converter.h:24:20: fatal error: Python.h: No such
> file or directory
> #include "Python.h"
> ^
> compilation terminated.
> make[1]: *** [qpython_priv.o] Error 1
> make[1]: *** [qpython_imageprovider.o] Error 1
> ../../git/src/global_libpython_loader.cpp:25:0: warning: "_GNU_SOURCE"
> redefined [enabled by default]
> #define _GNU_SOURCE
> ^
> :0:0: note: this is the location of the previous definition
> ../../git/src/global_libpython_loader.cpp:31:12: warning: unused
> parameter 'size' [-Wunused-parameter]
> static int load_python_globally_callback(struct dl_phdr_info *info,
> size_t size, void *data)
> ^
> make[1]: Leaving directory
> `/home/ubuntu/yocto/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/py
> otherside/1.3+gitAUTOINC+f870396346-r0/build/src' make: ***
> [sub-src-make_first] Error 2
> ERROR: oe_runmake failed
> WARNING: exit code 1 from a shell command.
>
>
> Does anybody have any idea, why Python.h is no longer found?
>
> $ find tmp/work -name "Python.h"
> tmp/work/i686-linux/python3-native/3.3.3-r0.0/sysroot-destdir/home/ubuntu/yo
> cto/build/tmp/sysroots/i686-linux/usr/include/python3.3m/Python.h
> tmp/work/i686-linux/python3-native/3.3.3-r0.0/Python-3.3.3/Include/Python.h
> tmp/work/i686-linux/python-native/2.7.3-r0.1/Python-2.7.3/Include/Python.h
> tmp/work/i686-linux/python-native/2.7.3-r0.1/image/home/ubuntu/yocto/build/
> tmp/sysroots/i686-linux/usr/include/python2.7/Python.h
> tmp/work/i686-linux/python-native/2.7.3-r0.1/sysroot-destdir/home/ubuntu/yo
> cto/build/tmp/sysroots/i686-linux/usr/include/python2.7/Python.h
> tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/python3/3.3.3-r0.0/package/
> usr/include/python3.3m/Python.h
> tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/python3/3.3.3-r0.0/sysroot-
> destdir/usr/include/python3.3m/Python.h
> tmp/work/cortexa
Re: [yocto] Updating daisy -> Python.h not found
Am 17.10.2014 um 16:51 schrieb Paul Eggleton: > Hi there, > > I agree this sort of thing shouldn't happen on a stable branch. I'm not sure > what would have caused such a problem though. However, above you are looking > under tmp/work, but the file being present under there doesn't really say > much > - the key question is is it still in the sysroot i.e. tmp/sysroots/* ? The > first thing to figure out is if the file is really missing, or if it is now > simply not looking for it in the right location. > > Cheers, > Paul > Very good point. $ find tmp/sysroots/ -name "Python.h" tmp/sysroots/i686-linux/usr/include/python2.7/Python.h tmp/sysroots/i686-linux/usr/include/python3.3m/Python.h tmp/sysroots/cubox-i/usr/include/python2.7/Python.h tmp/sysroots/cubox-i/usr/include/python3.3m/Python.h So, it seems to be there, if I see that correctly. The question then seems to be, why it is no longer found? Thanks for you help, Paul. Cheers Michael -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Updating daisy -> Python.h not found
On Friday 17 October 2014 17:01:46 Neuer User wrote: > Am 17.10.2014 um 16:51 schrieb Paul Eggleton: > > Hi there, > > > > I agree this sort of thing shouldn't happen on a stable branch. I'm not > > sure what would have caused such a problem though. However, above you are > > looking under tmp/work, but the file being present under there doesn't > > really say much - the key question is is it still in the sysroot i.e. > > tmp/sysroots/* ? The first thing to figure out is if the file is really > > missing, or if it is now simply not looking for it in the right location. > > > > Cheers, > > Paul > > Very good point. > > $ find tmp/sysroots/ -name "Python.h" > tmp/sysroots/i686-linux/usr/include/python2.7/Python.h > tmp/sysroots/i686-linux/usr/include/python3.3m/Python.h > tmp/sysroots/cubox-i/usr/include/python2.7/Python.h > tmp/sysroots/cubox-i/usr/include/python3.3m/Python.h > > So, it seems to be there, if I see that correctly. The question then > seems to be, why it is no longer found? I'm not sure. That's where you'd need to look at how the software your recipe is building searches for that - the configure log, devshell might be useful for determining that. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Updating daisy -> Python.h not found
Hmm, I looked through the compile log before, but you are right: the
configure log might be more interesting:
There is one error during configure (which, however, did not abort the
process, strangely):
DEBUG: Executing python function sysroot_cleansstate
DEBUG: Python function sysroot_cleansstate finished
DEBUG: Executing shell function qmake5_base_preconfigure
DEBUG: Shell function qmake5_base_preconfigure finished
DEBUG: Executing shell function do_configure
Reading
/home/ubuntu/yocto/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/pyotherside/1.3+gitAUTOINC+f870396346-r0/git/src/src.pro
[/home/ubuntu/yocto/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/pyotherside/1.3+gitAUTOINC+f870396346-r0/build/src]
Project MESSAGE: PYTHON_CONFIG = python3-config
Traceback (most recent call last):
File
"/home/ubuntu/yocto/build/tmp/sysroots/i686-linux/usr/bin/python3-native/python3-config",
line 7, in
from distutils import sysconfig
File
"/home/ubuntu/yocto/build/tmp/sysroots/i686-linux/usr/lib/python3.3/distutils/sysconfig.py",
line 19, in
PREFIX = os.path.normpath(sys.prefix).replace(
os.getenv("BUILD_SYS"), os.getenv("HOST_SYS") )
TypeError: Can't convert 'NoneType' object to str implicitly
Traceback (most recent call last):
File
"/home/ubuntu/yocto/build/tmp/sysroots/i686-linux/usr/bin/python3-native/python3-config",
line 7, in
from distutils import sysconfig
File
"/home/ubuntu/yocto/build/tmp/sysroots/i686-linux/usr/lib/python3.3/distutils/sysconfig.py",
line 19, in
PREFIX = os.path.normpath(sys.prefix).replace(
os.getenv("BUILD_SYS"), os.getenv("HOST_SYS") )
TypeError: Can't convert 'NoneType' object to str implicitly
Reading
/home/ubuntu/yocto/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/pyotherside/1.3+gitAUTOINC+f870396346-r0/git/tests/tests.pro
[/home/ubuntu/yocto/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/pyotherside/1.3+gitAUTOINC+f870396346-r0/build/tests]
Project MESSAGE: PYTHON_CONFIG = python3-config
Traceback (most recent call last):
File
"/home/ubuntu/yocto/build/tmp/sysroots/i686-linux/usr/bin/python3-native/python3-config",
line 7, in
from distutils import sysconfig
File
"/home/ubuntu/yocto/build/tmp/sysroots/i686-linux/usr/lib/python3.3/distutils/sysconfig.py",
line 19, in
PREFIX = os.path.normpath(sys.prefix).replace(
os.getenv("BUILD_SYS"), os.getenv("HOST_SYS") )
TypeError: Can't convert 'NoneType' object to str implicitly
Traceback (most recent call last):
File
"/home/ubuntu/yocto/build/tmp/sysroots/i686-linux/usr/bin/python3-native/python3-config",
line 7, in
from distutils import sysconfig
File
"/home/ubuntu/yocto/build/tmp/sysroots/i686-linux/usr/lib/python3.3/distutils/sysconfig.py",
line 19, in
PREFIX = os.path.normpath(sys.prefix).replace(
os.getenv("BUILD_SYS"), os.getenv("HOST_SYS") )
TypeError: Can't convert 'NoneType' object to str implicitly
DEBUG: Shell function do_configure finished
DEBUG: Executing python function do_qa_configure
NOTE: Checking autotools environment for common misconfiguration
NOTE: pyotherside: md5 checksum matched for
file:///home/ubuntu/yocto/sources/poky/meta/files/common-licenses/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302
DEBUG: Python function do_qa_configure finished
DEBUG: Executing shell function qmake5_base_postconfigure
DEBUG: Shell function qmake5_base_postconfigure finished
Guess this not what it should be, right?
Am 17.10.2014 um 17:05 schrieb Paul Eggleton:
> On Friday 17 October 2014 17:01:46 Neuer User wrote:
>> Am 17.10.2014 um 16:51 schrieb Paul Eggleton:
>>> Hi there,
>>>
>>> I agree this sort of thing shouldn't happen on a stable branch. I'm not
>>> sure what would have caused such a problem though. However, above you are
>>> looking under tmp/work, but the file being present under there doesn't
>>> really say much - the key question is is it still in the sysroot i.e.
>>> tmp/sysroots/* ? The first thing to figure out is if the file is really
>>> missing, or if it is now simply not looking for it in the right location.
>>>
>>> Cheers,
>>> Paul
>>
>> Very good point.
>>
>> $ find tmp/sysroots/ -name "Python.h"
>> tmp/sysroots/i686-linux/usr/include/python2.7/Python.h
>> tmp/sysroots/i686-linux/usr/include/python3.3m/Python.h
>> tmp/sysroots/cubox-i/usr/include/python2.7/Python.h
>> tmp/sysroots/cubox-i/usr/include/python3.3m/Python.h
>>
>> So, it seems to be there, if I see that correctly. The question then
>> seems to be, why it is no longer found?
>
> I'm not sure. That's where you'd need to look at how the software your recipe
> is building searches for that - the configure log, devshell might be useful
> for
> determining that.
>
> Cheers,
> Paul
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] CEWG project BOFS in Dusseldorf (today)
For those of you at plumbers, The CE Workgroup of the Linux Foundation is holding some Birds-Of-a-Feather sessions in Room 02 (not '2', but '02', downstairs), to discuss some initiatives and projects we're working on. Here are the times and topics we're discussing: 2:00-3:00 - Reducing System Size 3:00-4:00 - Making a standard embedded distribution Discussion of the requirements for a standard distribution of Linux, and whether it is needed or not. 4:00-5:00 - Device mainlining Working as an industry to overcome structural obstacles to contributing open source code upstream. (This last one is a follow-on from my talk at ELCE earlier this week) If you're here in Dusseldorf and are interested in any of these project, feel free to come. -- Tim Bird Senior Software Engineer, Sony Mobile Architecture Group Chair, CE Workgroup, Linux Foundation -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Updating daisy -> Python.h not found
Hmm, going deeper into the configure error I found the following:
File
/home/ubuntu/yocto/build/tmp/sysroots/i686-linux/usr/lib/python3.3/distutils/sysconfig.py
contains in line 19:
PREFIX = os.path.normpath(sys.prefix).replace( os.getenv("BUILD_SYS"),
os.getenv("HOST_SYS") )
This gives error
TypeError: Can't convert 'NoneType' object to str implicitly
It does the same if I type this line on python3 on my host computer.
Looking into the sysconfig of python3 of my ubuntu installation, it does
NOT HAVE this line!
here are the lines from python3 sysconfig.py from yocto:
-
"""Provide access to Python's configuration information. The specific
configuration variables available depend heavily on the platform and
configuration. The values may be retrieved using
get_config_var(name), and the list of variables is available via
get_config_vars().keys(). Additional convenience functions are also
available.
Written by: Fred L. Drake, Jr.
Email:
"""
import os
import re
import sys
from .errors import DistutilsPlatformError
# These are needed in a couple of spots, so just compute them once.
PREFIX = os.path.normpath(sys.prefix).replace( os.getenv("BUILD_SYS"),
os.getenv("HOST_SYS") )
EXEC_PREFIX = os.path.normpath(sys.exec_prefix).replace(
os.getenv("BUILD_SYS"), os.getenv("HOST_SYS") )
BASE_PREFIX = os.path.normpath(sys.base_prefix).replace(
os.getenv("BUILD_SYS"), os.getenv("HOST_SYS") )
BASE_EXEC_PREFIX= os.path.normpath(sys.base_exec_prefix).replace(
os.getenv("BUILD_SYS"), os.getenv("HOST_SYS") )
[...]
--
and here from my host pc:
--
"""Provide access to Python's configuration information. The specific
configuration variables available depend heavily on the platform and
configuration. The values may be retrieved using
get_config_var(name), and the list of variables is available via
get_config_vars().keys(). Additional convenience functions are also
available.
Written by: Fred L. Drake, Jr.
Email:
"""
import os
import re
import sys
from .errors import DistutilsPlatformError
# These are needed in a couple of spots, so just compute them once.
PREFIX = os.path.normpath(sys.prefix)
EXEC_PREFIX = os.path.normpath(sys.exec_prefix)
BASE_PREFIX = os.path.normpath(sys.base_prefix)
BASE_EXEC_PREFIX = os.path.normpath(sys.base_exec_prefix)
--
Now, I don't know if that changed with the daisy update, but it
definitely seems to be wrong.
Any python3 expert out there? Can we find out (git blame) when these
lines were changed last?
EDIT: found it, it's this patch:
./poky/meta/recipes-devtools/python/python3/12-distutils-prefix-is-inside-staging-area.patch
and it is from 2013-05-14, so pretty old... :-(
That leaves the question why it gives an error now after updating daisy,
but not before.
Here is the log_configure from before updating daisy:
DEBUG: Executing python function sysroot_cleansstate
DEBUG: Removing manifest:
/home/ubuntu/yocto/build/tmp/sysroots/cubox-i/sysroot-providers/pyotherside
DEBUG: Removing manifest:
/home/ubuntu/yocto/build/tmp/sysroots/cubox-i/usr/lib/qt5/qml/io/thp/pyotherside/qmldir
DEBUG: Removing manifest:
/home/ubuntu/yocto/build/tmp/sysroots/cubox-i/usr/lib/qt5/qml/io/thp/pyotherside/libpyothersideplugin.so
DEBUG: Removing manifest:
/home/ubuntu/yocto/build/tmp/sysroots/cubox-i/usr/lib/qt5/qml/io/thp/pyotherside/
DEBUG: Removing manifest:
/home/ubuntu/yocto/build/tmp/sysroots/cubox-i/usr/lib/qt5/qml/io/thp/
DEBUG: Removing manifest:
/home/ubuntu/yocto/build/tmp/sysroots/cubox-i/usr/lib/qt5/qml/io/
DEBUG: Removing manifest:
/home/ubuntu/yocto/build/tmp/sysroots/cubox-i/sysroot-providers/
DEBUG: Removing manifest:
/home/ubuntu/yocto/build/tmp/sysroots/cubox-i/usr/lib/qt5/qml/
DEBUG: Removing manifest:
/home/ubuntu/yocto/build/tmp/sysroots/cubox-i/usr/lib/qt5/
DEBUG: Removing manifest:
/home/ubuntu/yocto/build/tmp/sysroots/cubox-i/usr/lib/
DEBUG: Removing manifest: /home/ubuntu/yocto/build/tmp/sysroots/cubox-i/usr/
DEBUG: Python function sysroot_cleansstate finished
DEBUG: Executing shell function qmake5_base_preconfigure
Previously configured separate build directory detected, cleaning
/home/ubuntu/yocto/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/pyotherside/1.2+gitAUTOINC+87e5eaf470-r0/build
DEBUG: Shell function qmake5_base_preconfigure finished
DEBUG: Executing shell function do_configure
Reading
/home/ubuntu/yocto/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/pyotherside/1.2+gitAUTOINC+87e5eaf470-r0/git/src/src.pro
[/home/ubuntu/yocto/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/pyotherside/1.2+gitAUTOINC+87e5eaf470-r0/build/src]
Project MESSAGE: PYTHON_CONFIG = python3-config
Reading
/home/ubuntu/yocto/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi
Re: [yocto] local.conf assignment priority with autobuilder
On 10/15/2014 02:45 PM, Jate Sujjavanich wrote: I am attempting to control debug-tweaks via an image recipe. Previous posts suggest that the autobuilder will use auto.conf and ignore local.conf. However, meta/conf/bitbake.conf says that the include order is auto.conf, and then local.conf. Correct, the autobuilder will use auto.conf to load it's modifications, but as you note in bitbake.conf, the local.conf will also be loaded after auto.conf. This means that the default local.conf.template installed overrides with a regular assignment. EXTRA_IMAGE_FEATURES = "debug-tweaks" Perhaps the assignment in local.conf be a weak one, i.e. ?= where it would not override a previous assignment. You can use EXTRA_IMAGE_FEATURES_remove = "debug-tweaks" which will remove it when it's finalized. If you want to add to EXTRA_IMAGE_FEATURES you can use += operation. Sau! Or maybe I need a new buildstep. How should I be doing this? - Jate S. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to get autotools to use C++11 under 'danny'
Does anybody know what I need to add to my configure.ac to get C++11 (or C++0x) support added to the gcc flags at compile time? I've tried using: AC_LANG([C++]) AC_PROG_CXX AX_CXX_COMPILE_STDCXX_11([noext]) But that fails at configure time. -- Chris Tapp opensou...@keylevel.com www.keylevel.com You can tell you're getting older when your car insurance gets real cheap! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Questions regarding adding a new llvm based cross-compiler
On Fri, Oct 17, 2014 at 09:07:19AM +0100, Paul Barker wrote: > On 16 October 2014 18:46, Cody P Schafer wrote: > > Hi all, > > > > I'm working on creating a layer for the rust compiler (which uses > > llvm) and was wondering if there were any best practices and/or > > examples people could point me at. Are you using llvm recipes from meta-oe (or at least starting from them)? > I can't really offer much help on the LLVM side, but I can say this > will be really useful work. I'm slowly learning Rust and researching > how it can be used for embedded development and it will be excellent > to have a rust compiler working as part of OpenEmbedded/Yocto. > > If you need any testing of this layer once it's created, just let me know. I'm also interested. I haven't tried it yet, but I've asked Servo developer, how they do cross-builds and he said that it's really simple with Rust and Cargo, which support cross-compilation by design. Now reading: http://doc.crates.io/faq.html#does-cargo-handle-multi-platform-projects-or-cross-compilation? it doesn't looks so convincing, but I would be happy to test. Regards, -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com signature.asc Description: Digital signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to get autotools to use C++11 under 'danny'
On Friday 17 of October 2014 17:47:29 Chris Tapp wrote:
> Does anybody know what I need to add to my configure.ac to get C++11 (or
> C++0x) support added to the gcc flags at compile time?
>
> I've tried using:
>
>AC_LANG([C++])
>AC_PROG_CXX
>AX_CXX_COMPILE_STDCXX_11([noext])
>
> But that fails at configure time.
Care for posting how exactly that fails?
Besides AX_CXX_COMPILE_STDCXX_11 is part of autoconf-archive. Adding autoconf-
archive to DEPENDS might help. You could also dump the macro directly into say
m4 dir in your source package and add EXTRA_AUTORECONF_append = "-I${S}/m4"
the recipe.
--
Maciej Borzęcki
Senior Software Engineer Open-RnD Sp. z o.o.
www.open-rnd.pl, Facebook, Twitter
mobile: +48 telefon, fax: +48 42 657 9079
Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub
poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do
których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo
zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku
uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie
nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy.
This message, including any attachments hereto, may contain privileged or
confidential information and is sent solely for the attention and use of the
intended addressee(s). If you are not an intended addressee, you may neither
use this message nor copy or deliver it to anyone. In such case, you should
immediately destroy this message and kindly notify the sender by reply email.
Thank you.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to get autotools to use C++11 under 'danny'
On 17 Oct 2014, at 20:17, Maciej Borzecki wrote:
> On Friday 17 of October 2014 17:47:29 Chris Tapp wrote:
>> Does anybody know what I need to add to my configure.ac to get C++11 (or
>> C++0x) support added to the gcc flags at compile time?
>>
>> I've tried using:
>>
>> AC_LANG([C++])
>> AC_PROG_CXX
>> AX_CXX_COMPILE_STDCXX_11([noext])
>>
>> But that fails at configure time.
> Care for posting how exactly that fails?
Ah - I meant to say "with a syntax error" !
> Besides AX_CXX_COMPILE_STDCXX_11 is part of autoconf-archive. Adding autoconf-
> archive to DEPENDS might help. You could also dump the macro directly into
> say
> m4 dir in your source package and add EXTRA_AUTORECONF_append = "-I${S}/m4"
> the recipe.
Thanks, I'll have a look at that. In the mean time I've added CFLAGS+="
-std=c++x0" to get me going.
>
> --
>
> Maciej Borzęcki
> Senior Software Engineer Open-RnD Sp. z o.o.
> www.open-rnd.pl, Facebook, Twitter
> mobile: +48 telefon, fax: +48 42 657 9079
>
> Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub
> poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do
> których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo
> zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim
> przypadku
> uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie
> nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy.
>
> This message, including any attachments hereto, may contain privileged or
> confidential information and is sent solely for the attention and use of the
> intended addressee(s). If you are not an intended addressee, you may neither
> use this message nor copy or deliver it to anyone. In such case, you should
> immediately destroy this message and kindly notify the sender by reply email.
> Thank you.
--
Chris Tapp
opensou...@keylevel.com
www.keylevel.com
You can tell you're getting older when your car insurance gets real cheap!
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] DEFAULT_PREFERENCE not working as expected
I've got a layer that includes a recipe for libsoup at version 2.40.3 which sets DEFAULT_PREFERENCE = "-1". However, this version gets used when I build rather than the 2.38.? version in poky/meta (under danny). Why is this? -- Chris Tapp opensou...@keylevel.com www.keylevel.com You can tell you're getting older when your car insurance gets real cheap! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] DEFAULT_PREFERENCE not working as expected
That's by (IMHO wrong) design: https://bugzilla.yoctoproject.org/show_bug.cgi?id=2964 Instead of setting P_V 2.40 only for that single project which needs that newer libsoup, you need to set P_V to 2.38 for every other project which is using your layer. On Fri, Oct 17, 2014 at 10:57 PM, Chris Tapp wrote: > I've got a layer that includes a recipe for libsoup at version 2.40.3 > which sets DEFAULT_PREFERENCE = "-1". > > However, this version gets used when I build rather than the 2.38.? > version in poky/meta (under danny). Why is this? > > -- > > Chris Tapp > opensou...@keylevel.com > www.keylevel.com > > > You can tell you're getting older when your car insurance gets real cheap! > > -- > ___ > 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] DEFAULT_PREFERENCE not working as expected
On 17 Oct 2014, at 22:37, Martin Jansa wrote: > That's by (IMHO wrong) design: > https://bugzilla.yoctoproject.org/show_bug.cgi?id=2964 Thanks - I was wondering if layers had something to do with it. > Instead of setting P_V 2.40 only for that single project which needs that > newer libsoup, you need to set P_V to 2.38 for every other project which is > using your layer. I can work with that - the layer is being used to up-rev various recipes for bug fixes (e.g. bash) and to add later versions of things like gstreamer. It would be nice if the default was "keep it as is" with DP set to -1, but I think I'll need to create a distro to get that behaviour. From the link it looks as if layer priority may also be important, so I'll have a play with that when the current build finishes... > On Fri, Oct 17, 2014 at 10:57 PM, Chris Tapp wrote: > I've got a layer that includes a recipe for libsoup at version 2.40.3 which > sets DEFAULT_PREFERENCE = "-1". > > However, this version gets used when I build rather than the 2.38.? version > in poky/meta (under danny). Why is this? > > -- > > Chris Tapp > opensou...@keylevel.com > www.keylevel.com > > > You can tell you're getting older when your car insurance gets real cheap! > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- Chris Tapp opensou...@keylevel.com www.keylevel.com You can tell you're getting older when your car insurance gets real cheap! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
