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

IPO problems

Ivan_V_
Beginner
376 Views

-------------- Build: Debug Win32 in Engine ---------------

xilink.exe /nologo /subsystem:windows /LIBPATH:"C:\Program Files (x86)\Intel\Compiler\C++\10.1.025\EM64T\Lib" /LIBPATH:"C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\lib\amd64" /LIBPATH:I:\SDKWINDOWS6.1\Lib\x64 /LIBPATH:H:\DirectXSDK-August2008\Lib\x64 /out:Debug\C4.exe "C:\Program Files\Intel\MKL\10.0.5.025\em64t\lib\mkl_em64t.lib" "C:\Program Files (x86)\Intel\Compiler\C++\10.1.025\EM64T\Lib\libmmdd.lib" "C:\Program Files\Intel\MKL\10.0.5.025\em64t\lib\mkl_core.lib" "C:\Program Files\Intel\MKL\10.0.5.025\em64t\lib\mkl_sequential.lib" "C:\Program Files\Intel\MKL\10.0.5.025\em64t\lib\mkl_cdft.lib" "C:\Program Files (x86)\Intel\Compiler\C++\10.1.025\EM64T\Lib\libguide.lib" "C:\Program Files\Intel\MKL\10.0.5.025\em64t\lib\libguide.lib" advapi32.lib gdi32.lib kernel32.lib ole32.lib opengl32.lib user32.lib uuid.lib ws2_32.lib winmm.lib powrprof.lib dinput8.lib dsound.lib dxguid.lib xinput.lib "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\lib\amd64\msvcrtd.lib" Debug\EngineCode\C4Animation.obj Debug\EngineCode\C4Application.obj Debug\EngineCode\C4Attributes.obj Debug\EngineCode\C4AudioCapture.obj Debug\EngineCode\C4Base.obj Debug\EngineCode\C4Bounding.obj Debug\EngineCode\C4CameraObjects.obj Debug\EngineCode\C4Cameras.obj Debug\EngineCode\C4Character.obj Debug\EngineCode\C4Cloth.obj Debug\EngineCode\C4Collision.obj Debug\EngineCode\C4ColorPicker.obj Debug\EngineCode\C4ColorRGBA.obj Debug\EngineCode\C4Configurable.obj Debug\EngineCode\C4Configuration.obj Debug\EngineCode\C4Constants.obj Debug\EngineCode\C4Controller.obj Debug\EngineCode\C4Dialog.obj Debug\EngineCode\C4Display.obj Debug\EngineCode\C4Effects.obj Debug\EngineCode\C4Emitters.obj Debug\EngineCode\C4Engine.obj Debug\EngineCode\C4Expressions.obj Debug\EngineCode\C4FilePicker.obj Debug\EngineCode\C4Files.obj Debug\EngineCode\C4Fluid.obj Debug\EngineCode\C4Fonts.obj Debug\EngineCode\C4FragmentPrograms.obj Debug\EngineCode\C4Geometries.obj Debug\EngineCode\C4GeometryLevel.obj Debug\EngineCode\C4GeometryObjects.obj Debug\EngineCode\C4Graph.obj Debug\EngineCode\C4Graphics.obj Debug\EngineCode\C4Hash.obj Debug\EngineCode\C4Image.obj Debug\EngineCode\C4Input.obj Debug\EngineCode\C4Interface.obj Debug\EngineCode\C4LightObjects.obj Debug\EngineCode\C4Lights.obj Debug\EngineCode\C4List.obj Debug\EngineCode\C4Main.obj Debug\EngineCode\C4Manipulator.obj Debug\EngineCode\C4Map.obj Debug\EngineCode\C4Markers.obj Debug\EngineCode\C4MaterialObjects.obj Debug\EngineCode\C4Math.obj Debug\EngineCode\C4Matrix3D.obj Debug\EngineCode\C4Matrix4D.obj Debug\EngineCode\C4Memory.obj Debug\EngineCode\C4Messages.obj Debug\EngineCode\C4Models.obj Debug\EngineCode\C4Mutators.obj Debug\EngineCode\C4Network.obj Debug\EngineCode\C4Node.obj Debug\EngineCode\C4Objects.obj Debug\EngineCode\C4OpenGL.obj Debug\EngineCode\C4Packing.obj Debug\EngineCode\C4Panels.obj Debug\EngineCode\C4Particles.obj Debug\EngineCode\C4Paths.obj Debug\EngineCode\C4Plugins.obj Debug\EngineCode\C4Portals.obj Debug\EngineCode\C4Primitives.obj Debug\EngineCode\C4Programs.obj Debug\EngineCode\C4Projectile.obj Debug\EngineCode\C4Properties.obj Debug\EngineCode\C4Quaternion.obj Debug\EngineCode\C4Random.obj Debug\EngineCode\C4Regions.obj Debug\EngineCode\C4Render.obj Debug\EngineCode\C4Renderable.obj Debug\EngineCode\C4Resources.obj Debug\EngineCode\C4Scripts.obj Debug\EngineCode\C4ShaderTextures.obj Debug\EngineCode\C4Shadows.obj Debug\EngineCode\C4Skybox.obj Debug\EngineCode\C4Sound.obj Debug\EngineCode\C4Sources.obj Debug\EngineCode\C4SpaceObjects.obj Debug\EngineCode\C4Spaces.obj Debug\EngineCode\C4String.obj Debug\EngineCode\C4StringTable.obj Debug\EngineCode\C4Terrain.obj Debug\EngineCode\C4Textures.obj Debug\EngineCode\C4Threads.obj Debug\EngineCode\C4Time.obj Debug\EngineCode\C4ToolWindows.obj Debug\EngineCode\C4Topology.obj Debug\EngineCode\C4Trees.obj Debug\EngineCode\C4Triggers.obj Debug\EngineCode\C4Types.obj Debug\EngineCode\C4Values.obj Debug\EngineCode\C4Vector2D.obj Debug\EngineCode\C4Vector3D.obj Debug\EngineCode\C4Vector4D.obj Debug\EngineCode\C4VertexPrograms.obj Debug\EngineCode\C4Viewports.obj Debug\EngineCode\C4World.obj Debug\EngineCode\C4Zones.obj Debug\EngineCode\C4ResWindows.res /NODEFAULTLIB:LIBCMT.lib /pdb:.pdb -qipo_fas

