IRC channel logs
2014-09-10.log
back to list of logs
<tadni_>safinaskar: It should be. Don't have a dedicated Guix/GNU box anymore though... so can't check if that's actually the case. <safinaskar>gnu has no /lib!!!!! nor /lib32, nor /lib64. it doesn't have even symlink /lib <safinaskar>so, you don't have /lib/ld-linux.so etc, so you completely breaked binary compatibility <safinaskar>so, i no way can run "normal binary" from debian on guix/gnu <Ulrar>safinaskar: Did you actually read what guix is about ? <safinaskar>why there is no /lib (even with symlinks to /gnu)? <drewc>sure you can! first make a chroot of the 'normal' distro in which you want a 'normal' binary to dynamically link, and chroot the binary! done. :) <safinaskar>drewc: i already copied tar archive of debian chroot to guix/gnu <safinaskar>drewc: but i cannot untar it, because guix/gnu doesn't have tar :) <safinaskar>but i cannot run it, because gnu/guix doesn't have /lib <Ulrar>It does, it's just not a big /lib with everything in it <drewc>why do you want to run a debian binary tar under gnu/guix at all when the entire point of guix is a package management scheme? <Ulrar>safinaskar: I think you missed the point of guix <jxself>Perhaps it would help if you read up about what the package manager is all about. :) <safinaskar>drewc: because "guix pull" already started and doesn't finished yet. (i think that i cannot run two "guix" at the same time) *tadni_ wonders when Ludo's talk is getting posted. <Ulrar>tadni_: He did a talk about it ? <jxself>Binary compatibility was deemed unimportant since free programs can simply be recompiled and then magically work. So the only "loss" is proprietary programs where that's not possible and I'm not sure that's much of a loss. :) <tadni_>Ulrar: He's done like 2 prior. The latest one is the 3rd or so at this yeart GHM. <safinaskar>jxself: yes, but binary compatibility is important for bootstrapping purposes. now i cannot try "tar" binary and so cannot untar archive <tadni_>It'd be nice to link, for people with an interest in the guix way of doing things. <jxself>Guix can be bootraped with Guix. :) <tadni_>safinaskar: Why can't you grab tar from guix? <jxself>Yeah. The 2014 ones will (I hope) be ready soon. <jxself>Someone sent in an email about that. Not sure of the status. <tadni_>Man, that was Feburary. I feel like that was soooo much longer than that. <tadni_>This year has gone by sooooo fast. <safinaskar>Ulrar: "guix isn't up to date, that's why it can't parse your config file" - but this is exactly same config i used for the first gnu/guix (which is successfully installed). so, it follows, guix in installed system is older than in installer???? <Ulrar>Wouldn't know, I've had guix installed for a few days only <safinaskar>tadni_: "Why can't you grab tar from guix?" - because guix already started and it is building something now <Ulrar>Is the binary libtoolize missing from libtool somehow ? <tadni_>safinaskar: There are multiple build users, you should be able to grab while it's building something else. <jxself>safinaskar: Yes, installing guix 0.7 installs guix 0.6 which you then need to update for it to be 0.7. It's odd! <Ulrar>My bad, just needed "bin" and "out" <drewc>What is the answer? inquiring minds want to know! <Ulrar>I guess I'll just continue to build those packages myself <Ulrar>yeah, I did manage to load it once this morning <Ulrar>gdbus doesn't build, tap-driver.sh has a I/O internal error <civodul>hydra.gnu.org seems to be doing slightly better now <Ulrar>well that might be why that vm is so slow <civodul>there are substitutes for glib on x86_64 currently <civodul>so it must build, sometimes at least ;-) <Ulrar>I guess it must, but not for me :( <DusXMT>`sometimes'? I thought packages were 99% reproducible ;) <civodul>Ulrar: could you post the build log and any additional details to bug-guix? <civodul>it builds on i686 as well, apparently <Ulrar>--keep-failed, is that right ? <DusXMT>Ulrar: As well as "2>&1 | tee build.log" <DusXMT>Ludo's suggestion might be better actually, since it doesn't involve pipes <Ulrar>It's building, it'll need some time to get to the error <DusXMT>that reminds me... waiting 2 hours just to see if a patch I wrote fixed the current source file, then it breaking on the next... (well, that exact scenario only happened once, but you get the idea) <Ulrar>So I the log file to bug-guix@gnu.org ? <civodul>Ulrar: yes, let's start with the last 100 lines of the build log, say <civodul>keep the rest around, so we can look at it if need be <civodul>ISTR that GLib's test suite produces detailed logs somewhere <Ulrar>Well that might have to wait, I have no way of getting the file out of the vm for now <Ulrar>I'll try to get ssh installed <Ulrar>Forgot I could just use ftp to transfer it :) <Ulrar>Got weechat working. Now let's try to add some of the plugins <Ulrar>So I have a patch to apply, I generated it with diff -ruN orig/ new/ > file.patch but it doesn't find the file at build. What is the correct way to generate the patch for guix ? <DusXMT>Ulrar: You need to make sure patch can use it with the -p1 argument <DusXMT>eg. a/Makefine.in b/Makefine.in instead of directly Makefile.in Makefile.in <DusXMT>I usually just generate patches with paths completely off and then fix it up with some sed magic and copy/pasting *DusXMT is obviously a noob for doing it like this. He realizes it, but it simply works for him <Ulrar>Mh, that's what I already have <DusXMT>Oh, sorry for bothering, didn't see it in the manpage <Ulrar>Mh, if I add -p1 to the arguments it works better <Ulrar>Half the patch now gets applied, the other half gets rejected <DusXMT>Ulrar: Does lua not have an autotool-styled build system? <Ulrar>DusXMT: not that I am aware of <Ulrar>That's actually just a copy of most of the ArchLinux patch <Ulrar>Mh, okay. I was missing a line before the second diff line <DusXMT>Could someone who has an account on Libreplanet remove Abiword? It's in already and seems to work properly <jxself>It was added recently, I think... <civodul>so, hackathon on the 27-28th anyone? :-) <Ulrar>Okay, so I've figured out how to make my patch work. It makes it also compile a .so for 5.1.5, should I just patch the current lua-5.1 or add something like lua-so-5.1 ?