Very good point!! Indeed after taking a second look at your config.log, it
does seem as if this variable is not set. In LAM, we use C++ only for the
top level executables (laminfo, mpicc, etc). The libraries are written
completely in C (other than the C++ bindings). So, if you really want the
compilation with intel suite, then you should be setting the environment
variable CC to icc.
Hope this helps,
Anju.
On Thu, 17 Jun 2004, Richard Hadsell wrote:
> Raphael Gaspar Lullis wrote:
>
> >Hi,
> >I trying to compile lam-7.0.6 with the latest intel compilers. To do so,
> >I set the env variables as directed, but still get configure errors.
> >
> >I don't have any idea what happens with configure, so I sending
> >config.log attached. The only thing that I noticed is that icc is not
> >running when invoked by a regular user, but that's due to a misplaced
> >license file.
> >
> >Hope someone can help me,
> >Raphael
> >
> >
> From your config.log it seems that you have not set CC to icc. It is
> using gcc for the C compiler and icc for the C++ compiler.
>
> Also, in your environment set LDFLAGS and CXXLDFLAGS to
> -Wl,-rpath,/xxx/intel/compiler80/ia32/lib (fill in the xxx with wherever
> your Intel compiler is installed, so this flag points to the runtime
> libraries. With icc 7.x, the compiler would include the right rpath in
> binaries that it built, but icc 8.0 leaves it to you to get it right
> (either through the rpath or through LD_LIBRARY_PATH at run time).
>
> A lot of the errors you may be able to ignore. I see many of the same,
> but the resulting configuration still works.
>
> --
> Dick Hadsell 914-259-6320 Fax: 914-259-6499
> Reply-to: hadsell_at_[hidden]
> Blue Sky Studios http://www.blueskystudios.com
> 44 South Broadway, White Plains, NY 10601
>
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
|
