- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
may be I am ahead of time but I am curious. Did somebody successfully try the Intel Fortran Compiler 11.1 on the new Fedora 13?
I have to update my rather old Fedora system and wonder if I can skip a couple of releases.
Best regards,
Lothar
may be I am ahead of time but I am curious. Did somebody successfully try the Intel Fortran Compiler 11.1 on the new Fedora 13?
I have to update my rather old Fedora system and wonder if I can skip a couple of releases.
Best regards,
Lothar
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
FC12 x86_64 has been tried successfully by several of us. I don't know about 13. Ron's Fedora installation hints at the top of the forum should be sufficient, even though this is several steps ahead of what 11.1 supported fully. Basically, a running g++, and the 32- and 64-bit libstdc++-33, are needed, as mentioned previously on this forum.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the quick response.
I took a leap of faith and gave it a try. Short summary for l_cprof_p_11.1.072_intel64 on Fedora 13, x86_64
In principle the compiler (ifort) works following the Fedora 11/12 instructions by Ron. However the linker
complains:
ld: cannot find -lm
If the static library glibc-static.x86_64 is installed the linking succeeds and the code actually runs.
There are however three warnings:
ipo: warning #11020: unresolved __rela_iplt_end
Referenced in libc.a(elf-init.o)
ipo: warning #11020: unresolved __rela_iplt_start
Referenced in libc.a(elf-init.o)
ipo: remark #11000: performing multi-file optimizations
ipo: remark #11005: generating object file /tmp/ipo_f900qYjxN.o
/usr/lib/gcc/x86_64-redhat-linux/4.4.4/../../../../lib64/libpthread.a(libpthread.o): In function `sem_open':
(.text+0x75ad): warning: the use of `mktemp' is dangerous, better use `mkstemp'
I guess I don't access those functions otherwise my code should not run!?
Would be nice to get rid of the warnings. ;-)
Am I missing a package?
Best regards,
Lothar
I took a leap of faith and gave it a try. Short summary for l_cprof_p_11.1.072_intel64 on Fedora 13, x86_64
In principle the compiler (ifort) works following the Fedora 11/12 instructions by Ron. However the linker
complains:
ld: cannot find -lm
If the static library glibc-static.x86_64 is installed the linking succeeds and the code actually runs.
There are however three warnings:
ipo: warning #11020: unresolved __rela_iplt_end
Referenced in libc.a(elf-init.o)
ipo: warning #11020: unresolved __rela_iplt_start
Referenced in libc.a(elf-init.o)
ipo: remark #11000: performing multi-file optimizations
ipo: remark #11005: generating object file /tmp/ipo_f900qYjxN.o
/usr/lib/gcc/x86_64-redhat-linux/4.4.4/../../../../lib64/libpthread.a(libpthread.o): In function `sem_open':
(.text+0x75ad): warning: the use of `mktemp' is dangerous, better use `mkstemp'
I guess I don't access those functions otherwise my code should not run!?
Would be nice to get rid of the warnings. ;-)
Am I missing a package?
Best regards,
Lothar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ipo certainly is one of the first things which might run into difficulty on an unsupported installation. You didn't say what options you set; possibly -fast which invokes -ipo and wants the static math library.
Linker warning about mktemp is normal; it's built into gnu ld and has nothing to do with your use of Intel compiler.
You might need an expert on FC to interpret why an FC library, if it really is meant for your FC13, might have unresolved references. If you install by yum or rpm, one would think it would know about dependencies.
Linker warning about mktemp is normal; it's built into gnu ld and has nothing to do with your use of Intel compiler.
You might need an expert on FC to interpret why an FC library, if it really is meant for your FC13, might have unresolved references. If you install by yum or rpm, one would think it would know about dependencies.

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