On Wed, 19 Jan 2011 18:19:45 +0100, "Islam El Salawi"
thanks for your response. I'd like to know,
whether you are able to run the
square.py example. I'm just wondering, because you told me, maybe I am not
feeding hedge with the right date types. But I am not feeding anything, I
am just trying to run the square.py example and then this error comes up.
I took your advice and debugged the square script and all arguments of arg
were of type numpy array float 64, except the first two of them, which were
something like uniform element or something.
I even reinstalled hedge and took another version of boost, but it still
does't work out.
I'm stuck and I really need help to move on with my calculations. Thanks
Sorry for the delay. I was finally able to reproduce the issue you are
seeing, and as far as I can tell it's likely due to two versions of
Boost on your include path. This often happens if you install one
version of Boost yourself, and your Linux distribution installs another,
typically in /usr. (This can happen behind your back, say to satisfy a
dependency of another package, or if a sysadmin does so.) The solution
would usually be to get rid of one of those boost installations. (If you
get rid of the systemwide one, you only need to remove the *dev
package--not the entire library!) In general, the systemwide one should
be ok, though, and a self-compiled one is redundant.
In my case, I was compiling against headers from boost 1.39, but linking
against a library built from boost 1.42. In general, doing this can have
arbitrarily bad results--crash, load failures, what have you. In your
case, it boiled down to a PyUblas overload failure. Which is within the
realm of the possible.
You can also try deleting
(substituting your user ID for NNNN) This *shouldn't* be a factor, but
deleting this is generally harmless, so it helps eliminate 'stale cached
binaries' as a failure reason.
Hope this helps,