From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][[RFC][PATCH] nodejs: add 0.8.18
Date: Thu, 31 Jan 2013 22:03:59 +0100 [thread overview]
Message-ID: <keem7q$lsm$1@ger.gmane.org> (raw)
In-Reply-To: <20130131180051.GG2102@jama.dyndns-home.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 31-01-13 19:00, Martin Jansa schreef:
> On Thu, Jan 31, 2013 at 06:07:37PM +0100, Koen Kooi wrote:
>>
>> Op 31 jan. 2013, om 17:56 heeft Martin Jansa <martin.jansa@gmail.com>
>> het volgende geschreven:
>>
>>> On Wed, Jan 30, 2013 at 09:02:35AM +0100, Koen Kooi wrote:
>>>> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> ---
>>>> .../nodejs/nodejs/0002-Enable-NEON.patch | 27 ++++++++++
>>>> ...0003-Resolve-bad-rpath-issue-when-linking.patch | 29 ++++++++++
>>>> meta-oe/recipes-devtools/nodejs/nodejs_0.8.18.bb | 61
>>>> ++++++++++++++++++++++ 3 files changed, 117 insertions(+) create
>>>> mode 100644
>>>> meta-oe/recipes-devtools/nodejs/nodejs/0002-Enable-NEON.patch
>>>> create mode 100644
>>>> meta-oe/recipes-devtools/nodejs/nodejs/0003-Resolve-bad-rpath-issue-when-linking.patch
>>>>
>>>>
create mode 100644 meta-oe/recipes-devtools/nodejs/nodejs_0.8.18.bb
>>>
>>> FWIW: 0.6.21 fails exactly the same as 0.6.20 but I've merged it as
>>> it's not worse.
>>>
>>> I've tried 0.8.18 today and it fails: ERROR: Function failed:
>>> do_configure (see
>>> /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/nodejs-native/0.8.18-r0/temp/log.do_configure.30923
>>> for further information) ERROR: Logfile of failure stored in:
>>> /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/nodejs-native/0.8.18-r0/temp/log.do_configure.30923
>>>
>>>
Log data follows:
>>> | DEBUG: Executing python function sysroot_cleansstate | DEBUG:
>>> Python function sysroot_cleansstate finished | DEBUG: Executing shell
>>> function do_configure |
>>> /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/nodejs-native/0.8.18-r0/gcc:
>>> 2:
>>> /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/nodejs-native/0.8.18-r0/gcc:
>>> Cannot fork |
>>> /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/nodejs-native/0.8.18-r0/gcc:
>>> 2:
>>> /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/nodejs-native/0.8.18-r0/gcc:
>>> Cannot fork | Traceback (most recent call last): | File
>>> "./configure", line 473, in <module> | configure_node(output) |
>>> File "./configure", line 371, in configure_node | cc_version,
>>> is_clang = compiler_version() | File "./configure", line 331, in
>>> compiler_version | version = tuple(map(int,
>>> proc.communicate()[0].split('.'))) | ValueError: invalid literal for
>>> int() with base 10: '' | ERROR: Function failed: do_configure (see
>>> /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/nodejs-native/0.8.18-r0/temp/log.do_configure.30923
>>> for further information) NOTE: recipe nodejs-native-0.8.18-r0: task
>>> do_configure: Failed ERROR: Task 22884
>>> (virtual:native:/home/jenkins/oe/shr-core-branches/shr-core/meta-openembedded/meta-oe/recipes-devtools/nodejs/nodejs_0.8.18.bb,
>>> do_configure) failed with exit code '1'
>>>
>>> Any idea?
>>
>> That's likely the gcc wrapper script I added maybe it doesn't like your
>> native gcc. FWIW I only tested it on fedora 18
>
> Here it's on Ubuntu 12.04
>
> but wrapper is in $WORKDIR and PATH contains WORKDIR, so I guess that
> those wrappers are fork bombing poor jenkins.. (at least here because
> CC/CXX variables are just gcc/g++)
I've hear people report this issue before, but I've never managed to
reproduce or debug it :(
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFRCtw/MkyGM64RGpERAqXDAJ9m7dGMDMVuFg/XdYw+QGN3uzpaWQCePtbG
OoLxGkT94IuoEehKUqJG7Qs=
=ax5F
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-01-31 21:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 8:02 [meta-oe][[RFC][PATCH] nodejs: add 0.8.18 Koen Kooi
2013-01-30 8:45 ` Koen Kooi
2013-01-30 8:51 ` Eric Bénard
2013-01-30 9:03 ` Koen Kooi
2013-01-30 9:06 ` Marcin Juszkiewicz
2013-01-31 16:56 ` Martin Jansa
2013-01-31 17:07 ` Koen Kooi
2013-01-31 18:00 ` Martin Jansa
2013-01-31 21:03 ` Koen Kooi [this message]
2013-02-08 8:50 ` Kevin Baker
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='keem7q$lsm$1@ger.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.