Unfortunately, the distributed parts of our app is a relatively smal part of the whole system, and it would generate a lot of work for other people. That's why the move to HP/Itanium, which would solve all our problems, is not completed.

And yes, I can verify that threads and 2.95.2 do not mix, from experience with other, non-distributed code that I've written :(

Thanks for the info.

Fred Down wrote:

Is there a pressing reason to use Solaris 2.6 , I have dropped developing
for it. Solaris 7 and 8 run well on older hardware, I still use my Sparc 4
with Solaris 8. Both versions of Solaris can be bought cheaply on e-bay.

Do not use threads with gcc 2.95.2 since there is a compiler bug which will
cause your code to crash from time to time

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Donald A. Dade
Sent: Saturday, October 01, 2005 1:27 AM
To: [email protected]
Subject: [mico-devel] Solaris 2.6 incompatible with threaded 2.3.11

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.

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.

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.

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.

Don
_______________________________________________
Mico-devel mailing list
[email protected]
http://www.mico.org/mailman/listinfo/mico-devel


_______________________________________________
Mico-devel mailing list
[email protected]
http://www.mico.org/mailman/listinfo/mico-devel

Reply via email to