From: Catonano <catonano@gmail.com>
To: Eric Bavier <ericbavier@openmailbox.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: tree doesn't get called
Date: Mon, 8 May 2017 07:02:29 +0200 [thread overview]
Message-ID: <CAJ98PDwszMbkZ9GjPhugBOnUxAsjuHX1An5io6qzD3vd0CsAzw@mail.gmail.com> (raw)
In-Reply-To: <20170505172459.158487fc@openmailbox.org>
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
Eric,
2017-05-06 0:24 GMT+02:00 Eric Bavier <ericbavier@openmailbox.org>:
> On Fri, 5 May 2017 17:50:53 +0200
> Catonano <catonano@gmail.com> wrote:
>
> > stranded as usual.
> >
> > So here's the package
> > http://paste.lisp.org/display/345871
> >
> > What is wrong with it ?
> >
> > The build fails, the build folder (kept in /tmp) is empty
> >
> > Further, when I attempt to call tree, tree doesn't get called
>
> trivial-build-system requires you to do a lot manually. In this case
> '(zero? (system* "tree"))' fails because it's not found in $PATH.
>
> And the build folder is empty because the builder doesn't put anything
> there! :) Since you're working from a git checkout here, you could
> probably copy/compile things directly from the source checkout to 'out'.
>
> Hope that helps,
> `~Eric
>
>
Thank you so much or your help
Would you mind to take a look at this new version ?
http://paste.lisp.org/display/346142
The
(copy-file file
dest-file)
piece fails with
...
In unknown file:
?: 0 [copy-file "include.scm" ...]
ERROR: In procedure copy-file:
ERROR: In procedure copy-file: No such file or directory
But as you can see on te "tree" output, include.scm is there indeed
Thanks in advance
[-- Attachment #2: Type: text/html, Size: 4877 bytes --]
next prev parent reply other threads:[~2017-05-08 5:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 15:50 tree doesn't get called Catonano
2017-05-05 22:24 ` Eric Bavier
2017-05-08 5:02 ` Catonano [this message]
2017-05-08 6:08 ` Ricardo Wurmus
2017-05-08 17:14 ` Catonano
2017-05-08 17:45 ` Catonano
2017-05-08 20:19 ` Ricardo Wurmus
2017-05-09 15:41 ` Catonano
2017-05-09 15:43 ` Catonano
2017-05-10 19:51 ` Ricardo Wurmus
2017-05-11 4:20 ` Catonano
2017-05-09 17:20 ` Ricardo Wurmus
2017-05-09 18:12 ` Catonano
2017-05-08 7:34 ` Mark H Weaver
2017-05-08 17:28 ` Catonano
2017-05-08 17:58 ` Ricardo Wurmus
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=CAJ98PDwszMbkZ9GjPhugBOnUxAsjuHX1An5io6qzD3vd0CsAzw@mail.gmail.com \
--to=catonano@gmail.com \
--cc=ericbavier@openmailbox.org \
--cc=help-guix@gnu.org \
/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).