Closed mmokrejs closed 8 years ago
this is strange because the current head is using
the following hash: 8dd4559dced3a243dde094415a9974c03aceb3e3
and not what I'm seeing in you trace: 9999 . How did you clone that project ?
furthermore, 'make all' works in travis: https://travis-ci.org/lindenb/jvarkit#L8149
Anyway, the Makefile rules is missing, I think that is what the message says.
I don't see any rule missing.
make -nB all
produces no error.
furthermore, I suspect you're using a non-GNU version of make
(...)
* emake failed
And you can always restructure the makefile so that there are always these separate targets 'fetch', 'compile', 'install', 'all'
this is not my current interest, but feel free to submit a PR.
So what does the 'No rule to make target' mean?
I know it's not your final aim, but I would suggest you use a standard version of make, not your wrapper, and test if you get the very same message. If not, then I would say that it comes from your wrapper emake.
OK, I re-tried with calling make directly. I also forced one thread ... I got a different error.
/var/tmp/portage/sci-biology/jvarkit-9999/work/jvarkit-9999/src/main/java/com/github/lindenb/jvarkit/tools/misc/VcfToHilbert.java:162: error: unmappable character
for encoding ASCII
// Make A-shaped (really "???" shaped) curve at this scale:
^
Ah, I agree that one. There is an unicode character in my java file that was not detected by my tools.
file ./main/java/com/github/lindenb/jvarkit/tools/misc/VcfToHilbert.java
./main/java/com/github/lindenb/jvarkit/tools/misc/VcfToHilbert.java: UTF-8 Unicode C program text
it looks like, it's the only file with this problem:
$ find -type f -exec file '{}' ';' | grep Unicode
./main/java/com/github/lindenb/jvarkit/tools/misc/VcfToHilbert.java: UTF-8 Unicode C program text
fixed in https://github.com/lindenb/jvarkit/commit/c072292e4023b7943c99594616496f49241d0031
$ file ./main/java/com/github/lindenb/jvarkit/tools/misc/VcfToHilbert.java./main/java/com/github/lindenb/jvarkit/tools/misc/VcfToHilbert.java: ASCII C program text
thanks
fixed (via email)
Hi, it seems the Makefile does not ensure that a make exits upon error so nobody realized this so far? Below is a current HEAD checkout: