Skip to content

Handle external perl#13903

Merged
alalazo merged 2 commits intospack:developfrom
scheibelp:bugfix/perl-bin-external
Nov 29, 2019
Merged

Handle external perl#13903
alalazo merged 2 commits intospack:developfrom
scheibelp:bugfix/perl-bin-external

Conversation

@scheibelp
Copy link
Copy Markdown
Member

@scheibelp scheibelp commented Nov 26, 2019

Fixes #13792
Fixes #13930

99dfff4 updated perl to add perl's bin/ directory to PATH but does not filter it when it is a system path. This removes that logic from the perl package because adding bin for a given package is already handled in Spack core (and it includes filtering logic for system dirs)

…ady handled by spack core in a way that omits system dirs); also consolidate repeated logic between build/run env setup.
@adamjstewart
Copy link
Copy Markdown
Member

adamjstewart commented Nov 26, 2019

Why do we need to set PATH at all? Aren't all prefix.bin automatically added to the PATH?

@scheibelp
Copy link
Copy Markdown
Member Author

Why do we need to set PATH at all? Aren't all prefix.bin automatically added to the PATH?

They are: I don't see special considerations for doing this separately for perl (adding modules to PATH appears to date back to #3614). So I think that should also be addressed here too.

…e, so there is no need to do this in the Perl package
@scheibelp scheibelp requested a review from becker33 November 26, 2019 23:52
@mwkrentel
Copy link
Copy Markdown
Member

I tried this and yes, it does fix the problem I reported in #13792.

Of course, you may want to check with @becker33, in case there was
some specific reason for treating perl specially.

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.

External perl breaks $PATH in build_env external perl from /usr breaks build dependencies

4 participants