On 08/03/2013 03:28 PM, Saul Wold wrote:
On 08/02/2013 12:27 AM, Khem Raj wrote:

On Aug 1, 2013, at 9:53 PM, Saul Wold <[email protected]> wrote:

On 08/01/2013 01:19 PM, Khem Raj wrote:

On Jul 31, 2013, at 4:05 PM, Saul Wold <[email protected]> wrote:

On 07/31/2013 03:51 PM, Khem Raj wrote:

On Jul 31, 2013, at 3:49 PM, Saul Wold <[email protected]> wrote:


Still seems to failing in Jinja, I wonder if the dependencies are
correctly sinec it's nooking for native bits and the
python3-native had not been installed yet.



in my build from scratch several times, I never had this issue.
Did you do an incremental build to get to this issue ?


Yes, most of my builds are incremental until I throw them against
the Autobuilder!

Saul,

I was able to reproduce the incremental build issue. I have now
fixed it and pushed a rebased branch to pull tree
in contrib. Please try it out


Almost there!  It looks like you have a ${PN} in the tarball name
instead of ${BPN} and it's causing a multilib failure for zeromq.

Yes. Pushed a fix on top of the branch plus another fix that I ran
into was missing dependency on virtual/libntl


OK, Ran it on the Autobuilder last night, and came up with the following
on a World build with multilib enabled:

ERROR: This autoconf log indicates errors, it looked at host include
and/or library paths while determining system capabilities.
Rerun configure task after fixing this. The path was
'/srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-world/build/build/tmp/work/x86-pokymllib32-linux/lib32-python3/3.3.2-r0.0/Python-3.3.2'

ERROR: Function failed: do_qa_configure
ERROR: Logfile of failure stored in:
/srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-world/build/build/tmp/work/x86-pokymllib32-linux/lib32-python3/3.3.2-r0.0/temp/log.do_configure.13443

NOTE: recipe lib32-python3-3.3.2-r0.0: task do_configure: Failed
ERROR: Task 11368
(virtual:multilib:lib32:/srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-world/build/meta/recipes-devtools/python/python3_3.3.2.bb,
do_configure) failed with exit code '1'
NOTE: Running task 10412 of 21582 (ID: 12424,
virtual:multilib:lib32:/srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-world/build/meta/recipes-connectivity/bluez/bluez-hcidump_2.5.bb,
do_packagedata)
NOTE: recipe lib32-quota-4.01-r1: task do_compile: Started
ERROR: This autoconf log indicates errors, it looked at host include
and/or library paths while determining system capabilities.
Rerun configure task after fixing this. The path was
'/srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-world/build/build/tmp/work/i586-poky-linux/python3/3.3.2-r0.0/Python-3.3.2'

ERROR: Function failed: do_qa_configure
ERROR: Logfile of failure stored in:
/srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-world/build/build/tmp/work/i586-poky-linux/python3/3.3.2-r0.0/temp/log.do_configure.15796

NOTE: recipe python3-3.3.2-r0.0: task do_configure: Failed
ERROR: Task 80
(/srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-world/build/meta/recipes-devtools/python/python3_3.3.2.bb,
do_configure) failed with exit code '1'

Summary of local.conf changes:
DISTRO = "poky"
PACKAGE_CLASSES = "package_rpm package_deb package_ipk"
BB_NUMBER_THREADS = "16"
PARALLEL_MAKE = "-j 16"
SDKMACHINE ?= "x86_64"
DL_DIR = "/srv/www/vhosts/autobuilder.yoctoproject.org/current_sources"
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
SSTATE_DIR ?= "/srv/www/vhosts/sstate.yoctoproject.org//multilib"
MACHINE = "qemux86"
PREMIRRORS = ""
BB_GENERATE_MIRROR_TARBALLS = "1"
ADTREPO = "http://adtrepo.yoctoproject.org//1.4+snapshot";



Khem:

This are kind of killing my enthusiasm with python3

Another issue in jinja:

RefactoringTool: There was 1 error:
RefactoringTool: Can't parse ./ez_setup.py: ParseError: bad input: type=22, 
value='=', context=('', (54, 19))
--- ./jinja/translators/python.py       (original)
+++ ./jinja/translators/python.py       (refactored)

Sau!


Sau!




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


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

Reply via email to