[LDM #PXK-681085]: LDM v6.12.6 on Mac OS X v10.8.5

Dave,

I don't know why, but your linker is treating the "z" library differently than 
the "xml2" library. It stores the relative pathname of the "z" library in the 
LDM library, but the absolute pathname of the "xml2" library there. I'm 
guessing that the linker differentiates between them because the "z" library 
isn't in a system library directory.

Can you move or copy the "z" library, "libz.so.1.2.8", to a system library 
directory (e.g., "/usr/lib") and try again? Don't use the "--disable-shared" 
option of the configure(1) script. If it doesn't work, then please send me the 
files "configure.log" and "config.log".

> On Jan 22, 2015, at 3:28 PM, Unidata LDM Support <address@hidden> wrote:
> 
> > >> Which hupsyslog(1) program are you getting? Do a "which hupsyslog" or 
> > >> "type hupsyslog" and then get a long listing of the indicated program.
> 
> ldm_virga% ls -l `type hupsyslog | awk '{print$NF}'`
> -rwsr-xr-x  1 root  staff  9108 Jan 22 16:50 
> /usr/local/unidata/ldm/bin/hupsyslog*
> 
> > >> Does its timestamp correspond to when you installed the static LDM?
> 
> Yep.
> >
> > >> What's the output of the command "otool -L $HOME/bin/hupsyslog”.
> 
> ldm_virga% otool -L ~ldm/bin/hupsyslog
> /Users/ldm/bin/hupsyslog:
> /usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current version 
> 10.8.0)
> libz.so.1.2.8 (compatibility version 0.0.0, current version 0.0.0)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 
> 169.3.0)
> /usr/local/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 
> 1.0.0)

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: PXK-681085
Department: Support LDM
Priority: Normal
Status: Closed