image build fails during npm install (Bug #129)


Added by Dan Lipsitt almost 3 years ago. Updated over 2 years ago.


Status:In Progress Start date:12/22/2014
Priority:Normal Due date:
Assignee:Robert Nelson % Done:

0%

Category:-
Target version:-

Description

beagleboard.org_image.sh fails in chroot during npm install.
Build host is x86_64 running Ubuntu 14.04.1 (Trusty).

$ git describe
bb.org-v2014.12.11-8-g47cc9df
Installing npm packages
debug: node: [v0.10.29]

/usr/share/npm/node_modules/npmconf/config-defs.js:322
  Object.keys(os.networkInterfaces()).map(function (nic) {
                 ^
Error: EAFNOSUPPORT, address family not supported
    at getLocalAddresses (/usr/share/npm/node_modules/npmconf/config-defs.js:322:18)
    at Object.<anonymous> (/usr/share/npm/node_modules/npmconf/config-defs.js:269:23)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/usr/share/npm/node_modules/npmconf/npmconf.js:4:18)
    at Module._compile (module.js:456:26)
debug: npm: []

/usr/share/npm/node_modules/npmconf/config-defs.js:322
  Object.keys(os.networkInterfaces()).map(function (nic) {
                 ^
Error: EAFNOSUPPORT, address family not supported
    at getLocalAddresses (/usr/share/npm/node_modules/npmconf/config-defs.js:322:18)
    at Object.<anonymous> (/usr/share/npm/node_modules/npmconf/config-defs.js:269:23)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/usr/share/npm/node_modules/npmconf/npmconf.js:4:18)
    at Module._compile (module.js:456:26)

History

Updated by Bill Traynor almost 3 years ago

  • Assignee set to Robert Nelson

Updated by Robert Nelson almost 3 years ago

Sadly, qemu is just not reliable enough to run this script on x86.

Pickup up any beefy armv7-a system, Dual Core+ / 512Mb+ / sata (or usb-sata), running Ubuntu or Debian.

The usual failure point for qemu is: [git clone]

Regards,

  • Status changed from New to In Progress

Updated by Dan Lipsitt almost 3 years ago

I was able to complete a successful run of

./RootStock-NG.sh -c bb.org-console-debian-stable

I have not tried to boot a machine from it yet. Have you seen problems even if the build completes, or would you expect this image to work?

Updated by Robert Nelson almost 3 years ago

Hi Dan,

The "bb.org-console-debian-stable" generates the raw root file system used to generate these "console" images:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-12-19

It also doesn't include git or nodejs/npm so where it last got stuck get's completely bypassed..

It takes a little decoding, but the final stage to generate the *.img file is here:

https://github.com/beagleboard/image-builder/blob/master/publish/rcn-ee_bb.org-stable.sh#L81

sudo setup_sdcard.sh [options below]

Generate 2gb img with specific name:
--img-2gb bone-\${base_rootfs}

Target Beaglebone family (bbb/bbw)
--dtb beaglebone

Boot Partition has "BEAGLEBONE" label
--boot_label BEAGLEBONE

Force systemd (In wheezy we need to overide init to force systemd)
--enable-systemd

Support old versions in u-boot prior to August 2014: (this includes anything newer then Angstrom's July 2013)
--bbb-old-bootloader-in-emmc" 

Regards,

Updated by Dan Lipsitt over 2 years ago

I haven't had this problem with the console builds. OK to close.

Also available in: Atom PDF