[LDM #OBJ-220771]: Problems installing LDM

Hi Christian,

> I have the same results.
> 
> ~/ldm-6.13.16/bin] % more pqutil
> > #! /bin/bash
> > # pqutil - temporary wrapper script for .libs/pqutil
> > # Generated by libtool (GNU libtool) 2.4.2


> I did all the steps from the tar.gz:
> 
> >  1061  [27/09 18:11:20] rm -rf ldm-6.13.16

Why does this shell prompt differ from the previous one?

> 1062  [27/09 18:11:40] gunzip -c ldm-6.13.16.tar.gz | pax -r '-s:/:/src/:'
> >  1063  [27/09 18:11:45] cd ldm-6.13.16/src
> >  1064  [27/09 18:12:01] ./configure  >configure.log 2>&1
> >  1065  [27/09 18:12:49] make install >make.log 2>&1
> >
> And here are the config.log and make.log attached.

The libtool(1) utility that comes with the LDM distribution does this on my 
system:

Making install in pqutil
...
/bin/sh ../libtool  --tag=CC   --mode=link gcc -std=c99 -g -O0   -o pqutil 
pqutil.o ../lib/libldm.la -lxml2 -lpng -lz -lrt -lm -lpthread 
libtool: link: gcc -std=c99 -g -O0 -o .libs/pqutil pqutil.o  
../lib/.libs/libldm.so -lxml2 -lpng -lz -lrt -lm -lpthread -Wl,-rpath 
-Wl,/home/steve/Projects/ldm/lib
...
/bin/sh ../libtool   --mode=install /usr/bin/install -c pqutil 
'/home/steve/Projects/ldm/bin'
libtool: install: /usr/bin/install -c .libs/pqutil 
/home/steve/Projects/ldm/bin/pqutil

Note that the last line installs ".libs/pqutil", which is a binary executable.

On your system, however, the same libtool(1) utility does this, according to 
the file "make.log":

Making install in pqutil
...
/bin/bash ../libtool  --tag=CC   --mode=link gcc -std=c99 -g -O2   -o pqutil 
pqutil.o ../lib/libldm.la -lxml2 -lz -lrt -lm -lpthread 
libtool: link: gcc -std=c99 -g -O2 -o .libs/pqutil pqutil.o  
../lib/.libs/libldm.so -lxml2 -lz -lrt -lm -lpthread -Wl,-rpath 
-Wl,/home/ldm/ldm-6.13.16/lib
...
/bin/mkdir -p '/home/ldm/ldm-6.13.16/bin'
/bin/bash ../libtool   --mode=install /usr/bin/install -c pqutil 
'/home/ldm/ldm-6.13.16/bin'
libtool: install: /usr/bin/install -c pqutil /home/ldm/ldm-6.13.16/bin/pqutil

Note that the last line installs "pqutil", which is the libtool(1) wrapper 
script -- even though the binary executable was correctly built.

This shouldn't happen and I don't know why it does.

Could an environment variable be changing the behavior of the libtool(1) 
utility?

Googling this problem led to the workaround of changing the libtool(1) variable 
"fast_install" from "no" to "needless" (after the configure(1) script is run) 
via the Perl command "perl -pe -e 's/^fast_install.*/fast_install=needless' 
libtool".

I'm sorry I can't be of more help.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: OBJ-220771
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.