Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Tue, 28 May 2002 17:08:57 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: libkernel32.a missing TOOLHELP API exports Message-ID: <20020528210857.GA6491@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <005901c20689$edb2a7f0$fe00a8c0@laptop> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <005901c20689$edb2a7f0$fe00a8c0@laptop> User-Agent: Mutt/1.3.23.1i On Tue, May 28, 2002 at 04:54:56PM -0400, Steven Edwards wrote: >I've attempted to build the wine psapi.dll under windows using msys and >cygwin and I get this result: > >psapi_main.o(.text+0x308):psapi_main.c: undefined reference to >`Process32First@8' >psapi_main.o(.text+0x31f):psapi_main.c: undefined reference to >`Process32Next@8' >psapi_main.o(.text+0x698):psapi_main.c: undefined reference to >`Module32First@8' >psapi_main.o(.text+0x6af):psapi_main.c: undefined reference to >`Module32Next@8' > >If no one else wants to do it I can submit a patch. What list do I need >to report win32api bugs on? Either or both of cygwin-patches@cygwin.com and mingw-dvlpr@sourceforge.net . I'm not sure where these definitions should go, though. Do they go into the kernel32.def file or should there be a separate tlhlp32.def file? Is there already a convention for this? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/