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 Date: Wed, 29 May 2002 10:21:55 +0400 From: egor duda Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <157920282546.20020529102155@logos-m.ru> To: Christopher Faylor Subject: Re: libkernel32.a missing TOOLHELP API exports In-Reply-To: <20020528210857.GA6491@redhat.com> References: <005901c20689$edb2a7f0$fe00a8c0 AT laptop> <20020528210857 DOT GA6491 AT redhat DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Wednesday, 29 May, 2002 Christopher Faylor cgf AT redhat DOT com 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 AT 8' >>psapi_main.o(.text+0x31f):psapi_main.c: undefined reference to >>`Process32Next AT 8' >>psapi_main.o(.text+0x698):psapi_main.c: undefined reference to >>`Module32First AT 8' >>psapi_main.o(.text+0x6af):psapi_main.c: undefined reference to >>`Module32Next AT 8' >> >>If no one else wants to do it I can submit a patch. What list do I need >>to report win32api bugs on? CF> Either or both of CF> cygwin-patches AT cygwin DOT com and mingw-dvlpr AT sourceforge DOT net . CF> I'm not sure where these definitions should go, though. Do they go into CF> the kernel32.def file or should there be a separate tlhlp32.def file? Process32First AT 8 is not present in kernel32.dll on nt4.0 sp5. I believe this kind of api is very OS-specific. On nt4.0 process enumeration functions are available from microsoft's psapi.dll included (among others) in Resource kit. Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19 -- 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/