ipo: warning #11010 file format not recognized for ... .o

[staralfur]

Dear ForumReaders,

I just recently installed a new ubuntu 8.10 version on my mac via parallels and I am running into problems after installing ifort 11.074 on ubuntu. I did the same install of ubuntu 8.10 and ifort a month ago on another computer, and my code ran smoothly after that install. This time, when running the same exact code, I get an 'ipo: warning #11010 file format not recognized for ... .o, possible linker script'. From reading the various posts on this forum, I think my error has something to do with the libraries and/or paths. I am not very familiar with either Fortran-compiling nor Linux, and therefore I did not see from the previous posts how I can check whether all my links and libraries are in the right place, if that is even the problem with my current install.

So here are my system specs:

(uname -a ) Linux staralfur-laptop: 2.6.27-11-generic #1 SMP ... UTC 2009 i686 GNU/Linux

(ls /lib/libc*) /lib/libc-2.8.90.so, /lib/libcap.so.2.10, /lib/libcom_err.so.2.1, lib/libcap.so.1, lib/libcidn-2.8.90.so, lib/libcrypt-2.8.90.so, /lib/libcap.so.1.10, /lib/libcidn.so.1 /lib/libcrypts.so.1 /lib/libcap.so.2 /lib/libcom_err.so.2, lib/libc.so.6

I hope that someone on this forum can help me out. Also I would like to ask that when you reply, to be very specific on how and where I should type certain commands in my terminal, because I am really a beginner in linux.

Thanks in advance!

[TimP]

You haven't said what you are trying to do, or what you did to get the error report, so I can't see how to answer with what to type.
The .o files created by Intel ipo tools, as the message said, aren't recognized by any tools provided in linux. ifort and tools which it supplies, such as xild and xiar, are needed to work with ipo files. If you want to use linux tools on the .o files, you must avoid ipo.

[static_override]

Quoting - tim18

You haven't said what you are trying to do, or what you did to get the error report, so I can't see how to answer with what to type.
The .o files created by Intel ipo tools, as the message said, aren't recognized by any tools provided in linux. ifort and tools which it supplies, such as xild and xiar, are needed to work with ipo files. If you want to use linux tools on the .o files, you must avoid ipo.

i had the same problem...

I installed the suite of compilers for you to c++ and fortran in version free for linux.

The compiler for c++ seems to work well. Some programs and compiled the dependencies handled very well.
However, the programs in fortran don't compile in any way. Every time I got the same error:

ipo: warning #11010: file format not recognized for testa.f95, possible linker script
ld:testa.f95: file format not recognized; treating as linker script
ld:testa.f95:1: syntax error


The program is a simple "Hello world" and compile fine with gfortran, g95. The version of linux is Ubuntu 8.04 (
supposedly recommended):

Linux winx-laptop 2.6.24-23-generic #1 SMP Mon Jan 26 00:13:11 UTC 2009 i686 GNU/Linux

what to do?

thanks...

[TimP]

ipo messages are a catch-all for problems earlier on, Don't even set options which imply -ipo until you get other issues straight; then you will know if you get ipo error that it's not ipo.
Here are some possibilities, some of which you could have ruled out by showing us what you did:
as .f95 isn't recognized as meaning anything by ifort or icc, you might want to rename it as .f90 (if it's free form source) and try ifort testa.f90. Those other compilers don't use .f95 to set language standard level either, as far as I know.

[static_override]

Quoting - tim18

ipo messages are a catch-all for problems earlier on, Don't even set options which imply -ipo until you get other issues straight; then you will know if you get ipo error that it's not ipo.
Here are some possibilities, some of which you could have ruled out by showing us what you did:
as .f95 isn't recognized as meaning anything by ifort or icc, you might want to rename it as .f90 (if it's free form source) and try ifort testa.f90. Those other compilers don't use .f95 to set language standard level either, as far as I know.

worked!

when I rename the source to. f90 the ifort compiled normally!

however, a question arises. If I use resources in fortran 2003, I use the same .f90 extension?

thank you very much!

[Ron_Green]

Quoting - static_override

worked!

when I rename the source to. f90 the ifort compiled normally!

however, a question arises. If I use resources in fortran 2003, I use the same .f90 extension?

thank you very much!

Yes, .f90 implies free format source form - nothing more, nothing less. The file extension has nothing to do with the language standard to which you write your code.

[staralfur]

Quoting - tim18

You haven't said what you are trying to do, or what you did to get the error report, so I can't see how to answer with what to type.
The .o files created by Intel ipo tools, as the message said, aren't recognized by any tools provided in linux. ifort and tools which it supplies, such as xild and xiar, are needed to work with ipo files. If you want to use linux tools on the .o files, you must avoid ipo.

Thanks for your quick reply.

I have indeed not very clearly stated what my program is supposed to do. This is because this program was working earlier on an identical ifort11/unbuntu8.10 platform without any problems. So the program in itself should not be the problem, but the linking with the libraries on this new install might be. So in short, this program I have has a makefile that compiles about 20 different fortran files. (the compilation works well), but then when it comes to linking everything together into an executable program named 'coch', the earlier named error shows up.

So i can give you an example of how the makefile looks like if that helps:

OBJS = AllocationError.o ClosePressureEarCanal.o CloseProbing.o cochlea.o #etc for all the other o.files

#.o:

# $(CC) $(OFLAGS)

CC = /opt/intel/Compiler/11.0/074/bin/ia32/ifort

OFLAGS = -c

EFLAGS = -o

#now come the rules

coch: $(OBJS)

$(CC) $(EFLAGS) coch $(OBJS)

cochlea.o: Declare.f90 filesmodule.mod cochlea.f90 wavereadmodule.mod

$(CC) $(OFLAGS) cochlea.f90

#here follow about 20 or so of these same statements

wavereadmodule.mod: WaveReadModule.o WaveReadModule.f90

$(CC) $(OFLAGS) WaveReadModule.f90

%.o: %.f90

$(CC) $(OFLAGS) $<

#clean rule. Remove all object files, backup files AND the executable

clean:

rm *.o *.mod *~ coch

#eof

I hope this helps and that you have fresh ideas of how to help. I have to say that I did not make this program myself, but it was given to me in a working form and I installed it earlier on this other computer without any problems.

Thanks!

[staralfur]

Dear Forum,

I have solved my problem. The earlier post pointed me into the direction of checking whether my Fortran files were readable for the compiler. As I mentioned earlier, I installed this Ubuntu 8.10 version under as a virtual machine on my mac. This also means that the folder where my .f90 files are into are shared between the mac and ubuntu. Somehow the connection to mac made the files unreadable for the compiler in Linux. So i have copied the a fresh version of my folder into Ubuntu without having it shared with the mac and this seems to have solved the problem. It is weird that this happened, but it works now..

Thanks for your help!

Regards,

Sarah