Dnia 2011-06-02, czw o godzinie 09:08 +0200, Bogdan Opanchuk pisze: > Hello Andreas, > > On Wed, Jun 1, 2011 at 10:09 PM, Andreas Kloeckner > <[email protected]> wrote: > > I assume you're using shipped boost? > > Yes, I do. > > > I guess there's one thing I hadn't considered when merging the CURAND > > patches, and that is what happens when using shipped boost. As the > > CURAND wrappers end up being a separate binary, they simply don't get > > access to boost, which they need. Not sure what to do. I'm not sure > > setuptools is up to the job of building a separated shared library for > > boost, or if the _curand binary can have access to the boost bits in > > _driver. Any shared library gurus care to comment? > > I am by no means a guru, but can't you just link boost statically to > _curand as you do for _driver? Is the increased size of the module > such a bad thing?
I cannot help with this. I have also never experienced this problem. I am always using Boost from Debian, disabling shipped Boost; this was introduced during packaging as Debian requires packages to use system libraries, not providing own. > > > If worst comes to worst, we'll just shove the _curand wrappers back into > > the main PyCUDA wrapper binary. > > In the meantime the second issue should be fixed somehow, I think. > Currently I am using the following workaround: > > - def generate_direction_vectors(count, > direction=direction_vector_set.VECTOR_32): > + def generate_direction_vectors(count, direction=None): > + if direction is None: > + direction = direction_vector_set.VECTOR_32 I am working on wrapping CURAND 4.0 (not ready yet), and at the same time I have put equivalent change into source. Should I send it as separate patch, or just with CURAND 4.0? Best regards. -- Tomasz Rybak <[email protected]> GPG/PGP key ID: 2AD5 9860 Fingerprint A481 824E 7DD3 9C0E C40A 488E C654 FB33 2AD5 9860 http://member.acm.org/~tomaszrybak
signature.asc
Description: This is a digitally signed message part
_______________________________________________ PyCUDA mailing list [email protected] http://lists.tiker.net/listinfo/pycuda
