libkernel32.a missing TOOLHELP API exports

libkernel32.a missing TOOLHELP API exports

[Steven Edwards]

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?

Thanks
Steven


"Every revolution was once a thought in one man's mind"
- Ralph Waldo Emerson 


--
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/

Re: libkernel32.a missing TOOLHELP API exports

[Christopher Faylor]

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/

Re: libkernel32.a missing TOOLHELP API exports

[Earnie Boyd]

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?
> 

You can submit w32api patches to the http://sf.net/projects/mingw bugs
reporting tool.

Earnie.

--
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/

Re: libkernel32.a missing TOOLHELP API exports

[egor duda]

Hi!

Wednesday, 29 May, 2002 Christopher Faylor cgf@redhat.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@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?

CF> Either or both of

CF> cygwin-patches@cygwin.com and mingw-dvlpr@sourceforge.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@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@logos-m.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/

RE: libkernel32.a missing TOOLHELP API exports

[Steven Edwards]

> Process32First@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.

The toolhelp apis exist on both Win98, 2k and XP. They are part of
kernel32.dll but are developed using a separate import lib (libth32.lib
under VS6). I didn't think that libth32.a existed in the w32api package
before I sent the email. Now the only question is if it is still the
same for Visual Studio.Net or did the move the th32 import information
to kernel32? If M$ did change it then we should also.

Thanks
Steven 

"Every revolution was once a thought in one man's mind"
- Ralph Waldo Emerson 


--
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/

Re: libkernel32.a missing TOOLHELP API exports

[Christopher Faylor]

On Wed, May 29, 2002 at 09:59:17AM -0400, Steven Edwards wrote:
>> Process32First@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.
>
>The toolhelp apis exist on both Win98, 2k and XP. They are part of
>kernel32.dll but are developed using a separate import lib (libth32.lib
>under VS6). I didn't think that libth32.a existed in the w32api package
>before I sent the email. Now the only question is if it is still the
>same for Visual Studio.Net or did the move the th32 import information
>to kernel32? If M$ did change it then we should also.

If there is precedent for a separate library, then IMO that's what we
should do.

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/

Re: libkernel32.a missing TOOLHELP API exports

[Earnie Boyd]

[-- Attachment #1: Type: text/plain, Size: 168 bytes --]

Please don't send patches to mingw-dvlpr@lists.sf.net.  Such posts will
be rejected.  If you must post to a MinGW mailing list, use
mingw-patches@lists.sf.net.

Earnie.

[-- Attachment #2: cygwin.50889 --]
[-- Type: message/rfc822, Size: 1192 bytes --]

From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: libkernel32.a missing TOOLHELP API exports
Date: Tue, 28 May 2002 17:08:57 -0400
Message-ID: <20020528210857.GA6491@redhat.com>

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


[-- Attachment #3: Type: text/plain, Size: 214 bytes --]

--
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/