nodejs 0.10.12 and Angstrom issues

467 views
Skip to first unread message

Erwin Schaefer

unread,
Jun 24, 2013, 10:03:55 AM6/24/13
to nod...@googlegroups.com
Hello,

I'm using https://github.com/Angstrom-distribution/setup-scripts to build a rootfs containing node.js for a "beaglebone" device.
So far, I could successfully build nodejs 0.10.x on branch "angstrom-v2012.05-yocto1.2" by adding a recipe inspired from nodejs_0.8.18.bb. (However, I had issues building on branch "master"; see this thread: https://groups.google.com/forum/#!searchin/nodejs/yocto1.3/nodejs/D6Xzd4OHV-o/ZJMfJcLLLvMJ)

Now, I can no longer build nodejs 0.10.12 on branch "angstrom-v2012.05-yocto1.2" (and also master, for that matter)
The error I get is:

ERROR: Function failed: do_compile (see /data/oe_old/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/armv7a-angstrom-linux-gnueabi/nodejs-0.10.12-r0/temp/log.do_compile.6138 for further information)
ERROR: Logfile of failure stored in: /data/oe_old/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/armv7a-angstrom-linux-gnueabi/nodejs-0.10.12-r0/temp/log.do_compile.6138
Log data follows:
| ERROR: Function failed: do_compile (see /data/oe_old/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/armv7a-angstrom-linux-gnueabi/nodejs-0.10.12-r0/temp/log.do_compile.6138 for further information)
| make -C out BUILDTYPE=Release V=1
| make[1]: Entering directory `/data/oe_old/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/armv7a-angstrom-linux-gnueabi/nodejs-0.10.12-r0/node-v0.10.12/out'
|   arm-angstrom-linux-gnueabi-gcc  -march=armv7-a -fno-tree-vectorize     -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 --sysroot=/data/oe_old/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/beaglebone '-D_DARWIN_USE_64_BIT_INODE=1' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-D_GNU_SOURCE' '-DHAVE_CONFIG_H' '-DCARES_STATICLIB' -I../deps/cares/include -I../deps/cares/src -I../deps/cares/config/linux  -Wall -Wextra -Wno-unused-parameter -pthread -m64 -g --std=gnu89 -pedantic -Wall -Wextra -Wno-unused-parameter -O2 -fno-strict-aliasing -fno-tree-vrp  -MMD -MF /data/oe_old/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/armv7a-angstrom-linux-gnueabi/nodejs-0.10.12-r0/node-v0.10.12/out/Release/.deps//data/oe_old/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/armv7a-angstrom-linux-gnueabi/nodejs-0.10.12-r0/node-v0.10.12/out/Release/obj.target/cares/deps/cares/src/ares_cancel.o.d.raw -O2 -pipe -g -feliminate-unused-debug-types -c -o /data/oe_old/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/armv7a-angstrom-linux-gnueabi/nodejs-0.10.12-r0/node-v0.10.12/out/Release/obj.target/cares/deps/cares/src/ares_cancel.o ../deps/cares/src/ares_cancel.c
| cc1: error: unrecognized command line option "-m64"
| make[1]: *** [/data/oe_old/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/armv7a-angstrom-linux-gnueabi/nodejs-0.10.12-r0/node-v0.10.12/out/Release/obj.target/cares/deps/cares/src/ares_cancel.o] Error 1
| make[1]: Leaving directory `/data/oe_old/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/armv7a-angstrom-linux-gnueabi/nodejs-0.10.12-r0/node-v0.10.12/out'
| make: *** [node] Error 2
NOTE: package nodejs-0.10.12-r0: task do_compile: Failed

Is it due to the change in host_arch_cc()?
Thank you very much for your insights.

Best regards,

Erwin Schaefer

Ben Noordhuis

unread,
Jun 24, 2013, 11:30:39 AM6/24/13
to nod...@googlegroups.com
You mean [1]?

It's possible. What happens when you revert the commit?

[1] https://github.com/joyent/node/commit/acbdabb

Erwin Schaefer

unread,
Jun 24, 2013, 1:40:10 PM6/24/13
to nod...@googlegroups.com
Hello,

If I revert the commit on the "configure" file, nodejs builds fine under branch "angstrom-v2012.05-yocto1.2".

Best regards,

Erwin





--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

---
You received this message because you are subscribed to a topic in the Google Groups "nodejs" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/nodejs/k8HzqpqPkJQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to nodejs+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



Ben Noordhuis

unread,
Jun 24, 2013, 2:21:21 PM6/24/13
to nod...@googlegroups.com
On Mon, Jun 24, 2013 at 7:40 PM, Erwin Schaefer
<mamahuhu...@gmail.com> wrote:
> Hello,
>
> If I revert the commit on the "configure" file, nodejs builds fine under
> branch "angstrom-v2012.05-yocto1.2".
>
> Best regards,
>
> Erwin

Do you have a CC environment variable set? What does `echo $CC` or
`set | grep -w CC` print?

I don't mind reverting commit acbdabb but it looks innocuous. An
environmental issue seems more likely.

Erwin Schaefer

unread,
Jun 25, 2013, 4:28:02 AM6/25/13
to nod...@googlegroups.com
Hello,

CC environment variable is not set.

Best regards,

Erwin


Ben Noordhuis

unread,
Jun 25, 2013, 6:51:36 AM6/25/13
to nod...@googlegroups.com
On Tue, Jun 25, 2013 at 10:28 AM, Erwin Schaefer
<mamahuhu...@gmail.com> wrote:
> Hello,
>
> CC environment variable is not set.
>
> Best regards,
>
> Erwin

Okay, noted. Reverted in a0b6df0.
Reply all
Reply to author
Forward
0 new messages