all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dennis Mungai <dmngaie@gmail.com>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: 23055@debbugs.gnu.org
Subject: bug#23055: wget within guix fails to resolve FQDNs when used as an input (native or otherwise)
Date: Fri, 18 Mar 2016 21:23:24 +0300	[thread overview]
Message-ID: <CAKKYfmGdOhrN4h8BGArAgmgqDZ_--gunYagaf89NZra7yiQNNg@mail.gmail.com> (raw)
In-Reply-To: <CAJ=RwfYMnoJ8qZdfWGiLnpzHdsV_HSu-PNwt+E-3HzyBwCcSBg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2007 bytes --]

Hello David,

Thanks for the clarification.

Seems Arrayfire will need several modify-phases statements to clean up the
current build system and in addition, port Boost.Compute to GNU Guix as an
input.

Will do, and provide feedback on the same.

Thanks and regards,

Dennis Mungai.

On 18 March 2016 at 21:15, Thompson, David <dthompson2@worcester.edu> wrote:

> On Fri, Mar 18, 2016 at 2:04 PM, Dennis Mungai <dmngaie@gmail.com> wrote:
>
> > As you can see in the first part, fetching BoostCompute fails because the
> > specified MD5 hash fails, and as a result, the build system falls back to
> > fetching the same with wget (see second snippet).
> >
> > The second part fails because wget fails to resolve the FQDN entry
> > github.com.
> >
> > However, when invoking wget directly, both the local instalation and the
> > Guix installation, the FQDN can be resolved correctly and the associated
> > file fetched successfully:
> >
> > /gnu/store/w50mfvfzyjzpcbyw3lll7hm4j457jhb0-wget-1.17.1/bin/wget
> > https://github.com/boostorg/compute/archive/v0.5.tar.gz
> >
> > Would this qualify as a bug filed against wget in Guix, or does the
> problem
> > lie elsewhere?
>
> In Guix, builds are performed in an isolated container where there is
> *no* external network access.  It must be this way because otherwise
> builds would be non-deterministic. The only exception is for "fixed
> output derivations", whose checksum is known in advance, which
> wouldn't be the case here.  So, the problem lies with Arrayfire's
> build system.  A build system really shouldn't download from the net.
> It should use what the system has provided for it.  In my experience,
> build systems that try to download from the net usually try to find
> something to use locally first.  Without knowing anything beyond the
> log you've shown me, I would guess that you need to package
> BoostCompute first and provide that as an input to Arrayfire.
> Hopefully then it won't try to download it.
>
> Hope this helps!
>
> - Dave
>

[-- Attachment #2: Type: text/html, Size: 2797 bytes --]

  reply	other threads:[~2016-03-18 18:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18 18:04 bug#23055: wget within guix fails to resolve FQDNs when used as an input (native or otherwise) Dennis Mungai
2016-03-18 18:15 ` Thompson, David
2016-03-18 18:23   ` Dennis Mungai [this message]
2016-03-19  7:36     ` Dennis Mungai

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=CAKKYfmGdOhrN4h8BGArAgmgqDZ_--gunYagaf89NZra7yiQNNg@mail.gmail.com \
    --to=dmngaie@gmail.com \
    --cc=23055@debbugs.gnu.org \
    --cc=dthompson2@worcester.edu \
    /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.