zhangyiss/spack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

octopus: in-code comments to explain compiler flags

Browse Source
This commit is contained in:
Denis Davydov 2016-08-29 08:45:28 +02:00
parent 90070c317d
commit 5333a799ea
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
var/spack/repos/builtin/packages/octopus/package.py
View File

@ -70,10 +70,13 @@ def install(self, spec, prefix):
# --with-berkeleygw-prefix=${prefix} # --with-berkeleygw-prefix=${prefix}
]) ])
# Supposedly configure does not pick up the required flags for gfortran # When preprocessor expands macros (i.e. CFLAGS) defined as quoted
# Without it there are: # strings the result may be > 132 chars and is terminated.
# Error: Line truncated @ global.F90:157:132 # This will look to a compiler as an Unterminated character constant
# Error: Unterminated character constant @ global.F90:157:20 # and produce Line truncated errors. To vercome this, add flags to
# let compiler know that the entire line is meaningful.
# TODO: For the lack of better approach, assume that clang is mixed
# with GNU fortran.
if spec.satisfies('%clang') or spec.satisfies('%gcc'): if spec.satisfies('%clang') or spec.satisfies('%gcc'):
args.extend([ args.extend([
'FCFLAGS=-O2 -ffree-line-length-none' 'FCFLAGS=-O2 -ffree-line-length-none'