octopus: in-code comments to explain compiler flags
This commit is contained in:
parent
90070c317d
commit
5333a799ea
1 changed files with 7 additions and 4 deletions
|
@ -70,10 +70,13 @@ def install(self, spec, prefix):
|
|||
# --with-berkeleygw-prefix=${prefix}
|
||||
])
|
||||
|
||||
# Supposedly configure does not pick up the required flags for gfortran
|
||||
# Without it there are:
|
||||
# Error: Line truncated @ global.F90:157:132
|
||||
# Error: Unterminated character constant @ global.F90:157:20
|
||||
# When preprocessor expands macros (i.e. CFLAGS) defined as quoted
|
||||
# strings the result may be > 132 chars and is terminated.
|
||||
# This will look to a compiler as an Unterminated character constant
|
||||
# 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'):
|
||||
args.extend([
|
||||
'FCFLAGS=-O2 -ffree-line-length-none'
|
||||
|
|
Loading…
Reference in a new issue