- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
On linking to produce a dynamic library using FORTRAN 9.1 for the Intel MAC (using XCode), I receive the following errors:
IPO link: can not find "10.4"
ifort: error: problem during multi-file optimization compilation (code 1)
I have no idea what this means, nor do I know how to disable this type of optimization within XCode.
Thank you
Scott Frasier
The verbose linking command is listed below:
Checking Dependencies
Ld /Users/scott/Documents/ATK/NuCS/SIGDAT/build/Debug/libSIGDATLIB.dylib normal i386
cd /Users/scott/Documents/ATK/NuCS/SIGDAT
setenv MACOSX_DEPLOYMENT_TARGET 10.4
setenv NEXT_ROOT /Developer/SDKs/MacOSX10.4u.sdk
/usr/bin/ifort-9.1 -o /Users/scott/Documents/ATK/NuCS/SIGDAT/build/Debug/libSIGDATLIB.dylib -L/Users/scott/Documents/ATK/NuCS/SIGDAT/build/Debug -L/Users/scott/Documents/ATK/NuCS/SIGDAT/build/Debug -L/Developer/SDKs/MacOSX10.4u.sdk/usr/lib/gcc/darwin/default -F/Users/scott/Documents/ATK/NuCS/SIGDAT/build/Debug -filelist /Users/scott/Documents/ATK/NuCS/SIGDAT/build/SIGDAT.build/Debug/SIGDATLIB.build/Objects-normal/i386/SIGDATLIB.LinkFileList -arch i386 -Wl,-single_module -compatibility_version 1 -current_version 1 -install_name /usr/local/lib/libSIGDATLIB.dylib -dynamiclib -mmacosx-version-min=10.4 -Wl,-syslibroot,/Developer/SDKs/MacOSX10.4u.sdk
ifort: Command line warning: ignoring option '-c'; no argument required
ifort: Command line warning: ignoring option '-c'; no argument required
IPO link: can not find "10.4"
ifort: error: problem during multi-file optimization compilation (code 1)
IPO link: can not find "10.4"
ifort: error: problem during multi-file optimization compilation (code 1)
I have no idea what this means, nor do I know how to disable this type of optimization within XCode.
Thank you
Scott Frasier
The verbose linking command is listed below:
Checking Dependencies
Ld /Users/scott/Documents/ATK/NuCS/SIGDAT/build/Debug/libSIGDATLIB.dylib normal i386
cd /Users/scott/Documents/ATK/NuCS/SIGDAT
setenv MACOSX_DEPLOYMENT_TARGET 10.4
setenv NEXT_ROOT /Developer/SDKs/MacOSX10.4u.sdk
/usr/bin/ifort-9.1 -o /Users/scott/Documents/ATK/NuCS/SIGDAT/build/Debug/libSIGDATLIB.dylib -L/Users/scott/Documents/ATK/NuCS/SIGDAT/build/Debug -L/Users/scott/Documents/ATK/NuCS/SIGDAT/build/Debug -L/Developer/SDKs/MacOSX10.4u.sdk/usr/lib/gcc/darwin/default -F/Users/scott/Documents/ATK/NuCS/SIGDAT/build/Debug -filelist /Users/scott/Documents/ATK/NuCS/SIGDAT/build/SIGDAT.build/Debug/SIGDATLIB.build/Objects-normal/i386/SIGDATLIB.LinkFileList -arch i386 -Wl,-single_module -compatibility_version 1 -current_version 1 -install_name /usr/local/lib/libSIGDATLIB.dylib -dynamiclib -mmacosx-version-min=10.4 -Wl,-syslibroot,/Developer/SDKs/MacOSX10.4u.sdk
ifort: Command line warning: ignoring option '-c'; no argument required
ifort: Command line warning: ignoring option '-c'; no argument required
IPO link: can not find "10.4"
ifort: error: problem during multi-file optimization compilation (code 1)
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looks like your macosxversion flag isn't recognized by ifort. Likewise, -compatibility and -current aren't understood. Relatively few special gcc style flags will be recognized. Intel 9.x compilers have an annoying trait of reporting almost anything extraneous which makes it to the linker script as an ipo problem. ipo isn't enabled unless you set it explicitly or via -fast when performing the original compilation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Our compiler driver expert tells me that -compatibility_version and -current_version aren't accepted by the ifort you have, though they will in an update. If these are preceded by -WI, they'll be passed to the linker verbatim.
However, there seems to be another problem that may be a bug in the driver. Would you please file an Intel Premier Support request on this, and include the actual ifort command you used as well as the output? Please ask that it be assigned to Steve Lionel. Thanks.
However, there seems to be another problem that may be a bug in the driver. Would you please file an Intel Premier Support request on this, and include the actual ifort command you used as well as the output? Please ask that it be assigned to Steve Lionel. Thanks.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page