<civodul>there are nice ideas on how to handle package variants from the command line <civodul>we should Do Something About It™ :-) ***flojistik is now known as Phlogistique
<rekado_>civodul: the package customisation on the command line looks noisy (because of %@=^+); I think a little more verbosity wouldn't be a bad thing. <civodul>rekado_: right, i'm not convinced by the syntax, but the idea sounds good <civodul>phant0mas: did you see the 3 Hurd-related releases? wooohooo! <civodul>remi`bd: did you have a chance to play with Guile's FFI and/or GNUnet? <remi`bd>yes, I spent a few hours taking notes on GnuNet API <phant0mas>civodul: yes civodul, will update the packages today :-D <remi`bd>I’ll “translate” parts of the GnuNet C tutorial to Guile <remi`bd>I’ve also quickly read the source of gnunet-find, gnunet-download and gnunet-publish <civodul>remi`bd: please do provide feedback on these things, like the FFI and stuff *civodul has to go afk for a while <rekado_>seems that in "guix enviroment --pure icedtea7" "awt_Font.o" isn't even built. <rekado_>and the build process just finishes without errors. <rekado_>I prepared the build with "guix build -K icedtea7" and replaced the build phase with (lambda _ #f); then chown'd the directory, run "guix environment --pure icedtea7", "source ../environment-variables", and then "make". <davexunit>are you reporting an irregularity with 'guix environment' or an issue with building icedtea7? <rekado_>I also noticed that when my system has "/usr/include/sys/sdt.h", "make" will fail as it's trying to build some dtrace stuff, which is not found when it actually gets to building. <rekado_>so ... it seems to me that the early stuff triggered by "make" performs some additional configuration, overriding or augmenting what has been configured with the configure script already. <rekado_>I really don't enjoy manually tracing recursive makefiles to understand what's going on. <civodul>rekado_: you should use "source environment-variables" in the failed build tree rather than 'guix environment' <civodul>(for instance because there can be env. vars not known to 'guix environment') <rekado_>first guix environment, then source environment-variables. <civodul>and you did try #:parallel-build? #f, right? <rekado_>it builds just fine in guix environment. <rekado_>but fails building awt_Font.o in guix build. <rekado_>it seems not to build awt_Font.o at all in guix environment. <civodul>could it be there are some remnants or /bin/sh or something in makefiles? <rekado_>this is odd, because I'm just resuming an installation in which "configure" was already run. <civodul>that would make some test succeed outside of the chroot, and fail inside <civodul>thus leading to that file being built inside the chroot and not outside? <rekado_>saved the complete build output from the successful build with guix environment. Will analyse this some time later. <rekado_>I want to know why awt_Font.o isn't compiled. <rekado_>hmm, I was wrong. It actually *is* built, it just doesn't fail. ***nully` is now known as nully
<rekado_>I see "/usr/" paths among the includes for the compilation of awt_Font.o. <rekado_>in icedtea6 we also have "-I/usr/include/X11/extensions" <civodul>could you ldd the resulting binaries to see if they end up using FHS libs? <civodul>the binaries from the successfully-compiled-out-of-chroot variant <rekado_>for libawt.so I see links to libraries in the build directory: libjava.so => /buildtmp/nix-build-icedtea7-2.5.5.drv-0/icedtea-2.5.5/./openjdk.build/j2re-image/lib/amd64/libjava.so <rekado_>but so far nothing from the host system. <rekado_>I'll recompile the thing with guix build, and then diff the complete build output with what was produced under guix environment. <civodul>rekado_: yeah, diffing the build logs might help <civodul>as a very last resort, you could "strace -f" the whole build, and then grep for FHS accesses <civodul>"strace -f -e open" would be less unreasonable... ***ielectric1 is now known as iElectric
***jaerf is now known as freaj
<Sleep_Walker>I have package with static binaries only (not static-package though) and I'd like it to require no dependencies <bavier>Sleep_Walker: do you mean no inputs? <Sleep_Walker>I mean I'd like installation of my package not to trigger installation of any other package <bavier>Sleep_Walker: that should be possible, with trivial-build-system <bavier>and using the bootstrap guile to copy files into the package output <Sleep_Walker>but it still triggers installation of lvm2 and it's dependencies <bavier>yeah, because lvm2 is a native inputs <bavier>what does `guix gc --references` say? <civodul>(personally i would take care of that last) <civodul>i would rather do a separate package, like for e2fs <bavier>civodul: thanks for the "spack" link, very interesting <civodul>Sleep_Walker: does ldd or similar confirm it's static? <civodul>including something like 'refresh' and 'import' which seems quite powerful <civodul>did you try "guix gc --references $(guix build lvm2-static-whatev)"? <civodul>if that shows a non-empty list, then "grep" and "strings" are your friends ;-) <civodul>even better: use #:allow-references '() <Sleep_Walker>allowed-references doesn't seem to be defined for trivial-build-system