Intel® C++ Compiler
Community support and assistance for creating C++ code that runs on platforms based on Intel® processors.

xilink error under vsNET2002

beaupaisley
Beginner
364 Views
When using icl 9.0 from the vs.NET 2002 environment we get the error.

xilink: error: problem during multi-file optimization compilation (code 1)

This did not occur when running within the vc6 ide. Please advise.

(This is compiled with /Od so there should be no optimizations)

Thanks, Beau Paisley

0 Kudos
3 Replies
TimP
Honored Contributor III
364 Views
This message is usually misleading. Without a quotation of the errors which led up to it, nothing can be said.
0 Kudos
beaupaisley
Beginner
364 Views

Tim, Thank you for the rapid response. I rebuilt with linking as /VERBOSE but it does not to give much more details. The output follows. Also, I have attached the BuildLog file. Thanks, beau

------ Build started: Project: table, Configuration: Debug Win32 ------

table - up-to-date.

Build log was saved at "file://C:OM ableDebugBuildLog.htm"

table - 0 error(s), 0 warning(s)

------ Build started: Project: com, Configuration: Debug Win32 ------

com - up-to-date.

Build log was saved at "file://C:OMcomDebugBuildLog.htm"

com - 0 error(s), 0 warning(s)

------ Build started: Project: dde, Configuration: Debug Win32 ------

dde - up-to-date.

Build log was saved at "file://C:OMddeDebugBuildLog.htm"

dde - 0 error(s), 0 warning(s)

------ Build started: Project: debug, Configuration: Debug Win32 ------

debug - up-to-date.

Build log was saved at "file://C:OMdebugDebugBuildLog.htm"

debug - 0 error(s), 0 warning(s)

------ Build started: Project: dialogs, Configuration: Debug Win32 ------

dialogs - up-to-date.

Build log was saved at "file://C:OMdialogsDebugBuildLog.htm"

dialogs - 0 error(s), 0 warning(s)

------ Build started: Project: editor, Configuration: Debug Win32 ------

editor - up-to-date.

Build log was saved at "file://C:OMeditorDebugBuildLog.htm"

editor - 0 error(s), 0 warning(s)

------ Build started: Project: ex, Configuration: Debug Win32 ------

ex - up-to-date.

Build log was saved at "file://C:OMexDebugBuildLog.htm"

ex - 0 error(s), 0 warning(s)

------ Build started: Project: ext, Configuration: Debug Win32 ------

ext - up-to-date.

Build log was saved at "file://C:OMextDebugBuildLog.htm"

ext - 0 error(s), 0 warning(s)

------ Build started: Project: extNA, Configuration: Debug Win32 ------

extNA - up-to-date.

Build log was saved at "file://C:OMextNADebugBuildLog.htm"

extNA - 0 error(s), 0 warning(s)

------ Build started: Project: extSTATS, Configuration: Debug Win32 ------

extSTATS - up-to-date.

Build log was saved at "file://C:OMextSTATSDebugBuildLog.htm"

extSTATS - 0 error(s), 0 warning(s)

------ Build started: Project: graphics, Configuration: Debug Win32 ------

graphics - up-to-date.

Build log was saved at "file://C:OMgraphicsDebugBuildLog.htm"

graphics - 0 error(s), 0 warning(s)

------ Build started: Project: gui, Configuration: Debug Win32 ------

gui - up-to-date.

Build log was saved at "file://C:OMguiDebugBuildLog.htm"

gui - 0 error(s), 0 warning(s)

------ Build started: Project: ieee, Configuration: Debug Win32 ------

ieee - up-to-date.

Build log was saved at "file://C:OMieeeDebugBuildLog.htm"

ieee - 0 error(s), 0 warning(s)

------ Build started: Project: io, Configuration: Debug Win32 ------

io - up-to-date.

Build log was saved at "file://C:OMioDebugBuildLog.htm"

io - 0 error(s), 0 warning(s)

------ Build started: Project: math, Configuration: Debug Win32 ------

math - up-to-date.

Build log was saved at "file://C:OMmathDebugBuildLog.htm"

math - 0 error(s), 0 warning(s)

------ Build started: Project: mlfun, Configuration: Debug Win32 ------

mlfun - up-to-date.

Build log was saved at "file://C:OMmlfunDebugBuildLog.htm"

mlfun - 0 error(s), 0 warning(s)

------ Build started: Project: omtplink, Configuration: Debug Win32 ------

omtplink - up-to-date.

Build log was saved at "file://C:OMomtplinkDebugBuildLog.htm"

omtplink - 0 error(s), 0 warning(s)

------ Build started: Project: panes, Configuration: Debug Win32 ------

panes - up-to-date.

Build log was saved at "file://C:OMpanesDebugBuildLog.htm"

panes - 0 error(s), 0 warning(s)

------ Build started: Project: str, Configuration: Debug Win32 ------

str - up-to-date.

Build log was saved at "file://C:OMstrDebugBuildLog.htm"

str - 0 error(s), 0 warning(s)

------ Build started: Project: allocate, Configuration: Debug Win32 ------

allocate - up-to-date.

Build log was saved at "file://C:OMallocateDebugBuildLog.htm"

allocate - 0 error(s), 0 warning(s)

------ Build started: Project: om, Configuration: Debug Win32 ------

Linking...(Intel C++ Environment)

Fatal error cannot open "ipps.lib"

xilink: error: problem during multi-file optimization compilation (code 1)

xilink: error: problem during multi-file optimization compilation (code 1)

Build log was saved at "file://C:OMDebugBuildLog.htm"

Om - 2 error(s), 0 warning(s)

---------------------- Done ----------------------

Build: 20 succeeded, 1 failed, 0 skipped

0 Kudos
JenniferJ
Moderator
364 Views
"xilink: error: problem during multi-file ...." doesn't mean much here. If you resolve the other error "Fatal error cannot open "ipps.lib"", my guess is this one will go away. (you just need to add the lib directory of "ipps.lib" to your link property.)
xilink calls link.exe to do some work. If link.exe returns error, xilink will display an error, but xilink doesn't the detail of the error from "link.exe".
But xilink should only display the error once.
Jennifer
0 Kudos
Reply