X-Spam-Check-By: sourceware.org
Date: Tue, 11 Apr 2006 16:38:30 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.15.19 dlopen() dies with no dlerror()
Message-ID: <20060411203830.GF29148@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <Pine DOT GSO DOT 4 DOT 58 DOT 0604111255381 DOT 25406 AT blinky>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.58.0604111255381.25406@blinky>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

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/