<vagrantc>hrm. mescc-tools 1.0.1 fails to build on debian ... some issue with the install target? <vagrantc>cp bin/M1 bin/hex2 bin/blood-elf kaem bin/get_machine /<<PKGBUILDDIR>>/debian/mescc-tools/usr/bin <vagrantc>cp: -r not specified; omitting directory 'kaem' *vagrantc tries a quick patch <vagrantc>seems kaem switch to a directory between 0.7.0 and 1.0.1 ... which might be confusing the make <vagrantc>i've worked around it in the debian packaging for now by not "make install" ... but i wonder how that even worked for anyone. <vagrantc>oh, i see that this was fixed upstream by renaming the "kaem" directory to "Kaem" ... heh. <vagrantc>along with a bunch of other commits regarding guix... <vagrantc>could also move everything into "src" or something like that... <gf>rekado, I noticed an error while following classpath-devel <gf>The command passes to configure --with-javac= returns <gf>configure: WARNING: unrecognized options: --with-javac <gf>is this supposed to be JAVAC= <rekado_>in Guix it doesn’t matter because the only javac we have at this point is the bootstrap javac <rekado_>but on a system that builds packages without file system virtualization this could be a problem <gf>OK, nevermind then. and thanks for the other day, got the wrapper script running <rekado_>on what OS are you trying to reproduce this bootstrap path? <gf>This work is for Slackware-current (prob, future 15) ***ChanServ sets mode: +o rekado_
***rekado_ is now known as rekado
<stikonas>gf: you can take a look at my gentoo java bootstrap path too ***reepca` is now known as reepca