[Reproduce-devel] [bug #56715] Check for working C and Fortran compiler

[Mohammad Akhlaghi]

URL:
  <https://savannah.nongnu.org/bugs/?56715>

                 Summary: Check for working C and Fortran compiler
                 Project: Reproducible paper template
            Submitted by: makhlaghi
            Submitted on: Sun 04 Aug 2019 11:35:05 PM BST
                Category: Software
                Severity: 3 - Normal
              Item Group: Crash
                  Status: In Progress
                 Privacy: Public
             Assigned to: makhlaghi
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

It can happen that the host C or Fortran compilers don't work properly, even
if they are present. For example with errors like this (both happened on
different macOS systems).

For the C compiler

conftest.c:9:19: fatal error: stdio.h: No such file or directory
 #include <stdio.h>
                   ^
compilation terminated.


For the Fortran compiler

dyld: Library not loaded: @rpath/libisl.10.dylib
Referenced from:
/Users/Mahdieh/anaconda2/gcc/libexec/gcc/x86_64-apple-darwin15.5.0/4.9.3/f951
Reason: image not found
gfortran: internal compiler error: Abort trap: 6
-verbatim

These errors usually show up during the configuration of the programs (the C
error in `flock' and the Fortran error in WCSLIB).

But since the actual report of the configure-time checks are in their
`config.log' and within the project's closed environment, its much more easier
and clear for the users if we check them at the start of the configure script,
before actually building any of the software.  I am busy adding some small
tests to do this.




    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/bugs/?56715>

_______________________________________________
  Message sent via Savannah
  https://savannah.nongnu.org/