From: Catonano <catonano@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: libxsl reprise
Date: Mon, 27 Mar 2017 17:07:19 +0200 [thread overview]
Message-ID: <CAJ98PDzXa5n9Tzu5iApwrYgZvXm0eU7DoY0Xqq-kC4YqDpGs3Q@mail.gmail.com> (raw)
In-Reply-To: <20170327145456.GA15153@jasmine>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
2017-03-27 16:54 GMT+02:00 Leo Famulari <leo@famulari.name>:
> On Mon, Mar 27, 2017 at 04:30:47PM +0200, Catonano wrote:
> > In building libxsl I run into this error
> >
> > /gnu/store/qkw4zrwfybxww8f56nkb6hggxambk89b-bash-4.4.0/bin/bash:
> > ./configure: No such file or directory
>
> [...]
>
> > I added this piece
> >
> > (arguments
> > `(#:phases
> > (modify-phases %standard-phases
> > (add-before
> > 'configure 'pre-conigure
> > (lambda* (#:key inputs #:allow-other-keys)
> > (chdir "source/"))))))
> >
> >
> > I also tried with
> >
> > (chdir "source/libxsl"))))))
> >
> > and I get
> >
> > ERROR: In procedure chdir:
> > ERROR: In procedure chdir: No such file or directory
> >
> > No such file or directory ?
> >
> > What am I missing now ?
>
> Without the libxsl package definition, it's hard to say exactly what's
> going wrong. But, you could add the package 'tree' to (native-inputs)
> and then add a line like this to your pre-configure phase:
>
>
(zero? (system* "tree"))
>
> ... and it might help.
>
Ah. This will be useful too. Thanks
[-- Attachment #2: Type: text/html, Size: 1853 bytes --]
next prev parent reply other threads:[~2017-03-27 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 14:30 libxsl reprise Catonano
2017-03-27 14:51 ` Adonay Felipe Nogueira
2017-03-27 15:02 ` Catonano
2017-03-27 15:37 ` Adonay Felipe Nogueira
2017-03-27 14:54 ` Leo Famulari
2017-03-27 15:07 ` Catonano [this message]
2017-03-27 15:22 ` Quiliro
2017-03-27 15:26 ` Catonano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ98PDzXa5n9Tzu5iApwrYgZvXm0eU7DoY0Xqq-kC4YqDpGs3Q@mail.gmail.com \
--to=catonano@gmail.com \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).