Opened 6 years ago

Closed 5 years ago

Last modified 3 years ago

#57358 closed defect (fixed)

sundials @3.1.2_1: ERROR: FFLAGS='-pipe -Os' and FCFLAGS='-pipe -Os -m64' are both set but are not equal.

Reported by: dershow Owned by:
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: diochnos, MarcusCalhoun-Lopez (Marcus Calhoun-Lopez), jjstickel (Jonathan Stickel)
Port: sundials

Description

I have sundials 2.8_1 installed, and I attempted to upgrade to 2.9_0. First it reported this:

--->  Configuring sundials
Error: mpich-default has a different Fortran variant (gcc7) than the one selected, gcc8 (via +gfortran).
Error: Failed to configure sundials: Install mpich-default +gcc8
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_sundials/sundials/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

mpich-default was already installed with defaults (variant +gcc7), and it hadn't indicated that there was an upgrade. So, I reinstalled it, so that it would rebuild to the new defaults: +gcc8.

I then again tried to upgrade sundials, and it still fails to configure. I have attached my log.

Attachments (1)

main.log (17.6 KB) - added by dershow 6 years ago.

Download all attachments as: .zip

Change History (22)

Changed 6 years ago by dershow

Attachment: main.log added

comment:1 Changed 6 years ago by Schamschula (Marius Schamschula)

Cc: seanfarley removed
Owner: set to seanfarley
Status: newassigned

I also ran into this. I installed mpich-gcc8, and all was well.

Last edited 6 years ago by Schamschula (Marius Schamschula) (previous) (diff)

comment:2 Changed 6 years ago by dershow

Thanks. I just tried it, but it isn't working for me. I also tried to install mpich-gcc8 and then did what the port notes say: sudo port select --set mpi mpich-gcc8-fortran and it still doesn't build for me.

comment:3 Changed 6 years ago by jsmoon7605

You need to install mpich-default with the variant gcc8 (sudo port install mpich-default +gcc8). It will be automatically activated. Then, you can uninstall the previous one (optional).

comment:4 Changed 6 years ago by dershow

Nope, mpich-default doesn't do it. It's still not working for me:

$ port installed mpich-default
The following ports are currently installed:
  mpich-default @3.2.1_4+gcc6
  mpich-default @3.2.1_4+gcc7
  mpich-default @3.2.1_4+gcc8 (active)
$ sudo port clean sundials
--->  Cleaning sundials
$ sudo port upgrade sundials
--->  Computing dependencies for sundials
--->  Fetching archive for sundials
--->  Attempting to fetch sundials-3.1.2_1+accelerate+gfortran+mpich.darwin_17.x86_64.tbz2 from https://packages.macports.org/sundials
--->  Attempting to fetch sundials-3.1.2_1+accelerate+gfortran+mpich.darwin_17.x86_64.tbz2 from http://ywg.ca.packages.macports.org/mirror/macports/packages/sundials
--->  Attempting to fetch sundials-3.1.2_1+accelerate+gfortran+mpich.darwin_17.x86_64.tbz2 from http://lil.fr.packages.macports.org/sundials
--->  Fetching distfiles for sundials
--->  Verifying checksums for sundials
--->  Extracting sundials
--->  Applying patches to sundials
--->  Configuring sundials
Error: Failed to configure sundials: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_sundials/sundials/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

comment:5 Changed 6 years ago by dershow

Here is the last part of the log file, where the error occurs:

:info:configure -- Searching for a Fortran compiler... /opt/local/bin/mpif90-mpich-mp
:info:configure CMake Error at config/SundialsCMakeMacros.cmake:94 (MESSAGE):
:info:configure   ************************************************************
:info:configure   ERROR: FFLAGS='-pipe -Os' and FCFLAGS='-pipe -Os -m64' are both set but are
:info:configure   not equal.
:info:configure   ************************************************************
:info:configure Call Stack (most recent call first):
:info:configure   config/SundialsFortran.cmake:55 (PRINT_ERROR)
:info:configure   CMakeLists.txt:628 (INCLUDE)
:info:configure -- Configuring incomplete, errors occurred!
:info:configure See also "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_sundials/sundials/work/build/CMakeFiles/CMakeOutput.log".
:info:configure See also "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_sundials/sundials/work/build/CMakeFiles/CMakeError.log".
:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_sundials/sundials/work/build" && /opt/local/bin/cmake -G "CodeBlocks - Unix Makefiles" -DCMAKE_BUILD_TYPE=MacPorts -DCMAKE_INSTALL_PREFIX="/opt/local" -DCMAKE_INSTALL_NAME_DIR="/opt/local/lib" -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_C_COMPILER="$CC" -DCMAKE_CXX_COMPILER="$CXX" -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_POLICY_DEFAULT_CMP0060=NEW -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_MODULE_PATH="/opt/local/share/cmake/Modules" -DCMAKE_PREFIX_PATH="/opt/local/share/cmake/Modules" -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON -DCMAKE_INSTALL_RPATH="/opt/local/lib" -Wno-dev -DEXAMPLES_ENABLE_C=OFF -DEXAMPLES_ENABLE_CXX=OFF -DEXAMPLES_ENABLE_F77=OFF -DEXAMPLES_ENABLE_F90=OFF -DBLAS_ENABLE=OFF -DLAPACK_ENABLE=ON -DFCMIX_ENABLE=ON -DKLU_ENABLE=ON -DKLU_LIBRARY_DIR=/opt/local/lib -DKLU_INCLUDE_DIR=/opt/local/include -DCMAKE_INCLUDE_DIRECTORIES_BEFORE=ON -DSUNDIALS_INDEX_TYPE=int32_t -DBLA_VENDOR=Apple -DCMAKE_OSX_ARCHITECTURES="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET="10.13" -DCMAKE_OSX_SYSROOT="/" -DMPI_ENABLE=ON -DMPI_MPICC=/opt/local/bin/mpicc-mpich-mp -DMPI_MPICXX=/opt/local/bin/mpicxx-mpich-mp -DMPI_MPIF77=/opt/local/bin/mpif77-mpich-mp -DMPI_MPIF90=/opt/local/bin/mpif90-mpich-mp -DMPI_RUN_COMMAND=/opt/local/bin/mpiexec-mpich-mp /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_sundials/sundials/work/sundials-3.1.2 
:info:configure Exit code: 1
:error:configure Failed to configure sundials: configure failure: command execution failed
:debug:configure Error code: NONE
:debug:configure Backtrace: configure failure: command execution failed
:debug:configure     while executing
:debug:configure "$procedure $targetname"
:error:configure See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_sundials/sundials/main.log for details.

Any ideas?

comment:6 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)

Summary: Sundials upgrade to 2.9_0 failssundials @3.1.2_1: ERROR: FFLAGS='-pipe -Os' and FCFLAGS='-pipe -Os -m64' are both set but are not equal.

The buildbot sees the same error.

comment:7 Changed 6 years ago by diochnos

Cc: diochnos added

comment:8 Changed 6 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Cc: MarcusCalhoun-Lopez added

comment:9 Changed 6 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

I believe this is a bug in base.
I recently ran into it with PETSc.
There is a pull request that attempts to fix it.

comment:10 Changed 6 years ago by jmroot (Joshua Root)

In b3ca3444e72c01aa4247eca31db91fc17d13154a/macports-base (master):

set FFLAGS not F77FLAGS in configure env

Issue introduced in aa375e5. The environment variable corresponding to
f77 cannot be derived by upper-casing it.

Closes: https://github.com/macports/macports-base/pull/108
See: #57358

comment:11 Changed 6 years ago by jmroot (Joshua Root)

This could be a workaround:

configure.fflags-append {*}${configure.f77_archflags}

comment:12 Changed 6 years ago by dershow

I added that to my local portfile and now it does build. Thank you.

comment:13 Changed 6 years ago by dershow

Was this fixed? I am a little confused unclear about the status. I believe that I locally made the edit above, and then was able to build sundials. But, I just looked at my local port file and it doesn't seem to have that edit. But, sundials is installed fine for me. Was there a change that fixed this and updated it? Should this be closed?

comment:14 Changed 6 years ago by jjstickel (Jonathan Stickel)

Cc: jjstickel added

comment:15 Changed 6 years ago by jjstickel (Jonathan Stickel)

I guess it is fixed in master, but it will not show up via selfupdate until there is another release. The workaround mentioned above worked for me today.

comment:16 Changed 6 years ago by dershow

Do you mean another release of macports or sundials? Does that mean that we need a rev-bump for sundials, or an actual change in the port to match a new sundials release?

comment:17 in reply to:  16 Changed 6 years ago by jjstickel (Jonathan Stickel)

Replying to dershow:

Do you mean another release of macports or sundials? Does that mean that we need a rev-bump for sundials, or an actual change in the port to match a new sundials release?

The next release of macports base, i.e., the port command. It is a bit unusual that something in base fixes a specific port, but apparently that is the situation here.

comment:18 Changed 6 years ago by mf2k (Frank Schima)

Owner: seanfarley deleted

comment:19 Changed 5 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Resolution: fixed
Status: assignedclosed

The fix is now in a released version of MacPorts.

comment:20 in reply to:  11 ; Changed 3 years ago by barracuda156

Replying to jmroot:

This could be a workaround:

configure.fflags-append {*}${configure.f77_archflags}

Should this be added to a port file?

I cannot now build sundials with gcc10, while it was building with gcc7.

comment:21 in reply to:  20 Changed 3 years ago by jjstickel (Jonathan Stickel)

Replying to barracuda156:

Replying to jmroot:

This could be a workaround:

configure.fflags-append {*}${configure.f77_archflags}

Should this be added to a port file?

I cannot now build sundials with gcc10, while it was building with gcc7.

This is an old ticket that was closed 2 years ago. That workaround is reported to be not needed anymore. I suggest you open a new ticket with more details about your situation including relevant error.

Note: See TracTickets for help on using tickets.