nodejs fails to build on arm64 due to libv8 dependency
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nodejs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Attempting to build the nodejs package from source on Trusty and Vivid fails due to missing the dependency on libv8-3.14-dev.
lsb_release -a:
Distributor ID: Ubuntu
Description: Ubuntu 14.04.2 LTS
Release: 14.04
Codename: trusty
uname -a:
Linux tael 3.13.0-46-generic #77-Ubuntu SMP Mon Mar 2 18:27:27 UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
Build log:
dget --allow-
dget: retrieving https:/
dget: retrieving https:/
dget: retrieving https:/
dpkg-source: info: extracting nodejs in nodejs-
dpkg-source: info: unpacking nodejs_
dpkg-source: info: unpacking nodejs_
dpkg-source: info: applying 2001_FHS_
dpkg-source: info: applying 2004_relax_
dpkg-source: info: applying 2005_expected_
dpkg-source: info: applying 2010_fix_
dpkg-source: info: applying 2011_mipsel.patch
dpkg-source: info: applying 2012_kfreebsd.patch
dpkg-source: info: applying 2013_gyp_
dpkg-source: info: applying 1001_readfile_
dpkg-source: info: applying 1002_increase_
dpkg-source: info: applying 1003_test_
dpkg-source: info: applying 1004_test_
dpkg-source: info: applying 1005_restore_
dpkg-source: info: applying 2014_powerpc_
dpkg-source: info: applying 2015_ppc64el_
dpkg-buildpackage: source package nodejs
dpkg-buildpackage: source version 0.10.25~
dpkg-buildpackage: source distribution trusty
dpkg-buildpackage: source changed by Adam Conrad <email address hidden>
dpkg-buildpackage: host architecture arm64
dpkg-source --before-build nodejs-
dpkg-checkbuild
dpkg-buildpackage: warning: build dependencies/
dpkg-buildpackage: warning: (Use -d flag to override.)
The libv8 package currently fails to build on arm64, and bug filed against itl: https:/
tags: | added: ftbfs |
tags: | removed: block-proposed |
Changed in nodejs (Ubuntu): | |
status: | Fix Committed → Fix Released |
Adding a block-proposed tag to this to keep 4.0.0 in -proposed until it gets some testing. 4.0.0 should fix this bug, however.