-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 01/17/2016 05:14 PM, Orion Poplawski wrote:
> On 01/17/2016 04:28 AM, Antonio Trande wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
>> 
>> On 01/17/2016 12:08 AM, Orion Poplawski wrote:
>>> On 01/16/2016 03:44 PM, Antonio Trande wrote:
>>>> Am I missing something? Any comment/idea?
>>> 
>>> Really impossible to tell without the cmake output logs, 
>>> specifically CMakeFiles/CMakeError.log.
>>> 
>> 
>> Hardened flags break cmake's MPI Fortran compiler test; I had to 
>> add
>> 
>> %if 0%{?rhel} && 0%{?rhel} > 6 %undefine _hardened_build %endif
>> 
> 
> Did you ever determine the exact error the compiler was emitting?
> 
> 

I have not found any error log but I found the config file that
perform MPI compiler test by adding --debug-output to cmake.

I forget that in my SPEC file I had already disabled MPI compiler
tests for Fedora>22 too; this confirms incompatibilities with hardened
flags.

In past, I have seen problem like that in this thread caused by link
flags but in this case I don't know why hardened flags breaks MPI
compiler test. So, there are 2 choices:

undefine hardened builds
or
disable MPI compiler tests

I chose second one.

- -- 
Antonio Trande

mailto: sagitter 'at' fedoraproject 'dot' org
http://fedoraos.wordpress.com/
https://fedoraproject.org/wiki/User:Sagitter
GPG Key: 0x565E653C
Check on https://keys.fedoraproject.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWm8ckAAoJEF5tK7VWXmU8h5gH/RBcBNRH9qDW7do/LCY/D0RZ
ZSl2tk216ibEZYKhd4UDlFUYJgO4IhdrBHgPEAIQ79wf6mMtxBjUKLt4XcrOvLzF
V2AARddq4mBzrsS3MdEeUoUMNoEHvbP6Rp1ETD3cfgXAXy0eEvUuEa24TySw5Y+c
cEI19AUmfGQ9CXp3rFljHrr/M3o8gtSukMX/H6Plf5XNTqKphpSFxaNXHM3gVjpg
s7o5n4+txzfkgzcqE6gRggL5DVpeLlwrEHxUi6j7OBIqkjWjA1lYVqCFSv1d+QmH
8Nkvyel4uynjHqi17OAtlDsVSObtotB26a/Lx0XtRJ1xtOrm5pv6H8Y4c148iDY=
=ChHW
-----END PGP SIGNATURE-----
_______________________________________________
epel-devel mailing list
[email protected]
http://lists.fedoraproject.org/admin/lists/[email protected]

Reply via email to