Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build failed ... Couldn't find file mpc-1.0.1.tar.gz anywhere... #409

Closed
ndusek opened this issue Feb 7, 2018 · 2 comments
Closed

build failed ... Couldn't find file mpc-1.0.1.tar.gz anywhere... #409

ndusek opened this issue Feb 7, 2018 · 2 comments

Comments

@ndusek
Copy link

ndusek commented Feb 7, 2018

EasyBuild version: 3.5.1
Modules type: Tcl Environment Modules, v3.2.10
OS: CentOS 6.8

We have EasyBuild installed and configured with the required options. Commands like eb -S [software] and eb [easybuild-file] -Dr work, but the out-of-the-box WRF install referenced in the docs is failing with the following trace:

== building and installing GCC/4.7.2...
== fetching files...
== FAILED: Installation ended unsuccessfully (build directory: /home/ndusek/easybuild/build/GCC/4.7.2/dummy-dummy): build failed (first 300 chars): Couldn't find file mpc-1.0.1.tar.gz anywhere, and downloading it didn't work either... Paths attempted (in order):

I've left out the specific paths, but any clue as to what the problem is here? I figure it must be something basic I'm missing since GCC should be pretty easy to install.

@boegel
Copy link
Member

boegel commented Feb 7, 2018

The problem is that MPC has changed the download locations. This is already fixed in our develop branch, see easybuilders/easybuild-easyconfigs#5662.

To work around this, you can download the tarball manually to the location that EasyBuild would (see ‘sourcepath’ in the output of ‘eb --show-config’)

@ndusek
Copy link
Author

ndusek commented Feb 7, 2018

Ok, thank you. I was about to post a comment saying I worked around it by modifying the source URL in the .eb file and that seems to have worked. I will consider the above approach for future fixes as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants