RE: libtool support for intel icc compiler

[Himanshu_Khurana]

Hi Robert ,
This compiler can be downloaded from the following link for a 30 day evaluation 
period.

http://www.intel.com/software/products/compilers/clin/eval.htm


Just follow the DOWNLOAD link. You will receive an email from intel with an 
attched file of a license file valid for one month.
COPY this file to /opt/intel/licenses/
and you are ready to use the intel compiler FOR LINUX


You may download this document for the installation isnstructions from this 
link 
http://www.intel.com/software/products/compilers/techtopics/C_Getting_Started_Guide1.htm

"Intel® C++ Compiler 7.0 for Linux* Getting Started Guide
This document explains how to install the Intel® C++ compiler for Linux*, build 
"Hello World" for IA-32 and Intel® Itanium® processor based systems and how to 
get started optimizing your applications with the Intel® compilers."

Thanks and regards
Himanshu Khurana


-----Original Message-----
From: Robert Boehne [mailto:address@hidden
Sent: Tuesday, March 25, 2003 8:10 PM
To: Himanshu_Khurana
Cc: Roberto Bagnara; address@hidden
Subject: Re: libtool support for intel icc compiler


icc users:

Aparently support for icc isn't complete.  Here is where
you can help by submitting a patch that fixes the problems
you're running into.  I don't have access to this compiler,
so if it is something you want, you'll have to volunteer to
do it.  Please read http://www.gnu.org/software/libtool/contribute.html
before you post your patch.

Thanks,

Robert

Himanshu_Khurana wrote:
> 
> Hi all
> I have been struggling with this since quite a while now. This is what I have 
> found. Some changes in libtool.m4 have been made to support Intel 
> compiler.Thes are like
> ..
> ..
> icpc)
>   # Intel C++
>   _LT_AC_TAGVAR(lt_prog_compiler_wl, $1)='-Wl,'
>   _LT_AC_TAGVAR(lt_prog_compiler_pic, $1)='-KPIC'
>   _LT_AC_TAGVAR(lt_prog_compiler_static, $1)='-static'
> ..
> ..
> linux*)
>   case $cc_basename in
>   icc|ecc)
>     _LT_AC_TAGVAR(lt_prog_compiler_wl, $1)='-Wl,'
>     _LT_AC_TAGVAR(lt_prog_compiler_pic, $1)='-KPIC'
>     _LT_AC_TAGVAR(lt_prog_compiler_static, $1)='-static'
>     ;;
> ..
> ..
> 
> WHICH means that libtool must now supoort both icc and icpc . BUT when I am 
> running my configure script by setting the following environment variables
> 
> CC=icc
> CXX=icpc
> LD=ld
> 
> PATH and LD_LIBRARY_PATH accordingly set to find the above
> 
> IT SEEMS that the above mentioned changes in libtool.m4 are never 
> incorporated in my case. Either this is a bug or may be I am making a blunder 
> .Of these two options  latter is a strong possibility  because its just been 
> 10 days since I have started with linux . :-)
> 
> Coming back to the point
> I run
> ./bootstrap             DOESNT COMPLAIN WITH ANY ERRORS
> ./configure --prefix=/home/me/usr    DOESNT COMPLAIN WITH ANY ERRORS
> make                    GIVES THE FOLLOWING ERROR
> 
> ...
> ...
> configure: creating ./config.status
> /bin/sh ./libtool --mode=compile icc -DHAVE_CONFIG_H -I. -I. -I.     -g -c -o 
> lt
> dl.lo `test -f 'ltdl.c' || echo './'`ltdl.c
> mkdir .libs
>  icc -DHAVE_CONFIG_H -I. -I. -I. -g -c ltdl.c  -DPIC -o .libs/ltdl.o
>  icc -DHAVE_CONFIG_H -I. -I. -I. -g -c ltdl.c -o ltdl.o >/dev/null 2>&1
> /bin/sh ./libtool --mode=link icc  -g   -o libltdl.la -rpath 
> /home/himanshu/usr/
> /lib -no-undefined -version-info 4:0:1 ltdl.lo -ldl
> icc -shared  .libs/ltdl.o  -ldl -lc  -soname libltdl.so.3 -o 
> .libs/libltdl.so.3.
> 1.0
> icc: Command line warning: ignoring unknown option '-soname'
> ld: cannot open libltdl.so.3: No such file or directory
> make[2]: *** [libltdl.la] Error 1
> make[2]: Target `all-am' not remade because of errors.
> make[1]: *** [all] Error 2
> make: *** [all-recursive] Error 1
> make: Target `all' not remade because of errors.
> 
> WHEN I SAY
> ls
> 
> I CAN SEE libtool having already been made
> 
> AND WHEN I SAY
> 
> ./libtool --config
> 
> I GET
> 
> ..
> ..
> # Libtool was configured on host blrkecxxx:
> 
> # Shell to use when invoking shell scripts.
> SHELL="/bin/sh"
> 
> # Whether or not to build shared libraries.
> build_libtool_libs=yes
> 
> # Whether or not to build static libraries.
> build_old_libs=yes
> 
> # Whether or not to add -lc for building shared libraries.
> build_libtool_need_lc=yes
> 
> # A C compiler.
> LTCC="icc"
> 
> # A language-specific compiler.
> CC="icc"
> 
> # Is the compiler the GNU C compiler?
> with_gcc=
> # The linker used to build libraries.
> LD="ld"
> 
> # How to pass a linker flag through the compiler.
> wl=""
> 
> # Additional compiler flags for building library objects.
> pic_flag=" -DPIC"
> pic_mode=default
> 
> ..
> ..
> 
> NOW WHAT I THINK IS THAT SINCE LIBTOOL FOR ICC IS NOT BEING TAUGHT HOW TO 
> handle PIC,and linker flag(wl="Wl,") and this is why the make command is  
> failing due to inability of icc to pass -soname option to linker.
> 
> WHICH MEANS that the abovementioned piece of code-patch in libtool.m4 is not 
> being accessed.
> 
> MY QUESTION IS WHY? IS IT A PROBLEM WITH THW WAY I AM DOING THINGS ???????
> LOOKING FOR HELP
> 
> :-)
> Himanshu Khurana
> Software Engineer
> Infosys Technologies,Bangalore,India
> 
> -----Original Message-----
> From: Roberto Bagnara [mailto:address@hidden
> Sent: Tuesday, March 25, 2003 12:40 PM
> To: address@hidden
> Cc: address@hidden; Himanshu_Khurana
> Subject: Re: libtool support for intel icc compiler
> 
> Robert Boehne wrote:
>  > You can always get the latest CVS version of GNU Libtool at:
>  > ftp://alpha.gnu.org/pub/gnu/cvs/libtool.tgz
>  >
>  > It does contain support for icc.
> 
> No, support for icc is broken, the problem has been reported
> to no avail, and the email address of the person who did the
> icc port bounces.  See
> http://mail.gnu.org/archive/html/libtool/2003-03/msg00000.html
> for more information (same problem with the current HEAD).
> Cheers
> 
>      Roberto
> 
> --
> Prof. Roberto Bagnara
> Computer Science Group
> Department of Mathematics, University of Parma, Italy
> http://www.cs.unipr.it/~bagnara/
> mailto:address@hidden