Martin Costabel wrote:
Sébastien Maret wrote:
[]
That's a bug in numarray 1.4.1. A bug report has been filled for it:
http://sourceforge.net/tracker/index.php?func=detail&aid=1350954&group_id=1369&atid=101369
Meanwhile you can downgrade to a earlier version of numarray.
The fink numarray package should perhaps fix this stupid bug by renaming
the member called "operator" to something that doesn't conflict with C++
reserved words. I think this new struct in nummacro.h is used nowhere
and is only half-baked anyway, so nothing will break if we rename
"operator" to "operator_name" or something.
The numarray people have now patched this in their CVS. They just
renamed "operator" to "oprator" (!). They seem not completely convinced
that this is the right fix, and I cannot judge, because there are
"operator" variables all over the place, too.
In any case, I made a numarray-py.patch file from that CVS diff, and put
the new numarray-py.{info,patch} files into my exp directory. For me,
this works in the sense that visual-pyXX now compiles without error, but
I haven't run any tests yet.
--
Martin
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users
