Skip to content

ALADIN bug fix: catch question for libgrib_api.a location instead of ignoring it#165

Merged
boegel merged 6 commits intoeasybuilders:v1.3.xfrom
boegel:aladin_fix
Mar 31, 2013
Merged

ALADIN bug fix: catch question for libgrib_api.a location instead of ignoring it#165
boegel merged 6 commits intoeasybuilders:v1.3.xfrom
boegel:aladin_fix

Conversation

@boegel
Copy link
Copy Markdown
Member

@boegel boegel commented Mar 31, 2013

Sometimes the ALADIN build procedure asks explicitly for the libgrib_api.a location, the other time it derives it by itself and just requests to confirm correctness.

This patch now also answers the explicit question properly.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

from what I understand, there was a convoluted mix-up of the api & api_f90 cases;
if so, it all looks good now, AFAI can tell... green light from this side.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It wasn't really a mixup exactly.

Specifying the location of libgrib_api_f90.a is always required, and sometimes (apparently) the location of libgrib_api.a is also requested.
Most of the time, the latter is automatically derived from the former whoever, and you just have to confirm the correctness of the derived value (which is handled by another regex).

This patch fixes the sometimes case, which I ran into during the regtests prior to v1.3.0.

boegel added a commit that referenced this pull request Mar 31, 2013
ALADIN bug fix: catch question for libgrib_api.a location instead of ignoring it
@boegel boegel merged commit 9dd37a7 into easybuilders:v1.3.x Mar 31, 2013
@boegel boegel deleted the aladin_fix branch March 31, 2013 18:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants