Re: libxsl reprise

El Mon, 27 Mar 2017 16:30:47 +0200 Catonano escribió: >'configure 'pre-conigure Is it not?: 'configure 'pre-configure -- Example of rude top posting: A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A:

Re: libxsl reprise

You're welcome! :) I'm glad it worked well.

Re: autom4te

On Mon, Mar 27, 2017 at 07:47:30PM +0200, Catonano wrote: > is autom4te in Guix ? It's part of m4.

autom4te

is autom4te in Guix ? I can't find it Thanks

Re: autom4te

2017-03-27 20:03 GMT+02:00 Leo Famulari : > On Mon, Mar 27, 2017 at 07:47:30PM +0200, Catonano wrote: > > is autom4te in Guix ? > > It's part of m4. > is it ? I made a --ad-hoc environment with m4 and I can't call it Thanks, anyway

Re: autom4te

On Mon, Mar 27, 2017 at 08:06:26PM +0200, Catonano wrote: > 2017-03-27 20:03 GMT+02:00 Leo Famulari : > > > On Mon, Mar 27, 2017 at 07:47:30PM +0200, Catonano wrote: > > > is autom4te in Guix ? > > > > It's part of m4. > > > > is it ? > > I made a --ad-hoc environment with

Re: libxsl reprise

2017-03-27 16:51 GMT+02:00 Adonay Felipe Nogueira : > Try: > > (chdir "libxsl") > > The reason for this suggestion is that "source" is already > traversed/changed-to after "unpack" phase. Because Guix already tries to > change to first directory it finds in the source. >

libxsl reprise

In building libxsl I run into this error /gnu/store/qkw4zrwfybxww8f56nkb6hggxambk89b-bash-4.4.0/bin/bash: ./configure: No such file or directory In keeping the build directory, as Pjotr notes in his notes, I find /tmp/guix-build-libxsl-1.4.0.drv-0$ ls environment-variables source/ configure

Re: libxsl reprise

Try: (chdir "libxsl") The reason for this suggestion is that "source" is already traversed/changed-to after "unpack" phase. Because Guix already tries to change to first directory it finds in the source. If it still doesn't work, revert the one I just recommended, and add: ... before the