On Wed, Sep 20, 2006 at 12:51:24PM -0700, Adam D. Morley wrote: > On Wed, Sep 20, 2006 at 09:21:19PM +0200, Ralf S. Engelschall wrote: > > On Wed, Sep 20, 2006, Adam D. Morley wrote: > > > > > On Wed, Sep 20, 2006 at 09:10:10PM +0200, Ralf S. Engelschall wrote: > > > > On Wed, Sep 20, 2006, Adam D. Morley wrote: > > > > > > > > > [...] > > > > > > And on top of all this I've to say that it works just fine for me on > > > > > > rm1.openpkg.net (a Solaris 10/x86 box) as the attached logfile > > > > > > shows. > > > > > > > > > > Ok, two questions: > > > > > > > > > > 1. Do you have a SPARC box? > > > > > > > > Yes, and _THERE_ is even fails for me now, too: > > > > > > > > | /bin/ksh ../libtool --mode=link /openpkg-dev/bin/cc -Wall -W -O2 > > > > -pipe -I/openpkg-dev/include -L/openpkg-dev/lib -R/openpkg-dev/lib > > > > -L/openpkg-dev/lib -L/openpkg-dev/lib -o client client.o common.o > > > > ../lib/libsasl2.la -lresolv -lresolv -ldb -lfsl -lsocket -lnsl -lrt > > > > | mkdir .libs > > > > | /openpkg-dev/bin/cc -Wall -W -O2 -pipe -I/openpkg-dev/include > > > > -L/openpkg-dev/lib -L/openpkg-dev/lib -L/openpkg-dev/lib -o > > > > .libs/client client.o common.o ../lib/.libs/libsasl2.so -ldl -lresolv > > > > -ldb -lfsl -lsocket -lnsl -lrt -lresolv -lresolv -ldb -lfsl -lsocket > > > > -lnsl -lrt -Wl,--rpath -Wl,/openpkg-dev/lib > > > > | ../lib/.libs/libsasl2.so: undefined reference to [EMAIL PROTECTED]' > > > > | ../lib/.libs/libsasl2.so: undefined reference to [EMAIL PROTECTED]' > > > > | ../lib/.libs/libsasl2.so: undefined reference to [EMAIL PROTECTED]' > > > > | ../lib/.libs/libsasl2.so: undefined reference to [EMAIL PROTECTED]' > > > > | ../lib/.libs/libsasl2.so: undefined reference to [EMAIL PROTECTED]' > > > > | collect2: ld returned 1 exit status > > > > | make[2]: *** [client] Error 1 > > > > | make[1]: *** [all-recursive] Error 1 > > > > | make: *** [all] Error 2 > > > > | error: Bad exit status from /tmp/rse/openpkg/rpm-tmp.2569 (%build) > > > > > > > > I'll investigating... > > > > > > I think it's a bug with /lib/libdl.so.1, because it looks like that file > > > was updated on July 13th. Can you confirm you have a similar libdl?: > > > > > > [adam cyrus-sasl-2.1.22]$ ls -l /lib/libdl.so.1 > > > -rwxr-xr-x 1 root bin 3940 Jul 13 10:22 /lib/libdl.so.1 > > > [adam cyrus-sasl-2.1.22]$ openssl dgst -md5 /lib/libdl.so.1 > > > MD5(/lib/libdl.so.1)= 5a5c56cb0d945e835c273bea6868508a > > > > > > And whether the x86 box has older/newer? > > > > - The Solaris 10/x86 box has: > > -rwxr-xr-x 1 root bin 3880 Jan 23 2005 /lib/libdl.so.1 > > > > - The Solaris 10/sparc64 box has: > > -rwxr-xr-x 1 root bin 3940 Jul 11 2005 /lib/libdl.so.1 > > > > Anyway, the main problem here was that we accidentaly built against > > the shared library version of SASL. Why this fails just under Solaris > > 10/sparc64 I don't know -- and to be honest, I also don't want to know > > it as Solaris always makes more trouble than one expects. But I've > > now fixed it by forcing the "-static" linking also for the sample > > applications in the SASL distribution and it now built fine again for me > > under Solaris 10/sparc64: http://cvs.openpkg.org/chngview?cn=30163 Just > > take the latest and greatest from CURRENT and it should now also work > > for you... > > It does. For others that experience the problem: patch 118833-23 does > nothing. Reporting to OpenSolaris if I can figure out how.
FWIW: cyrus-sasl-2.1.22 built fine with the gcc Sun ships with S10, where the OpenPKG gcc failed. So there is likely something wrong with OpenPKG gcc on Solaris when building shared. But I have no idea what or how to track it down. -- adam ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [email protected]
