xilib question

[michael_m2]

Hello:

I have a static library I'm trying to build. (I'm using "build solution"from the IDE, not the command line.) After all the files in the library are compiled, it needs to create the library. It seems that it uses xilib, which then calls lib.exe.

Does xilib try to create some temporary files which itsubsequently deletes (e.g. fileName.obj will cause the creation of fileName_ipo.obj)? Is there any way to control where the file gets created?

Thanks.

[Steven_L_Intel1]

I think it creates them in the temp directory (TEMP environment variable.) There's no other control over this as far as I know. The compiler driver also creates files there. What's the problem?

[michael_m2]

Now thatmy ability to post to the forum has been restored, I'd like to continue this thread for 2 reasons. Firstly, it may be helpful to anybody else searching for answers. Secondly, my supportfrom Premier Support (Issue #401761) seems to have stalled, so I'm hopeful that somebody else here may have encountered similar problems and may know of a work-around.

The problem is that I have a user who has a solution with a project in it, where the project is stored on a server that he has read-only permission to. (He is running version 8.1 of the compiler.) The build is failing with an error message from xilib saying that it can't open StochParamsMod_ipo.obj for writing. This file is a temporary file that xilib is attempting to create. Theoretically, it should be created in the user's TMP directory.

Firstly,I'm unclear why xilib is trying to create this file, since the library is not compiled with the /Qipo option.

Secondly, I'm not sure why it can't create this file since the user has full control over his TMP directory. In experimenting, I temporarily gavethe user full control over the directory on the server where the project file exists, and then library was created successsfully. So this makes me think that, for some reason, xilib (in this one user's setup) is trying to createits temporary files in the directory where the project is stored instead of in the TMP directory.

Has anybody else observed behavior like this? Any workarounds?

Since I'm not compiling with /Qipo, is there any way to get the compiler to skip the xilib step altogether, and just call LIB directly? (Note: We're compiling using the IDE, not from the command line.)

Thanks for any suggestions.

Michael

[Steven_L_Intel1]

It's very odd that xilib would be creating an .obj file if /Qipo was not used. I'll have to do some experiments about that.

The only workaround I can think of is to go to the Intel Fortran IA32BIN folder, rename xilib.exe to xilib-old.exe, and then copy in link.exe (yes, I said link) from the MSVS VCBIN folder and call it xilib.exe. This also works for xilink.exe.

I'll take a look at your issue and see if I can get it moving.

[michael_m2]

Thanks for your push to "get it moving". I thought I should post what happened for the benefit of others.

It looks like it was a bug with the xilib/xilink utilities in the 8.1 version of the compiler. We tried using 9.0 (9.0.030 to be exact), and things worked better, but there was still a problem. The user just upgraded to the latest version, 9.1.032, and things seem to work fine.

Michael