Mail Archives: cygwin/2001/03/31/03:46:18
First, thanks for your help,
Jason Tishler wrote:
> Bruno,
>
> On Fri, Mar 30, 2001 at 10:20:33PM +0200, bruno patin (travail) wrote:
>
>> I try to port omniorb on the cygwin platform. To do this, I'm first
>> porting python. I don't know why but I can't compile python with the
>> thread support and so I have problems with omniorb. Has someone
>> attempted such a thing.
>
>
> I noticed a while ago that omniorb needed Python to build their toolset.
> Are you sure that you need a Python with threading or just the ability
> to run Python scripts? If the latter, then note that Python 2.1b2 builds
> OOTB under Cygwin if you configure as follows:
>
> $ configure --with-threads=no
I did it before and it compile. But in the port of omniorb itself, the
omniidl command needs some Python software that it can't see. I wrote to
the omniorb mailing list and they ask me if cygwin could create .so
libraries. I didn't observe the gcc -shared command but I think you made
it identical with the other gcc on the other platforms. They ask for
knowing which platform to choose for the compilation as the cygwin one
doesn't exist. I took the glibc2.1 platform. Do you think it is right (I
regard the gcc version for this choice).
My choices :
to return to the python compiling and introduce a correct support thread
to use the native win32 omniorb implementation (is it possible and how)
to use another orb that is already ported on cygwin (do you know one)
As it is essential to my work I'm ready to make this effort as I think
it is really interesting to have a Broker present and native for the
cygwin platform in order to further banalize the windows os inside unix
environment (as a matter of fact your work is really good).
>
>
> Sorry, but Cygwin Python's support of threads is not ready for prime
> time.
>
> Jason
>
Thanks a lot
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
- Raw text -