[PD] pb with pyext and readanysf~ on OSX

[Thomas Grill]

Hi Vincent,

>>  it looks like it comes from this line
>>
>> typedef struct  
>> {                                                                      
>>                                                                        
>>             
>> PyObject_HEAD                                                          
>>                                                                        
>>                   PyObject *operator;          /* ufunc name */  
>>

it's fairly clear.... operator is a C++ keyword.
This can be considered as a numarray bug and seems to have been removed  
in version 1.5.0 i just tried.

>
> well, i'll have to look at that... which numarray version are you  
> using?
>
>
>>
>>  It is possible to launch pd39.2 with readanysf or pyext separetely  
>> but when i try to load both, i get;
>> ------------------------------------------------
>>  py/pyext 0.2.1pre - python script objects
>>  (C)2002-2005 Thomas Grill - http://grrrr.org/ext
>>
>>  using Python 2.4.1 (#2, Mar 31 2005, 00:05:10)
>>  [GCC 3.3 20030304 (Apple Computer, Inc. build 1666)]
>>  ------------------------------------------------
>>
>>  link error 0  dyld: /Applications/pd39.app/Contents/Resources/bin/pd  
>> multiple definitions of symbol _initialized
>>  /data/pdlibs/py.pd_darwin definition of _initialized
>>  /usr/local/lib/libflext-pd.dylib(flthr.opp) definition of  
>> _initialized
>>
>>  readanysf~: can't load library
>
>
> that's a known problem....  
> http://sourceforge.net/tracker/index.php? 
> func=detail&aid=1378927&group_id=55736&atid=478072
>
> There are two workarounds:
> - change the options to NSLinkModule in s_loader.c as described above  
> and recompile pd
> - build all flext externals using the flext shared library (build.sh  
> pd gcc build-release-shared)
>

hmmm, the latter doesn't seem to work... i hope i can find a workaround  
to get it going. Waiting for pd to change can be really tiresome.

all the best,
Thomas