From: ludo@gnu.org (Ludovic Courtès)
To: Adonay Felipe Nogueira <adfeno@openmailbox.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Are these paths important to fix/set to (in/out)puts?
Date: Wed, 05 Oct 2016 23:39:11 +0200 [thread overview]
Message-ID: <8760p65vcw.fsf@gnu.org> (raw)
In-Reply-To: <1475599187.4862.30.camel@adfeno-VPCEG17FB> (Adonay Felipe Nogueira's message of "Tue, 04 Oct 2016 13:39:47 -0300")
Adonay Felipe Nogueira <adfeno@openmailbox.org> skribis:
> Although I can barely understand what is written in these files, I see
> paths pointing to "/usr" or simply to paths starting from "/". There are
> others, however, that don't seem to be standard in GuixSD, but are still
> tested for in the files described in the attachment (that is, depending
> on the system being used, its directory hierarchy, and the order of the
> tests, then a different action might be triggered).
You can safely ignore hardcoded file names in Autoconf-generated files
and similar like those that appeared in the file attached to your
message. gnu-build-system.scm addresses most of these after unpacking
the tarball.
> There is a possibility that can answer my question more safely, that is:
> I don't know if `guix build` isolates the build environment by default,
> but if this is really done by default, then we can focus on fixing paths
> related to the typical directory hierarchy of of GuixSD.
Builds are isolated:
https://www.gnu.org/software/guix/manual/html_node/Build-Environment-Setup.html
HTH!
Ludo’.
next prev parent reply other threads:[~2016-10-05 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 16:39 Are these paths important to fix/set to (in/out)puts? Adonay Felipe Nogueira
2016-10-05 21:39 ` Ludovic Courtès [this message]
2016-10-16 12:01 ` Adonay Felipe Nogueira
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760p65vcw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=adfeno@openmailbox.org \
--cc=guix-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.