<executable>: "no version information available"

[Fernando Rodriguez]

On Tuesday, September 15, 2015 3:51:33 PM Fernando Rodriguez wrote:
> On Tuesday, September 15, 2015 11:57:40 AM René J.V. Bertin wrote:
> > Hi,
> > 
> > I know MacPorts isn't actually supported on Linux, but certain ports do 
> build without modification. I make very light use of that (and am even trying 
> if I can reuse my efforts on Qt5 ports), but have been running into an 
> interesting warning lately:
> > 
> > /opt/local/bin/cmake: /opt/local/bin/cmake: no version information 
available 
> (required by /opt/local/bin/cmake)
> > 
> > or
> > 
> > %> /opt/local/bin/bsdtar --version
> > /opt/local/bin/bsdtar: /opt/local/bin/bsdtar: no version information 
> available (required by /opt/local/lib/libxml2.so.2)
> > /opt/local/bin/bsdtar: /opt/local/bin/bsdtar: no version information 
> available (required by /opt/local/lib/libxml2.so.2)
> > bsdtar 3.1.2 - libarchive 3.1.2
> > 
> > I'm curious where this comes from (and how to remedy it), any ideas?
> > 
> > Thanks,
> > R.
> > _______________________________________________
> > macports-users mailing list
> > macports-users at lists.macosforge.org
> > https://lists.macosforge.org/mailman/listinfo/macports-users
> 
> It means that the libxml2.so that you linked against had versioned symbols 
but 
> the one that's getting loaded doesn't.

Actually it may be some other library that libxml.so linked against that has 
the versioned symbols. Running:

# ldd /opt/local/bin/cmake
# ldd /opt/local/bin/bsdtar
# ldd /opt/local/lib/libxml2.so.2

Will give you more info.

> 
> Most likely the compiler wasn't compiled correctly and is linking against 
your 
> system libraries. You can see nm to list the symbols on the libraries, the 
> ones with versioned symbols will have an @VERSION suffix on all symbols. You 
can 
> use the LD_LIBRARY_PATH and LD_PRELOAD environment variables to load the 
right 
> libraries for troubleshooting.
> 
> 

-- 
Fernando Rodriguez