[csw-maintainers] Sun Studio 11 is broken on current9s ATM

Dagobert Michelsen dam at opencsw.org
Fri Sep 17 22:14:31 CEST 2010


Hi,

Am 17.09.2010 um 21:51 schrieb Dagobert Michelsen:
> Am 01.09.2010 um 20:45 schrieb Yann Rouillard:
>> Dear buildfarm maintainers,
>>
>> I am currently trying to compile last openssl version and I am  
>> running into the following error:
>>
>> [...]
>> making all in crypto...
>> gmake[3]: Entering directory `/home/yann/mgar/openssl/trunk/work/ 
>> solaris9-sparc/build-isa-sparcv8/openssl-0.9.8o/crypto'
>> cc -I. -I.. -I../include -KPIC -DOPENSSL_PIC -DOPENSSL_THREADS - 
>> D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -xarch=v8 -xO5 -xstrconst - 
>> xdepend -Xa -DB_ENDIAN -DBN_DIV2W -I/opt/csw/include  -c -o  
>> cryptlib.o cryptlib.c
>> ld.so.1: acomp: fatal: libyabe.so: open failed: No such file or  
>> directory
>> cc: Fatal error in /opt/studio/SOS11/SUNWspro/prod/bin/acomp : Killed
>> gmake[3]: *** [cryptlib.o] Error 9
>> gmake[3]: Leaving directory `/home/yann/mgar/openssl/trunk/work/ 
>> solaris9-sparc/build-isa-sparcv8/openssl-0.9.8o/crypto'
>> gmake[2]: *** [build_crypto] Error 1
>> gmake[2]: Leaving directory `/home/yann/mgar/openssl/trunk/work/ 
>> solaris9-sparc/build-isa-sparcv8/openssl-0.9.8o'
>> gmake[1]: *** [build-work/solaris9-sparc/build-isa-sparcv8/ 
>> openssl-0.9.8o/Makefile] Error 2
>> gmake[1]: Leaving directory `/home/yann/mgar/openssl/trunk'
>> gmake: *** [merge-isa-sparcv8] Error 2
>>
>> It seems to be related to SUNWspro so I am trying to know at your  
>> door.
>>
>> Any idea what is the origin of this problem ?
>>
>> I saw the following pages on internet about libyabe.so:
>> http://hub.opensolaris.org/bin/view/Community+Group+ha-clusters/FAQ#buildingagents
>> http://forums.sun.com/thread.jspa?threadID=5071875
>>
>> libyabe.so is present at:
>> /opt/SUNWspro/prod/lib/sys/libyabe.so
>>
>> I might add this path but I suppose there is something else wrong.
>
> I looked more into it and in fact Sun Studio 11 is broken at least
> on current9s. The installation is definitely broken and my guess is
> that it is due to my installation/removal order of SOS11/12/12u1,
> then remove and reinstall 12 again because of a faulty script not
> taking multi-instance-packages into account correctly.
>
> I am reinstall Sun Studio 11 on current9s now and fix the issue.
> BTW: I need SOS11 too for a libserf bump bound to the compilation
> of the Apache stack also compiled with SOS11 ATM.

My guess was right: the try to remove/reinstall SOS11 corrupted the
SOS12 installation, so there is a glitch in the scripts:
   ld: fatal: file /opt/SUNWspro/prod/lib/v9/crti.o: open failed: No  
such file or directory

I guess I need to remove SOS12 also als then reinstall SOS11 and SOS12
without intermediate removal. Later I will inspect the compiler
installations on the other machines...


Sorry for the inconvenience

   -- Dago



More information about the maintainers mailing list