Mail Archives: cygwin/2006/04/11/16:38:43
On Tue, Apr 11, 2006 at 01:22:39PM -0700, Michael McKerns wrote:
>I've been using the following Makefile syntax with building cygwin
>applications:
>
>$(PROJ_DLL) $(PROJ_SAR): product_dirs $(PROJ_OBJS)
> $(CXX) $(LCXX_SARFLAGS) -Wl,--out-implib=$(PROJ_SAR) \
> -o $(PROJ_DLL) $(PROJ_OBJS) $(LCXXFLAGS)
>
>This is exactly what is in the cygwin documentation, but generalized
>for Makefiles. It has succesfully generated executables since way
>back, and was still working for cygwin 1.15.18-3, however since I've
>upgraded to 1.15.19-4 it fails.
>
>The behavior is this:
>Output from compile and build steps produce the expected linking
>messages. No apparent errors.
>
>However, applications die at dlopen.
>
>Example (1):
>importing a shared library (journal) through python
> $ python -v
> ...
> >>> import journal
> import journal # directory /home/mmckerns/tools/.../journal
> ...
> dlopen("/home/mmckerns/tools/.../_journalmodule.dll", 2);
>
>python dies here, and exits with no error.
>That lead me to writing a little test script to check the
>behavior of the .dll in C (without python).
>
>Example (2):
>testing a shared library (journal) with dlopen & dlerror
> $ ./dlopen.exe
> .dll TEST...
>
>the executable dies here, and exits with no error or print
>(please see attached dlopen.c)
WFM.
$ ./dlerr
.dll TEST...
No such file or directory
bash-3.1$ uname -a
CYGWIN_NT-5.1 norton 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin
Please see: http://cygwin.com/problems.html .
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -