Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: dlsym, Win32 error 127 ERROR_PROC_NOT_FOUND Date: Sun, 20 Feb 2005 15:23:38 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: Message-ID: X-OriginalArrivalTime: 20 Feb 2005 15:23:38.0071 (UTC) FILETIME=[26888E70:01C51760] > -----Original Message----- > From: cygwin-owner On Behalf Of Dr Clue > Sent: 18 February 2005 22:05 > I've some .dll/.so code I use for plugins to my html > application parser. > > This code works fine on various unix flavors of OS , but > not with cywin on windows XP. > I know that the loadable library is being found , as changing > the filename of the loadable to some bogus name gets an error > (ERROR_MOD_NOT_FOUND 126) > > When I change the target filename back I get > (ERROR_PROC_NOT_FOUND 127) Actually the text of the error > is "dlsym, Win32 error 127" > Any clues? Use nm to check the names of the functions in the .so and see if the one you're looking for is actually there or not. My guess is they all got decorated with 'doze-style @nnn endings and you'll need to link with that ld flag that matches decorated and undecorated names, what was it again..... --enable-stdcall-fixup Link _sym to _sym AT nn without warnings That might do the trick. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/