Subject: Re: libiconv on Solaris 9/x86: libtool or tool ooops?
To: Jonathan Groll <lists@groll.co.za>
From: Hubert Feyrer <hubert@feyrer.de>
List: pkgsrc-users
Date: 07/26/2007 13:06:53
On Thu, 26 Jul 2007, Jonathan Groll wrote:
> I encountered a similar problem recently on opensolaris (nevada, build
> 66,sparc) and could be remedied by rebuilding libtool with the following in
> my mk.conf for good measure:
> TOOLS_PLATFORM.ar= /usr/ccs/bin/ar
> TOOLS_PLATFORM.nm= /usr/ccs/bin/nm
> TOOLS_PLATFORM.ranlib= /usr/ccs/bin/ranlib
> USE_TOOLS+= ar nm ranlib
Unfortunately that still produces the same errors:
...
/bin/sh ../libtool --mode=link gcc -Wl,-R/bindata/Solaris/intel/9/pkg2/lib
-o libcharset.la -rpath /bindata/Solaris/intel/9/pkg2/lib -version-info
1:0:0 -no-undefined localcharset.lo relocatable.lo
gcc -shared .libs/localcharset.o .libs/relocatable.o
-L/net/zeus/bindata/NetBSD/cvs/pkgsrc/converters/libiconv/work.i386/.buildlink/lib
-lc -Wl,-R/bindata/Solaris/intel/9/pkg2/lib -Wl,-soname
-Wl,libcharset.so.1 -o .libs/libcharset.so.1.0.0
ld: warning: option -o appears more than once, first setting taken
ld: fatal: file libcharset.so.1: open failed: No such file or directory
ld: fatal: File processing errors. No output written to
.libs/libcharset.so.1.0.0
That's with libtool-base reinstalled with the above settings, and also
making sure that the 'ld' (and as, ...) in path are picked up from
/usr/ccs/bin.
- Hubert