Hello,
after installation of the newest cygwin release I cannot make a small
swig-program example which worked before.
I am not sure what of the many reinstalled cygwin components is responsible
for that, but I suppose that you test it and recompile it in the case of
need.
Here is the error mess
Hello Pavel,
great! This is the solution. Now I can proceed with my work.
Thanks to all who led me to this solution,
and sorry for assuming problems at wrong places at first.
Claudius
-
This Mail has been checked for Viruses
Attention:
Hello Norman,
that sounds interesting!
1)
First the versions of the used tools: gcc, swig, python:
@PC169/.../simple$ gcc -v
Reading specs from /bin/../lib/gcc-lib/i686-pc-cygwin/3.2/specs
Configured with: /netrel/src/gcc-3.2-1/configure
-
Hello,
I migrated my software to gcc-3.2.1.
Now I wish to build a dynamic module for python in cygwin, which is compiled
with gcc-2.95.
Since object code is not compatible between the two gcc-versions, I would
like to know whether a python-build for gcc-3.2 is available or when it is
supposed to
Hello,
I try to build some libraries, which in turn create *.so shared libraries.
According to my tests,
- names of shared libraries under cygwin have to end in .dll,
- the LD_LIBRARY_PATH is not searched for .dlls
Is this correct?
Are there some workarounds to configure cygwin to behave like a
5 matches
Mail list logo
