From: Khem Raj <raj.khem@gmail.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/24] Add python3 recipes
Date: Mon, 5 Aug 2013 22:29:28 -0700 [thread overview]
Message-ID: <C4934DB9-23CC-4B7D-AC40-CCEB59D08039@gmail.com> (raw)
In-Reply-To: <51FF33AE.20302@linux.intel.com>
>>>
>> 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"
>>
This is not reproducible on my end on multiple attempts. Built from scratch incremental anything
works ok python branch is on top of
commit bc6258f88705b0e7989089a8666ac5e5d2355823
Author: Saul Wold <sgw@linux.intel.com>
Date: Thu Aug 1 18:30:59 2013 -0700
grep: Add patch for texinfo 5.1
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Build Configuration:
BB_VERSION = "1.19.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-12.04"
TARGET_SYS = "x86_64-oe-linux"
MACHINE = "qemux86-64"
DISTRO_VERSION = "oe-core.0"
TUNE_FEATURES = "m64"
TARGET_FPU = ""
meta-nslu2 = "master:392b7799314a49b00f20a1bef004f9b0a0c9c364"
meta = "master:f902781f1cc6a7007060dfad3e3596688866ef87"
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 917 tasks of which 834 didn't need to be rerun and all succeeded.
next prev parent reply other threads:[~2013-08-06 5:29 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 21:59 [PATCH 00/24] Add python3 recipes Khem Raj
2013-06-28 22:03 ` [PATCH 01/24] generate-manifest-3.3.py: Add script to generate python 3.3 manifests Khem Raj
2013-06-28 22:03 ` [PATCH 02/24] python3native.bbclass: Add python3 abstraction class Khem Raj
2013-06-28 22:03 ` [PATCH 03/24] package_rpm.bbclass:Make the regexp less greedy Khem Raj
2013-06-28 22:03 ` [PATCH 04/24] classes/distutils: Introduce PYTHON_PN Khem Raj
2013-06-29 5:29 ` Martin Jansa
2013-06-29 14:07 ` Khem Raj
2013-06-28 22:03 ` [PATCH 05/24] classes: Add distutils for python3 Khem Raj
2013-06-28 22:03 ` [PATCH 06/24] setuptools.bbclass: Use python-distribute instead of python-setuptools Khem Raj
2013-06-28 22:03 ` [PATCH 07/24] distutils3.bbclass: Port the distutils class fix to handle filenames with spaces Khem Raj
2013-06-28 22:03 ` [PATCH 08/24] setuptools3.bbclass: Remove useless multiline comment Khem Raj
2013-06-28 22:03 ` [PATCH 09/24] distutils: Introduce PYTHON_ABI variable Khem Raj
2013-06-28 22:03 ` [PATCH 10/24] distutils3: Do build_ext as separate step during compile Khem Raj
2013-06-28 22:03 ` [PATCH 11/24] python-3.3-manifest: Add python3 manifest file Khem Raj
2013-06-28 22:03 ` [PATCH 12/24] python3: Add recipes Khem Raj
2013-08-26 13:32 ` Martin Jansa
2013-08-26 17:38 ` Khem Raj
2013-08-27 5:23 ` Khem Raj
2013-08-27 7:45 ` Martin Jansa
2013-08-27 7:48 ` Martin Jansa
2013-08-27 18:10 ` Khem Raj
2013-08-27 18:15 ` Martin Jansa
2013-08-28 6:23 ` Khem Raj
2013-06-28 22:03 ` [PATCH 13/24] python3: Add native recipe Khem Raj
2013-06-28 22:03 ` [PATCH 14/24] python_2.7.3.bb: Inherit python-dir Khem Raj
2013-06-28 22:04 ` [PATCH 15/24] ipython: Add recipes for ipython2 and ipython3 Khem Raj
2013-06-28 22:04 ` [PATCH 16/24] python-distribute: Add recipes for python2 and python3 Khem Raj
2013-07-08 10:49 ` Martin Jansa
2013-06-28 22:04 ` [PATCH 17/24] zeromq: Add recipe Khem Raj
2013-06-28 22:04 ` [PATCH 18/24] pyzmq: Add recipes using python3 Khem Raj
2013-06-28 22:04 ` [PATCH 19/24] python3-pycurl: Add recipe Khem Raj
2013-07-08 10:44 ` Martin Jansa
2013-06-28 22:04 ` [PATCH 20/24] python3-docutils: " Khem Raj
2013-06-28 22:04 ` [PATCH 21/24] python3-jinja: Recipe for python3 templating system Khem Raj
2013-06-30 10:30 ` Martin Jansa
2013-06-28 22:04 ` [PATCH 22/24] python3-nose: Testing tools for python Khem Raj
2013-06-28 22:04 ` [PATCH 23/24] python3-sphinx: New recipe for documentation system Khem Raj
2013-06-28 22:04 ` [PATCH 24/24] python3: Upgrade to 3.3.2 Khem Raj
2013-07-08 10:37 ` Paul Eggleton
2013-06-29 5:38 ` [PATCH 00/24] Add python3 recipes Martin Jansa
2013-06-29 14:11 ` Khem Raj
2013-06-29 15:31 ` Martin Jansa
2013-06-29 17:43 ` Khem Raj
2013-07-30 8:16 ` Khem Raj
2013-07-30 16:45 ` Saul Wold
2013-07-30 18:28 ` Khem Raj
2013-07-31 20:40 ` Saul Wold
2013-07-31 20:59 ` Khem Raj
2013-07-31 22:31 ` Khem Raj
2013-07-31 22:49 ` Saul Wold
2013-07-31 22:51 ` Khem Raj
2013-07-31 23:05 ` Saul Wold
2013-08-01 4:32 ` Khem Raj
2013-08-01 14:47 ` Khem Raj
2013-08-01 20:19 ` Khem Raj
2013-08-02 4:53 ` Saul Wold
2013-08-02 7:27 ` Khem Raj
2013-08-03 22:28 ` Saul Wold
2013-08-05 5:10 ` Saul Wold
2013-08-05 17:50 ` Khem Raj
2013-08-06 5:29 ` Khem Raj [this message]
2013-08-07 4:57 ` Khem Raj
2013-07-08 10:37 ` Paul Eggleton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C4934DB9-23CC-4B7D-AC40-CCEB59D08039@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox