I upgraded my macbook to Sonoma 14.0 then my iFort won't work!

ifort test.f90 -o test

-macosx_version_min has been renamed to -macos_version_min

ld: warning: -keep_dwarf_unwind is obsolete

ld: warning: ignoring duplicate libraries: '/opt/intel/compilers_and_libraries_2020.4.301/mac/compiler/lib/libsvml.a'

ld: warning: no platform load command found in '/opt/intel/compilers_and_libraries_2020.4.301/mac/compiler/lib/for_main.o', assuming: macOS

ld: warning: no platform load command found in '/private/var/folders/x1/vb5f70dd38916dhr2_7cx0bm0000gn/T/iforte8fstn.o', assuming: macOS

ld: warning: no platform load command found in '/opt/intel/compilers_and_libraries_2020.4.301/mac/compiler/lib/libifcoremt.a[2](cvt__globals.o)', assuming: macOS

ld: warning: no platform load command found in '/opt/intel/compilers_and_libraries_2020.4.301/mac/compiler/lib/libifcoremt.a[3](cvt_int_to_text.o)', assuming: macOS...


MacBook Pro 13″, macOS 10.15

Posted on Oct 3, 2023 12:06 PM

Reply
Question marked as Top-ranking reply

Posted on Oct 3, 2023 12:54 PM

Upgrade to the most current Intel Fortran Classic version, and try again.


If you are running the current 2023.2.1 Build, Contact Intel Support for assistance with Intel Fortran.


The system requirements don’t list macOS 14 Sonoma as supported:


https://www.intel.com/content/www/us/en/developer/articles/system-requirements/oneapi-fortran-compiler-system-requirements.html


Per Intel, you’re seemingly also headed for some sort of migration:


macOS support is deprecated for Intel® Fortran Compiler Classic (ifort) in the oneAPI 2023.1 release. macOS support for Intel® Fortran Compiler Classic (ifort) will not be available starting with the oneAPI 2024.0 release.


Intel oneAPI Base Toolkit for macOS on x86 is now deprecated and will be discontinued in the 2024.0 release. Several Intel-led open source developer tool projects will continue supporting macOS on Apple Silicon including oneAPI Threading Building Blocks (oneTBB) and Intel® Implicit SPMD Program Compiler and we welcome the opportunity to work with contributors to expand support to additional tools in the future.


Intel oneAPI HPC Toolkit for macOS on x86 is now deprecated and will be discontinued in the 2024.0 release. Several Intel-led open source developer tool projects will continue supporting macOS on Apple Silicon including oneAPI Threading Building Blocks (oneTBB) and Intel® Implicit SPMD Program Compiler and we welcome the opportunity to work with contributors to expand support to additional tools in the future.



As an alternative to Intel Fortran, I’ve successfully used gfortran for some work, though not recently:


https://github.com/fxcoudert/gfortran-for-macOS/releases


Syntax details and extensions can differ.

Similar questions

16 replies
Question marked as Top-ranking reply

Oct 3, 2023 12:54 PM in response to DY2011

Upgrade to the most current Intel Fortran Classic version, and try again.


If you are running the current 2023.2.1 Build, Contact Intel Support for assistance with Intel Fortran.


The system requirements don’t list macOS 14 Sonoma as supported:


https://www.intel.com/content/www/us/en/developer/articles/system-requirements/oneapi-fortran-compiler-system-requirements.html


Per Intel, you’re seemingly also headed for some sort of migration:


macOS support is deprecated for Intel® Fortran Compiler Classic (ifort) in the oneAPI 2023.1 release. macOS support for Intel® Fortran Compiler Classic (ifort) will not be available starting with the oneAPI 2024.0 release.


Intel oneAPI Base Toolkit for macOS on x86 is now deprecated and will be discontinued in the 2024.0 release. Several Intel-led open source developer tool projects will continue supporting macOS on Apple Silicon including oneAPI Threading Building Blocks (oneTBB) and Intel® Implicit SPMD Program Compiler and we welcome the opportunity to work with contributors to expand support to additional tools in the future.


Intel oneAPI HPC Toolkit for macOS on x86 is now deprecated and will be discontinued in the 2024.0 release. Several Intel-led open source developer tool projects will continue supporting macOS on Apple Silicon including oneAPI Threading Building Blocks (oneTBB) and Intel® Implicit SPMD Program Compiler and we welcome the opportunity to work with contributors to expand support to additional tools in the future.



As an alternative to Intel Fortran, I’ve successfully used gfortran for some work, though not recently:


https://github.com/fxcoudert/gfortran-for-macOS/releases


Syntax details and extensions can differ.

Oct 10, 2023 3:13 PM in response to tz0616

Okay, part of that looks to be a known bug:

https://www.mail-archive.com/gcc-bugs@gcc.gnu.org/msg785716.html


Looks like the developer with that switch change might have been at Apple too, not at gcc/gfortran.


The other error looks to be Homebrew, based on this:

https://github.com/orgs/Homebrew/discussions/4794#discussioncomment-7117550


A workaround for Xcode 15 looks to be adding the following switches:

-Wl,-ld_classic

Oct 10, 2023 8:37 AM in response to tz0616

Check whatever build script is being used for building that code, and fix the two switches shown.


1: Some gcc/gfortran developer decided to change that switch name without just leaving the old name as a synonym. Some developer decided to change a switch name and emit a diagnostic for the old switch that does the same thing, rather than silently just doing what was expected. That switch will have to be changed to suppress that message.


2: It appears there are two references in the linked objects to the same library in the gfortran command. Basically, a duplicate library reference. That is usually an explicit reference on the compile command, or can be hidden in an alias for the compiler command, or can be loaded from somewhere during the compile, depending on the arcaneness rating of the build script. Anything using autoconf tends to be somewhere out past arcane, too. Look underneath whatever that gfnew script or alias might be.


As I'm guessing this probably isn't your Fortran code and your build script (gfnew?), check for source and build updates from whoever is maintaining it, and check for build switches that might be used for selecting a particular compiler.


Welcome to porting Fortran and its build scripts around.


Fortran itself has a few gnarly bits, particularly if the code is old enough. FORTRAN code (FORTRAN code, as differentiated from Fortran code) using syntax from prior to about F90 tends to be gnarly. Code with vendor extensions, too. And some build scripts and some build script tooling... shudder.

Oct 9, 2023 3:44 PM in response to tz0616

The gfortran version I'm running is now very old, and was mildly annoying to get it to build and work.


If I was re-starting the local Fortran development work on macOS—that work is happening else-platform—I'd start with the pre-built version I've previously linked: https://github.com/fxcoudert/gfortran-for-macOS/releases


If that fails, I'd next look at Flang (though that's very new, is "not ready yet for production usage", and is not something I've used as yet): https://github.com/llvm/llvm-project/tree/main/flang


Installing gfortran via Homebrew would be the next stop. gcc is, however, enormous and complex and fiddly.*



*Clang, Flang, and LLVM are also enormous, complex, and fiddly.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

I upgraded my macbook to Sonoma 14.0 then my iFort won't work!

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.