Hi, as our nightly-build script stops after this error, I got only a few packages compiled.
After I forced the script to continue compiling after the openssl error, over 90 other openpkg packages compiled without an error. Peter Zimmer -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Ralf S. Engelschall Gesendet: Freitag, 20. Januar 2006 22:06 An: openpkg-users@openpkg.org Betreff: Re: Cannot compile OpenSSL on AMD64/Solaris 10 On Fri, Jan 20, 2006, Peter Zimmer wrote: > here are some more lines before the error occurs: > > gcc -DMONOLITH -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT -fPIC > -m64 -O3 - > Wall -DL_ENDIAN -DMD32_REG_T=int -DMD5_ASM -c -o engine.o engine.c > gcc -DMONOLITH -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT -fPIC > -m64 -O3 - > Wall -DL_ENDIAN -DMD32_REG_T=int -DMD5_ASM -c -o ocsp.o ocsp.c > gcc -DMONOLITH -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT -fPIC > -m64 -O3 - > Wall -DL_ENDIAN -DMD32_REG_T=int -DMD5_ASM -c -o prime.o prime.c > gcc -DMONOLITH -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT -fPIC > -m64 -O3 - > Wall -DL_ENDIAN -DMD32_REG_T=int -DMD5_ASM -c -o openssl.o openssl.c > rm -f openssl > shlib_target=; if [ -n "" ]; then \ > shlib_target="solaris-shared"; \ > fi; \ > if [ "${shlib_target}" = "darwin-shared" ] ; then \ > LIBRARIES="../libssl.a ../libcrypto.a" ; \ > else \ > LIBRARIES="-L.. -lssl -L.. -lcrypto" ; \ > fi; \ > /opt/local/bin/make -f ../Makefile.shared -e \ > APPNAME=openssl OBJECTS="openssl.o verify.o asn1pars.o req.o > dgst.o dh.o > dhparam.o enc.o passwd.o gendh.o errstr.o ca.o pkcs7.o crl2p7.o crl.o > rsa.o rsaut > l.o dsa.o dsaparam.o ec.o ecparam.o x509.o genrsa.o gendsa.o s_server.o > s_client. > o speed.o s_time.o apps.o s_cb.o s_socket.o app_rand.o version.o > sess_id.o cipher > s.o nseq.o pkcs12.o pkcs8.o spkac.o smime.o rand.o engine.o ocsp.o > prime.o" \ > LIBDEPS=" $LIBRARIES -lsocket -lnsl -ldl" \ > link_app.${shlib_target} > ( :; LIBDEPS="${LIBDEPS:--L.. -lssl -L.. -lcrypto -lsocket -lnsl > -ldl}"; LDCMD=" > ${LDCMD:-gcc}"; LDFLAGS="${LDFLAGS:--DOPENSSL_THREADS -D_REENTRANT -fPIC > -m64 -O3 > -Wall -DL_ENDIAN -DMD32_REG_T=int -DMD5_ASM}"; LIBPATH=`for x in > $LIBDEPS; do if > echo $x | grep '^ *-L' > /dev/null 2>&1; then echo $x | sed -e 's/^ > *-L//'; fi; > done | uniq`; LIBPATH=`echo $LIBPATH | sed -e 's/ /:/g'`; > LD_LIBRARY_PATH=$LIBPAT > H:$LD_LIBRARY_PATH ${LDCMD} ${LDFLAGS} -o ${APPNAME:=openssl} openssl.o > verify.o > asn1pars.o req.o dgst.o dh.o dhparam.o enc.o passwd.o gendh.o errstr.o > ca.o pkcs7 > .o crl2p7.o crl.o rsa.o rsautl.o dsa.o dsaparam.o ec.o ecparam.o x509.o > genrsa.o > gendsa.o s_server.o s_client.o speed.o s_time.o apps.o s_cb.o s_socket.o > app_rand > .o version.o sess_id.o ciphers.o nseq.o pkcs12.o pkcs8.o spkac.o smime.o > rand.o e > ngine.o ocsp.o prime.o ${LIBDEPS} ) > /usr/lib/amd64/crt1.o: file not recognized: File format not recognized Now I'm confused. The flags clearly show that OpenSSL correctly builds and links with a 64-bit enforced GCC (which especially results in the picking up of the /usr/lib/amd64/crt1.o). But I've no clue remotely why ld(1) cannot recognize the file format of the crt1.o. OTOH is this problem just occurring when building "openssl" or does it also occur when building other packages (except for "make", "binutils" and "gcc")? If others have the same problem we are searching in the wrong corner. Then GNU binutils have configured theirself incorrectly or something like this... Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List openpkg-users@openpkg.org ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List openpkg-users@openpkg.org
