AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
March 2006

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems



Valid HTML 4.01!



Thread

2006.03.28 21:24 "lots of compile errors on solaris for v 3.8.2", by Mike Stevenson
2006.03.28 22:05 "Re: lots of compile errors on solaris for v 3.8.2", by Bob Friesenhahn

2006.03.28 22:05 "Re: lots of compile errors on solaris for v 3.8.2", by Bob Friesenhahn

On Tue, 28 Mar 2006, Mike Stevenson wrote:
>
> Hi, I'm trying to build libtiff and am getting a lot of errors on
> compilation.  The ./configure runs with no complaints, and make starts
> off well also.  then i get
> Text relocation remains                 	referenced
>    against symbol		    offset	in file
>
> and about 1300 lines of (no, really) stuff like this:
> <unknown>                           0xae0
> /opt/local/lib/gcc-lib/sparc-sun-solaris2.6/2.95.3/libstdc++.a(iovfscanf.o)
>
> The symbol and offsets vary pretty widely, but the referenced file is
> always libstdc++.a, with some or another .o file in parenthesis.  The
>
>
> I don't have root access to this machine.  Is this something I can work
> around myself, or is it something wrong on a higher level?  I've been
> doing a lot of building of late, and this is the first time I've seen
> anything like this.  Any help is greatly appreciated.

Are you using Solaris 2.6?  It is good to make sure that you are not 
using a compiler built for an older version of Solaris since doing so 
can cause problems ...

Regardless, the error is caused by GCC's C++ library not being built 
as a shared library.  In order for libtiff's shared library to link 
with it, GCC's C++ library also needs to be built as a shared library.

If you are not planning to use the C++ interface, then you can try 
configuring libtiff like

  ./configure --disable-cxx

This should disable the C++ component of libtiff so the problem goes 
away.  There is also the option of specifying --disable-shared but 
this will have the effect of building libtiff itself as only a static 
library.

Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/