Giovanni Samaey wrote:
> changing the library path and explicitly adding libraries =['gsl',
> 'gslcblas'] did the trick !
one other suggestion:
if you want this to run any other machine, you might want to build gsl
as a static lib, so it will get linked directly into your extension, and
your
Thanks,
changing the library path and explicitly adding libraries =['gsl',
'gslcblas'] did the trick !
Thank you so much !
Giovanni
On 04 Nov 2008, at 12:09, Matthieu Brucher wrote:
> The issue with the LD_LIBRARY_PATH would come up in any case. You have
> to put your gsl library folder befor
The issue with the LD_LIBRARY_PATH would come up in any case. You have
to put your gsl library folder before the system one if you want your
gsl library to be used.
For the cblas issue, it seems from Google you have to link against a
CBLAS library as well to use the GSL (for instance blas or atlas
And, additionally setting the environment variable LD_LIBRARY_PATH to
start with /data/home/u0038151/lib instead of ending with it, it picks
up my own gsl, and gives the error message
0 [EMAIL PROTECTED] dot2 $ python -c "import dot"
Traceback (most recent call last):
File "", line 1, in ?
Hi Matthieu,
thank you for your prompt reply.
On 04 Nov 2008, at 11:24, Matthieu Brucher wrote:
>> # dot extension module
>> _test = Extension("_test",
>>["test_wrap.c",
>> "test.c"],
>>include_dirs = [numpy_include,'/data/home/
>> u003
> # dot extension module
> _test = Extension("_test",
> ["test_wrap.c",
> "test.c"],
> include_dirs = [numpy_include,'/data/home/
> u0038151/include'],
>library_dirs = ['/data/home/u0038151/lib']
> )
Dear all,
I am unsure about the correct place to put this question -- If this
isn't the correct list, please let me know which place is more
appropriate.
I am trying to build an extension module in python that calls a C
routine that depends on the GNU Scientific Library.
I am using swig to
