Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Fri, 16 Mar 2001 10:32:53 -0500 From: Christopher Faylor To: Cygwin Subject: Re: Win32 error 127 with dlsym & dlopen Message-ID: <20010316103253.H11518@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: Cygwin References: <003f01c0adf8$f3643820$db011fac AT fer DOT ucs DOT co DOT za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <003f01c0adf8$f3643820$db011fac@fer.ucs.co.za>; from fer@ucs.co.za on Fri, Mar 16, 2001 at 11:10:31AM +0200 On Fri, Mar 16, 2001 at 11:10:31AM +0200, Frans Rossouw wrote: >Hey all > >OK, you are probably all sick of me by now but here goes anyways :) > >a) i) Does anyone know if dlopen has been modified to cater for: > > handle = dlopen (NULL, RTLD_LAZY); > ^^ > at this stage, the only way to stop the dlopen > from generating a error 127 is to give an absolute path to the .exe?? > > ii)When I try to use a dlsym after the dlopen I also get the error 127? > Does anyone know how I can get by this? > fPtr = (int (*)(int)) dlsym (handle, buf); > >b) Does anyone have a patched version somewhere? >c) Can you guys help me patch it myself? Try a snapshot: http://cygwin.com/ , look for "Snapshots". cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple