Skip to content

Implicit rpaths for NAG/GCC mixed toolchain#14782

Merged
becker33 merged 2 commits intospack:developfrom
skosukhin:nag_implicit_rpaths
Jun 3, 2020
Merged

Implicit rpaths for NAG/GCC mixed toolchain#14782
becker33 merged 2 commits intospack:developfrom
skosukhin:nag_implicit_rpaths

Conversation

@skosukhin
Copy link
Copy Markdown
Member

This PR enables the implicit rpath detection for NAG/GCC mixed toolchain and makes sure that it won't be as difficult to identify a similar problem for a new compiler.

@skosukhin skosukhin force-pushed the nag_implicit_rpaths branch from c6e62d6 to 2c15358 Compare February 6, 2020 12:55
@adamjstewart
Copy link
Copy Markdown
Member

@ThemosTsikas

@skosukhin skosukhin force-pushed the nag_implicit_rpaths branch from 24d2f28 to ffab396 Compare June 2, 2020 10:14
@skosukhin
Copy link
Copy Markdown
Member Author

@becker33 could you, please, take a look? This adds a verbose_flag for NAG and makes sure that the compiler is run with required environment modifications. For example, NAG fails if the environment variable NAG_KUSARI_FILE is not set and it is normally set either with the modules or environment sections of compilers.yaml.

This is relevant for other compilers too. For example, Intel compiler uses the first gcc in the PATH by default and we need to account for the case when the variable is modified in compilers.yaml.

@skosukhin skosukhin force-pushed the nag_implicit_rpaths branch from 3d51501 to 4c943e3 Compare June 2, 2020 13:05
@becker33 becker33 merged commit 7aa9cb0 into spack:develop Jun 3, 2020
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

Successfully merging this pull request may close these issues.

3 participants