help-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with uilding a package for intel onepi fortran compiler.


From: Céline Acary
Subject: Re: Problem with uilding a package for intel onepi fortran compiler.
Date: Fri, 2 Sep 2022 18:59:55 +0200

Hi Simon
Not really
Pierre Antoine là-dedans significative progress without reaching to suceed....
Cheers 

> Le 2 sept. 2022 à 18:46, zimoun <zimon.toutoune@gmail.com> a écrit :
> 
> Hi Cécile,
> 
> I am really late to the party.  Did you solve the issue in the meantime?
> 
>> On Wed, 13 Apr 2022 at 08:38, Céline Acary-Robert 
>> <celine.acary-robert@univ-grenoble-alpes.fr> wrote:
>> 
>> We are trying to build a package for intel onepi fortran compiler. The
>> sources are installed through a script "install" (/bin/sh) which calls
>> a binary bootstrapper which allows to download the files and install
>> them
> 
> As Thiago noticed, the network is not available inside the build
> environment.  So it would not be possible that the script would download
> these files.
> 
> The workaround is to download them beforehand, if possible, and provide
> them as inputs.  Hum, I do not find an example in the Guix source; maybe
> I remember incorrectly.
> 
> 
> 
>> ./install.sh: line 34: 
>> /tmp/guix-build-intel_oneapi-2022.0.1.70.drv-0/l_fortran-compiler_p_2022.0.1.70_offline/bootstrapper:
>>  No such file or directory 
>> error: in phase 'install': uncaught exception:
> 
> Are you sure that the file pointed by the script install.sh at the line
> 34 is provided by the source of the package.  You can examine the
> post-mortem failure with:
> 
>    guix build -f oneapi.scm -K
>    cd /tmp/guix-<blabla>/source
> 
> and inspect this line 34.
> 
> 
>>        (uri (string-append 
>> "https://registrationcenter-download.intel.com/akdlm/irc_nas/18436/l_fortran-comp$
> 
> It is hard to test myself since the URL had been mangled.  Could you
> provide where can I download the archive?  Well, if it is still an
> issue. :-)
> 
> 
> Cheers,
> simon



reply via email to

[Prev in Thread] Current Thread [Next in Thread]