***Infiltra1or is now known as Infiltrator
<manolis1>mark_weaver: phant0mas here just from another computer <manolis1>mach recipe works when I build it with system i686 <manolis1>I still don't like that I have to use 32 bit enviroment to build it <manolis1>I should make it build from a 64 bit as well <davexunit>manolis1: yeah he's on vacation for a few days. <mark_weaver>but you should realize that what we're doing here is preparing for cross-compilation. <manolis1>that's why I have to make it to build regardless of the system <manolis1>even though if we have a hurd guix machine it will be on 32 bits so it will work no problem <mark_weaver>I haven't researched this issue properly, but my impression is that in this case we were able to basically avoid cross-compilation by doing native compilation from a 32-bit user environment. <mark_weaver>so if not for --system=i686-linux, there would have to be something else that might have been even less convenient. <mark_weaver>but we shouldn't be worrying too much about the convenience of these cross-compilation steps. <mark_weaver>because this is something that we'll have to do just once. users won't have to do these steps after we've built bootstrap tarballs for hurd. <manolis1>I will first try to build it the normal way <manolis1>and then when I am sure what I am doing, I will start doing the same on guix <mark_weaver>you'll have to modify the existing glibc recipe in base.scm, but only when the target system is hurd. <mark_weaver>okay, that sounds good. I would rather that civodul help you with this part anyway. <fdsfssd>mark_weaver: You might be interested to know that I'm making some progress on supporting signed NAR info files. I intend to post a rough version tonight and would be glad to hear some feedback. <dfsdfsd>are you familiar with libgcrypt's gcry_pk_genkey function? <dfsdfsd>"The argument is a string with a number in C-notation. The value should be a multiple of 8." <dfsdfsd>Are you familiar with the mentioned notation? <mark_weaver>I suppose I would do some web searches, and failing that, look in the source code. <dfsdfsd>(I need it to test the 'parse-signature' function that I wrote.) <dfsdfsd>mark_weaver: I've just found out on #gnupg. <dfsdfsd>mark_weaver: I'm trying to use 'test-error' from SRFI-64 but keep getting syntax errors even though 'test-assert' works. Any idea? <dfsdfsd>Basically, I do (in REPL): (test-begin "foo"), then (test-error (error "foo")). After that I get a syntax error. <dfsdfsd>unknown file:3:0: source expression failed to match any pattern in form (%test-error #t (error "foo")) <dfsdfsd>That's for (test-error (error "foo")) <dfsdfsd>I didn't take it from schemers.org. It probably comes from guix (see srfi in the tree); but how can I check? <mark_weaver>guix has guile-2.0.9, which does not include srfi-64 <dfsdfsd>I have srfi/srfi-64.scm in the tree. <mark_weaver>sounds like you got it from somewhere else. that's not the version I made. <dfsdfsd>When I said guix, I meant the source tree of the project. <mark_weaver>I recently ported SRFI-64 to guile and made many fixes to it for guile-2. <mark_weaver>dfsdfsd: almost done, just waiting for 'make check' to complete on my Yeeloong. <mark_weaver>tests/builders.scm takes a long time on this machine... <dfsdfsd>Everything takes a long time on YeeLoong. <mark_weaver>hmm, is this thing doing a full bootstrap from source in test-tmp? <mark_weaver>I guess I shouldn't have removed that directory a while ago :-( <dfsdfsd>Frankly, I have no idea. But there are a lot of files in that directory, indeed. <mark_weaver>well, I went ahead and bravely pushed the SRFI-64 update to master. hopefully I didn't break anything :) <mark_weaver>if you could run a 'make check' to verify that things still work, I'd be grateful. <dfsdfsd>Indeed, 'test-error' now works as it should. <dfsdfsd>mark_weaver: How do I catch a specific error? <dfsdfsd>(test-error "two" "expected" (error "real")) doesn't seem to do the right thing. <mark_weaver>checking for a specific error is not currently implemented in srfi-64 for guile. <mark_weaver>but you could do it by using guile-specific constructs.