Source: libv8
Version: 3.5.10.24-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
The latest libv8 upload fails to build on i386:
../src/ia32/lithium-codegen-ia32.cc:3178:12: error: variable 'key' set but
not used
Package: libv8
Version: 3.5.10.24-1
Severity: serious
Justification: fails to build from source
Builds of libv8 on mipsel are now failing due to what appears to be a
gap in upstream's build system:
/usr/bin/make -C . CFLAGS=-g -O2 -Wformat -Wformat-security
-Werror=format-security -Wall
Package: libv8
Version: 3.5.10.24-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Builds of libv8 on armel are now failing because its build system
insists for some reason on passing the unsupported -m32 flag:
make[2]: Entering directory
to libv8) has ARM-specific changes.
AFAICT, the build attempts occurred just a couple of weeks ago, using an
sbuild version from February.
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Package: node-bones
Version: 2.0.1+ds1-1
Severity: grave
Justification: renders package unusable (uninstallable)
As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated node
package. To accommodate that change, please
Package: node-express
Version: 2.5.9-1
Severity: grave
Justification: renders package unusable (uninstallable)
As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated node
package. To accommodate that change, please
Package: node-jake
Version: 0.2.32-1
Severity: grave
Justification: renders package unusable (uninstallable)
As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated node
package. To accommodate that change, please
Package: node-optimist
Version: 0.3.1-1
Severity: grave
Justification: renders package unusable (uninstallable)
As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated node
package. To accommodate that change, please
Package: node-vows
Version: 0.6.3-1
Severity: grave
Justification: renders package unusable (uninstallable)
As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated node
package. To accommodate that change, please
Package: npm
Version: 1.1.4~dfsg-1
Severity: grave
Justification: renders package unusable
As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated node
package. To accommodate that change, please update the
Package: buddycloud-server
Version: 0.3.1-1
Severity: grave
Justification: renders package unusable (uninstallable)
As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated node
package. To accommodate that change,
Package: carto
Version: 0.4.6+ds1-1
Severity: grave
Justification: renders package unusable (uninstallable)
As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated node
package. To accommodate that change, please
Package: node-tilelive
Version: 4.2.1-3
Severity: grave
Justification: renders package unusable (uninstallable)
As you may have heard, nodejs's main executable is now /usr/bin/nodejs
rather than /usr/bin/node to avoid clashing with the unrelated node
package. To accommodate that change, please
Source: libuv
Version: 0.10.8-0~exp2
Severity: important
Justification: fails to build from source
Builds of libuv on kFreeBSD and the Hurd have been failing:
In file included from /.../libuv-0.10.8/include/uv.h:67:0,
from src/unix/async.c:25:
Source: libuv1
Version: 1.4.2-1
Severity: serious
Justification: fails to build from source
The automated builds of libuv1 all failed with test suite errors.
For some reason, pipe_set_non_blocking failed everywhere:
`pipe_set_non_blocking` failed: exit code 6
Output from process
if at all possible. However, I see that the
latest packaged version is pretty old -- 3.14.5.8 vs. nodejs's
embedded 5.1.281.
Thanks!
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--
Pkg
: error: 'NativeHandle' does not
name a type
NativeHandle& native_handle() {
Could you please take a look and ensure that the build system
recognizes both OSes as POSIX-compliant?
Thanks!
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ |
to `uv__platform_invalidate_fd'
/usr/lib/i386-gnu/libuv.so: undefined reference to `uv__io_poll'
/usr/lib/i386-gnu/libuv.so: undefined reference to `uv__platform_loop_init'
/usr/lib/i386-gnu/libuv.so: undefined reference to `uv__fs_event_close'
Could you please take a look?
Thanks!
--
Aaron M. Ucko
18 matches
Mail list logo
