Hi Davide,
On 24/02/2021 22:16, Davide Vanzo wrote:
Kenneth,
The problem is a missing M4 build dependency (and also Perl to be picky).
Me and my "bad" habit of building on a minimal OS... 😝
Here are the issues:
https://github.com/easybuilders/easybuild-easyconfigs/issues/12271
https://github.com/easybuilders/easybuild-framework/issues/3593
Thanks for opening the issues, both problems are fixed in the develop
branches now, so they will be included with the next EasyBuild release
(ETA end of March).
regards,
Kenneth
Davide
-----Original Message-----
From: Kenneth Hoste <[email protected]>
Sent: Wednesday, February 24, 2021 11:54 AM
To: Davide Vanzo <[email protected]>
Cc: [email protected]
Subject: [EXTERNAL] Re: [easybuild] WRF-3.9.1.1-foss-2020a-dmpar fails with no
output
Hi Davide,
On 24/02/2021 18:15, Davide Vanzo wrote:
Hello all!
I have been trying to build WRF-3.9.1.1-foss-2020a-dmpar but it fails
at configure step. The strange thing is that there is no output from
configure in the logs, hence it is tough to figure out what is going on.
Attached you can find the full build log.
Has anybody hit this issue before?
That's very strange, and it rings a bell for me...
First of all, the WRF configure script is not what you may think it is (an
Autotools configure script), it's a shell script that calls an
(interactive) Python script.
What happens if you try to run the script manually, does it produce any output
then?
We fixed a problem with running interactive commands that we hit with
WRF a while ago,
see
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feasybuilders%2Feasybuild-framework%2Fpull%2F3126&data=04%7C01%7CDavide.Vanzo%40microsoft.com%7Ced4ae48f3d954174570508d8d8ed1ed1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637497860227965245%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qwoyQ%2B%2FQVxr3%2FwcCKAgQADfFNiDlvaVJAzIBxCwHY9Q%3D&reserved=0
and
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feasybuilders%2Feasybuild-framework%2Fpull%2F3130&data=04%7C01%7CDavide.Vanzo%40microsoft.com%7Ced4ae48f3d954174570508d8d8ed1ed1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637497860227975240%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=KewTaaCm4ZqKoNuZ1UEbtk9ncVwo7%2B26GxtHDctiqyc%3D&reserved=0
.
It's possible you're hitting a similar issue that we haven't seen yet...
In this case, you're using a very recent EasyBuild version and Python 2
though, so your problem may be something different entirely, but perhaps
there are some clues there that help you figure out the problem.
The first "exit 1" I see in that configure script is when it checks for
the m4 command. The script is producing error messages, but maybe they
don't pop up in your log for some reason?
Can you try loading Autotools as a build dependency?
If that helps, it would be nice if you could:
* Open an issue in framework to report the missing output, perhaps our
run_cmd_qa does need a bit more love to avoid output produced by
interactive commands from disappearing.
* Open an issue or pull request to add the missing Autotools build
dependency for WRF.
regards,
Kenneth
Davide
