[Wine] Re: more compile problems

[Joris Huizer]

CrashedAgain wrote:

> gcc -c -I. -I. -I../../include -I../../include  -D__WINESRC__
> -D_USER32_ -D_WINABLE_ -D_REENTRANT -fPIC -Wall -pipe
> -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+
> -Wpointer-arith  -g -O2 -o ../../controls/edit.o ../../controls/edit.c
> ../../windows/winproc.c:1761: warning: pointer targets in passing
> argument 3 of 'MultiByteToWideChar' differ in signedness
> ../../windows/winproc.c:1770: warning: pointer targets in passing
> argument 3 of 'MultiByteToWideChar' differ in signedness
> ../../windows/winproc.c: In function 'WINPROC_MapMsg32ATo16':
> ../../windows/winproc.c:2002: error: invalid lvalue in increment
> ../../windows/winproc.c:2145: error: invalid lvalue in increment
> ../../windows/winproc.c: In function 'WINPROC_MapMsg32WTo16':
> ../../windows/winproc.c:2619: warning: pointer targets in passing
> argument 5 of 'WideCharToMultiByte' differ in signedness
> ../../windows/winproc.c:2625: warning: pointer targets in passing
> argument 5 of 'WideCharToMultiByte' differ in signedness
> ../../windows/winproc.c:2634: warning: pointer targets in passing
> argument 5 of 'WideCharToMultiByte' differ in signedness
> ../../windows/winproc.c:2644: warning: pointer targets in passing
> argument 5 of 'WideCharToMultiByte' differ in signedness
> make[2]: *** [../../windows/winproc.o] Error 1
> make[2]: Leaving directory
> `/mnt/hdb3/home/crashedagain/wine-20040121/dlls/user'
> make[1]: *** [user/__install__] Error 2
> make[1]: Leaving directory
> `/mnt/hdb3/home/crashedagain/wine-20040121/dlls'
> make: *** [dlls/__install-lib__] Error 2
> root at desktop:/mnt/hdb3/home/crashedagain/wine-20040121#
> 


You already had compile problems before and then this? maybe you should 
really get a known-good source (like one of the tarballs from winehq.org)

one suggestion if you want to try more on the source you're using now - 
it sometimes helps to do a 'make distclean' and restart building, if you 
didn't clean up after the last compile error - though normally that 
happens at link time -- these errors are really at compile time, so I 
wouldn't bet on it

HTH,

Joris