(0): internal error: 101004_3

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

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

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

0 Kudos
1 Solution
TimP
Honored Contributor III
376 Views

If you are making a 32-bit build, it's no use specifying libraries from the 64-bit compiwler and MKL. As you have specified mkl_sequential, it may not matter that you have specified both a 64-bit MKL libguide and a 64-bit C++ libguide, which would be a problem if one were needed and the two were not identical. I don't think it's clear what your reason for rejecting the non-debug threaded libc might be. I would have expected some error messages prior to those you quote, which of course are more likely to be meaningful.

View solution in original post

0 Kudos
2 Replies
TimP
Honored Contributor III
377 Views

If you are making a 32-bit build, it's no use specifying libraries from the 64-bit compiwler and MKL. As you have specified mkl_sequential, it may not matter that you have specified both a 64-bit MKL libguide and a 64-bit C++ libguide, which would be a problem if one were needed and the two were not identical. I don't think it's clear what your reason for rejecting the non-debug threaded libc might be. I would have expected some error messages prior to those you quote, which of course are more likely to be meaningful.

0 Kudos
Ivan_V_
Beginner
376 Views
Quoting - tim18

If you are making a 32-bit build, it's no use specifying libraries from the 64-bit compiwler and MKL. As you have specified mkl_sequential, it may not matter that you have specified both a 64-bit MKL libguide and a 64-bit C++ libguide, which would be a problem if one were needed and the two were not identical. I don't think it's clear what your reason for rejecting the non-debug threaded libc might be. I would have expected some error messages prior to those you quote, which of course are more likely to be meaningful.

I think I found the error.

There are some objects missing in linking.

I had disable the warnings because allthem in compilationrefered to multibyte character.

The link shows the lack of objects asawarning. Ilinked withthe 2missinglibs .

There were problems of instability under comand line construction, but thelink finished Ok.

The programm executed.

Thanks for your help.

0 Kudos
Reply