[csw-buildfarm] python not using the new SOS12 path ...

[Dagobert Michelsen]

Hi Rupert,

Am 31.08.2010 um 19:04 schrieb rupert THURNER:
> while trying to release a new version of mercurial it bailed out with:
>
> /opt/studio/SOS12/SUNWspro/bin/cc -G -m32 -xarch=v8 -norunpath
> -L/opt/csw/lib -xO3 -m32 -xarch=v8 -xnorunpath -I/opt/csw/include
> build/temp.solaris-2.9-sun4u-2.6/mercurial/base85.o -L/opt/csw/lib
> -lpython2.6 -o build/lib.solaris-2.9-sun4u-2.6/mercurial/base85.so
> unable to execute /opt/studio/SOS12/SUNWspro/bin/cc: No such file or  
> directory
> error: command '/opt/studio/SOS12/SUNWspro/bin/cc' failed with exit  
> status 1
> gmake[2]: *** [build-work/solaris9-sparc/build-isa-sparcv8/ 
> mercurial-1.6.3/setup.py]
> Error 1
> gmake[2]: Leaving directory `/home/rupert/mgar/pkg/mercurial/trunk'
> gmake[1]: *** [merge-isa-sparcv8] Error 2
> gmake[1]: Leaving directory `/home/rupert/mgar/pkg/mercurial/trunk'
> gmake: *** [platforms] Error 2
>
> it seems the python package installed on the buildserver has the old
> path in it, and setuptools tries to use it while building mercurial.
> what can we do to fix this?

We kindle ask Maciej to just respin Python, which should fix the  
problem.


Best regards

   -- Dago