From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Thompson, David" Subject: bug#23055: wget within guix fails to resolve FQDNs when used as an input (native or otherwise) Date: Fri, 18 Mar 2016 14:15:37 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34020) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1agywQ-00016N-BZ for bug-guix@gnu.org; Fri, 18 Mar 2016 14:16:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1agywM-0005TV-4t for bug-guix@gnu.org; Fri, 18 Mar 2016 14:16:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:55807) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1agywM-0005TO-0X for bug-guix@gnu.org; Fri, 18 Mar 2016 14:16:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1agywL-0007rJ-Nl for bug-guix@gnu.org; Fri, 18 Mar 2016 14:16:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Dennis Mungai Cc: 23055@debbugs.gnu.org On Fri, Mar 18, 2016 at 2:04 PM, Dennis Mungai 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