Hello,
On Fri, 30 Sep 2005, Donald A. Dade wrote:
A follow-up to some investigating I've done into ny Solaris 2.6 problem with
2.3.11:
1) I tried compiling 2.3.11 with --enable-threads --enable-pthreads and gcc
2.95.2, 3.3.2, and 3.4.4 with no success because apparently 2.6 has no
support for POSIX read/write locks.
yes, MICO depends on POSIX read-write locks.
2) I tried those same compilers with --enable-threads
--enable-solaris-threads, also to no avail because there were a lot of
compile errors due to the MICO namespace.
solaris threads are probably completely broken. In fact I've never seen
them running, since solarises which I have access to, all supported RW
locks well and so we used POSIX by default.
3) Compiling without threads worked fine, but my app always gets TRANSIENT
failures whenever I compile with -DREENTRANT, regardless of wether I actually
have multiple threads in the program or even if I have multiple threads, but
only one that interacts with the orb.
that's interesting, since this point to probably broken transport or IOP
layer. For debugging you can find -ORBDebug GIOP -ORBDebug IIOP useful.
If I can find the time, I'll fix it, but for now, I think Solaris 2.6 should
be taken off of the compatibility list for multi-threaded 2.3.11 if it were
ever explicitly on it.
If you need multi-threading and if you really prefer SunOS 5.6, then I
would recommend you to write RW lock on top of POSIX mutex. We can also do
it for you under the contract agreement if you prefer this way.
Thanks,
Karel
--
Karel Gardas [EMAIL PROTECTED]
ObjectSecurity Ltd. http://www.objectsecurity.com
---
Need experienced, fast, reliable technical MICO support?
---> http://www.objectsecurity.com/commsup.html <---
---
_______________________________________________
Mico-devel mailing list
[email protected]
http://www.mico.org/mailman/listinfo/mico-devel
