vmkit: FTBFS: make[1]: *** No rule to make target `Makefile.common'. Stop.

[Andreas Moog]

Imported from Debian bug http://bugs.debian.org/724104:

Source: vmkit
Version: 0.32~r185341-1
Severity: serious
Tags: jessie sid
User: <email address hidden>
Usertags: qa-ftbfs-20130922 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with autotools-dev
> dh_testdir
> dh_auto_clean
> make -j1 distclean
> make[1]: Entering directory `/«PKGBUILDDIR»'
> Makefile:14: Makefile.common: No such file or directory
> make[1]: *** No rule to make target `Makefile.common'. Stop.
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> dh_auto_clean: make -j1 distclean returned exit code 2
> make: *** [clean] Error 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/09/22/vmkit_0.32~r185341-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

[Andreas Moog (ampelbein)]

 subscribe
Hi there,

while this particular bug is relatively easy to fix by adding

override_dh_auto_clean:
 [ ! -f Makefile.common ] || dh_auto_clean

to debian/rules, the build will fail further on with a core dump:

vmjc: JavaClass.cpp:496: j3::JavaObject *j3::Class::doNew(j3::Jnjvm *):
Assertion `(this->isInitializing() ||
classLoader->getCompiler()->isStaticCompiling() || this ==
classLoader->bootstrapLoader->upcalls->newClass) && "Uninitialized class
when allocating."' failed.
0 vmjc 0x0000000000ea72b2
llvm::sys::PrintStackTrace(_IO_FILE*) + 34
1 vmjc 0x0000000000ea7119
2 libpthread.so.0 0x00002b450d729bb0
3 libc.so.6 0x00002b450e7b0f77 gsignal + 55
4 libc.so.6 0x00002b450e7b45e8 abort + 328
5 libc.so.6 0x00002b450e7a9d43
6 libc.so.6 0x00002b450e7a9df2
7 vmjc 0x000000000059f2a0 j3::Class::doNew(j3::Jnjvm*) + 144
8 vmjc 0x00000000005c6abf
j3::Jnjvm::CreateNullPointerException() + 79
9 vmjc 0x00002b45135149e6
j3::Jnjvm::CreateNullPointerException() + 318037878
Aborted (core dumped)
make[4]: ***
[/mnt/devel/andreas/temp/vmkit-0.32~r185341/mmtk/java/Release+Asserts/mmtk-vmkit-lower.bc]
Error 134

Upstream seems to be aware of the issue, saying the build only works
with "a version strictly before the 7u25 (probably the
7u21), sorry!", see
http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-November/068087.html

Cheers,
  Andreas

--
Andreas Moog, Berliner Str. 29, 36205 Sontra/Germany
PGP-encrypted mails preferred (Key-ID: 74DE6624)
PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624

[Sylvestre Ledru (sylvestre)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 29/11/2013 15:20, Andreas Moog wrote:
> subscribe
> Hi there,
>
> while this particular bug is relatively easy to fix by adding
>
> override_dh_auto_clean:
> [ ! -f Makefile.common ] || dh_auto_clean
>
> to debian/rules, the build will fail further on with a core dump:
Yep, it is why I haven't fixed yet ...
>
>
> Upstream seems to be aware of the issue, saying the build only works
> with "a version strictly before the 7u25 (probably the
> 7u21), sorry!", see
> http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-November/068087.html
>
Yep, I am aware of that ... (upstream is a friend).
He is currently refactoring some large part of vmkit to tackle this issue.

Sylvestre

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iEYEARECAAYFAlKYpCAACgkQiOXXM92JlhBPCACg8GQ37Sk4d0y0HUsQ+kjPgdz/
wvsAnikEqWbMFLqB0aVr+HmmgonqqHZA
=EdqU
-----END PGP SIGNATURE-----

[Ross Gammon (rosco2)]

The Debian bug has been acknowledged upstream and is being worked on.

[Andreas Moog (ampelbein)]

Package has been removed from Ubuntu.