Werner Punz wrote:
> bene wrote:
>
>>
> I have to respecify the question, the problem I have seems to be javahl
> binding related (but not to deep in the binding because I get the same
> error if I move to javasvn with the binding libs still active)
> So switching to command line might help (havent tried it yet) but due to
> the bugs the command line layer has, I would prefer not to...
>
> The problem also could be EMT64 related because Intel broke several
> smaller things in the AMD64 bindings which might cause the mutex lock
> problems.
Sorry to answer myself here, but I got it up and running, I simply used
the pure java connector and with the pure java sublipse jar which
bypasses the javahl entirely.
The main mistake I made, just read that in another thread, was that the
plugin cache was still active, a simple eclipse -clean solved my problems.
Everything works fine now.
The problem I probably had was that the JNI bindings in the cache
probably referred to 32 bit library connectors and my JavaHL already was
64 bit, a simple replacement of the java JNI JavaHL bindings with the
self compiled ones and then cleaning up the cache (the old ones probably
were in the cache) would have resolved the problem very likely either.
But it runs and I am happy with it now.
Received on Sat Jan 29 01:35:30 2005