[csw-maintainers] issue when trying to provide a python binding

[Peter FELECAN]

Dagobert Michelsen <dam at opencsw.org> writes:

> Hi,
>
> Am 08.05.2009 um 18:24 schrieb Mike Watters:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi Peter,
>> Peter FELECAN wrote:
>>
>>> There are 2 issues:
>>>
>>> 1. I'm using gcc, so why cc is used? Because Python is generated with
>>>   Sun Studio?
>> Yes that is exactly correct, when you build a python extension it will
>> look at the way python was compiled and use those settings ( this is
>> just like
>> PERL )
>>
>>> 2. How comes that a specific build machine path is used, i.e. Sun
>>>   Studio is installed by default in /opt/SUNWspro (I know that it can
>>>   be installed at the administrator's convenience and on the build
>>>   machines is installed in a /opt/studio directory but that is
>>> another
>>>   story)
>>
>> Unfortunately, this is just the way it is handled,  it is true for
>> PERL and
>> most if not all the other packages that have a pkg-config like
>> structure.
>>
>> you should be able to work around this by setting the environment
>> variables
>> CC={path to cc} CXX={path to c++ (CC in SunStudio)}
>
> Is it really this bad? Then we should make Sun Studio 11 the default at
> /opt/SUNWspro and let GAR switch flags on the detected compiler if there
> is e. g. SS12 at that location.

Please. This will work for those not using gar, for the moment.

__ 
Peter