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

[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)}

> The second issue is a show stopper for me...


- --

Thanks,
Mike

"Any intelligent fool can make things bigger, more complex,
and more violent.  It takes a touch of genius -- and a lot of courage --
to move in the opposite direction."

* Albert Einstein 1879 - 1955
    US German-born Theoretical Physicist
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkoEXKIACgkQLrhmsXMSLxfRWgCfWix2FTTnX34uuzsr5AWXDPao
zeYAn2gbcXoeX73QwLFKdd73y1NiOBpf
=+rV1
-----END PGP SIGNATURE-----