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

new versions of TFEL and MGIS #14249

Merged
merged 73 commits into from
Jan 9, 2020
Merged

new versions of TFEL and MGIS #14249

merged 73 commits into from
Jan 9, 2020

Conversation

thelfer
Copy link
Contributor

@thelfer thelfer commented Dec 20, 2019

No description provided.

alalazo and others added 30 commits May 18, 2016 08:28
- Bugfixes for spack find
- 0.9.1 can read specs from current develop.
* Revert "Quick fix for relocation issues."

This reverts commit 57608a6.

* Buildcache: relocate fixes (spack#6512)

* Updated function which checks if a binary file needs relocation.
  Previously this was incorrectly identifying ELF binaries as symbolic
  links (so they were being excluded from relocation). Added test to
  check that ELF binaries are not considered symlinks.

* relocate_text was not replacing paths in text files. Added test to
  check that text files are relocated properly (i.e. paths in the file
  are converted to the new prefix).

* Exclude backup files created by filter_file when installing from
  binary cache.

* Update write_buildinfo_file method signature to distinguish between
  the spec prefix and the working directory for the binary cache
  package.
This adds the ability for packages to apply compiler flags in one of
three ways: by injecting them into the compiler wrapper calls (the
default in this PR and previously the only automated choice);
exporting environment variable definitions for variables with
corresponding names (e.g. CPPFLAGS=...); providing them as arguments
to the build system (e.g. configure).

When applying compiler flags using build system arguments, a package
must implement the 'flags_to_build_system_args" function. This is
provided for CMake and autotools packages, so for packages which
subclass those build systems, they need only update their flag
handler method specify which compiler flags should be specified as
arguments to the build system.

Convenience methods are provided to specify that all flags be applied
in one of the 3 available ways, so a custom implementation is only
required if more than one method of applying compiler flags is
needed.

This also removes redundant build system definitions from tutorial
examples
The flag_handlers method was being set as a bound method, but when
reset in the package.py file it was being set as an unbound method
(all python2 issues). This gets the underlying function information,
which is the same in either case.

The bug was uncovered for parmetis in spack#6858. This is a partial fix.
Included are changes to the parmetis package.py file to make use of
flag_handlers.
* Adding flags to codecov reports

* OSX builds are triggered once a day
…pack#6515) (spack#7027)

"brew install gcc" fails for travis build because of an existing
/usr/local/include/c++. This commit removes the offending file
as suggested by brew.
@thelfer
Copy link
Contributor Author

thelfer commented Dec 20, 2019

@adamjstewart Thanks for the review. I'll modify this ASAP.

@adamjstewart
Copy link
Member

The only thing preventing merging is this flake8 error:

var/spack/repos/builtin/packages/tfel/package.py:145: [W293] blank line contains whitespace

@adamjstewart adamjstewart merged commit ff23672 into spack:develop Jan 9, 2020
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.

None yet

6 participants