Re: ifort bug

From: Dr Chaos (mbkennelSPAMBEGONE_at_NOSPAMyahoo.com)
Date: 03/18/04 

Date: Thu, 18 Mar 2004 21:00:12 +0000 (UTC)

Rich Townsend <rhdt@barVOIDtol.udel.edu> wrote:
> If it is an LD_LIBRARY_PATH problem -- where the executable is being dynamically
> linked to different libraries when you are using different accounts -- then the
> way to track it down is ldd. This useful proggy, which is a standard UN*X tool,
> shows which libraries will be linked against at runtime. For example:
>
> rhdt@cmell boojum_lite $ ldd boojum_lite
> linux-gate.so.1 => (0xffffe000)
> libg2c.so.0 => /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/libg2c.so.0 (0x4001f000)
> libm.so.6 => /lib/libm.so.6 (0x4003c000)
> libcxa.so.5 => /opt/intel/intel_fc_80/lib/libcxa.so.5 (0x4005d000)
> libunwind.so.5 => /opt/intel/intel_fc_80/lib/libunwind.so.5 (0x40083000)
> libpthread.so.0 => /lib/libpthread.so.0 (0x40089000)
> libc.so.6 => /lib/libc.so.6 (0x400d9000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

Oooh, I hated that libcxa stuff.

There's an obscure option, finally documented long after it was there,

   -static-libcxa

I generally want my programs to link only to standard distribution
libraries, and not Fortran specific libs, as much as possible.

Easier to move the binary.

Relevant Pages

  • Re: C89, size_t, and long
    ... libraries which have useful stuff). ... So because others here can't think of a good reason to use long instead of size_t and you can't prove there is never such a reason, we must all assume there could be a good reason to not use the mechanisms provided by the standard to deal with a problem? ... If you are claiming there is a reason to avoid the mechanisms the standard provides to allow portability then it is up to *you* to prove your point, not up to others to disprove it. ... but you can hardly blame the consequences on the Standard headers. ...
    (comp.lang.c)
  • Re: C89, size_t, and long
    ... libraries which have useful stuff). ... So because others here can't think of a good reason to use long instead of size_t and you can't prove there is never such a reason, we must all assume there could be a good reason to not use the mechanisms provided by the standard to deal with a problem? ... want to have standard headers included in their own headers which ...
    (comp.lang.c)
  • Re: comparing doubles for equality
    ... AFAIK there is no ANSI/ISO standard for it. ... Fortran 95 seem to have some built-in operators but it's not clear ... LIA,GIA,ICE libraries for interval methods in C++ from Delisoft ... Actually I've been for quite some months proposing getting together ...
    (comp.programming)
  • Re: "Criticism of the C programming language ??????"
    ... "that's not in the standard, ... rewrites of the compiler. ... PH> They got all the compiler vendors to agree to a common ... or graphics libraries or threading libraries, ...
    (comp.lang.c)
  • Re: OT: Requesting C advice
    ... fit in the standard process memory footprint of a VAX at the time. ... in the libraries--and indeed how many libraries there were going to be. ... had (a PDP-11 and a VAX), the linker couldn't handle the library size. ... a nice Morrow Microdecision with two floppy disk drives. ...
    (Fedora)