From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dennis Mungai Subject: bug#23055: wget within guix fails to resolve FQDNs when used as an input (native or otherwise) Date: Sat, 19 Mar 2016 10:36:35 +0300 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c0a79ca5db6ba052e61ecbf Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34437) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ahBRZ-0003XL-In for bug-guix@gnu.org; Sat, 19 Mar 2016 03:37:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ahBRW-0007fA-BI for bug-guix@gnu.org; Sat, 19 Mar 2016 03:37:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:56040) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ahBRW-0007em-6r for bug-guix@gnu.org; Sat, 19 Mar 2016 03:37:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ahBRW-0001ke-0M for bug-guix@gnu.org; Sat, 19 Mar 2016 03:37:02 -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: "Thompson, David" Cc: 23055@debbugs.gnu.org --94eb2c0a79ca5db6ba052e61ecbf Content-Type: text/plain; charset=UTF-8 Update: All worked out. I was able to port over the dependencies to guix and fed them as inputs to the package in question. All builds as expected. Thanks and regards, Dennis Mungai. On 18 March 2016 at 21:23, Dennis Mungai wrote: > 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 > wrote: > >> 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 >> > > --94eb2c0a79ca5db6ba052e61ecbf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Update:

All worked o= ut.

I was able to port over the dependencies to guix and fed t= hem as inputs to the package in question.
All builds as expected.<= br>
Thanks and regards,

Dennis Mungai.

On 18 March 2016 at 21= :23, Dennis Mungai <dmngaie@gmail.com> wrote:
Hello David,<= br>
Thanks for the clarification.

Seems Arrayfire wi= ll need several modify-phases statements to clean up the current build syst= em and in addition, port Boost.Compute to GNU Guix as an input.

Will do, and provide feedback on the same.

Thanks and regard= s,

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
> git= hub.com.
>
> However, when invoking wget directly, both the local instalation and t= he
> Guix installation, the FQDN can be resolved correctly and the associat= ed
> file fetched successfully:
>
> /gnu/store/w50mfvfzyjzpcbyw3lll7hm4j457jhb0-wget-1.17.1/bin/wget
> https://github.com/boostorg/compute/arch= ive/v0.5.tar.gz
>
> Would this qualify as a bug filed against wget in Guix, or does the pr= oblem
> lie elsewhere?

In Guix, builds are performed in an isolated container where there is
*no* external network access.=C2=A0 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.=C2=A0 So, the problem lies with Arrayfire= 9;s
build system.=C2=A0 A build system really shouldn't download from the n= et.
It should use what the system has provided for it.=C2=A0 In my experience,<= br> build systems that try to download from the net usually try to find
something to use locally first.=C2=A0 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


--94eb2c0a79ca5db6ba052e61ecbf--