valgrind for WINE fails to compile

Adam Gundy arg at
Thu Apr 3 09:53:36 CST 2003

At 16:53 03/04/03 +0200, Sylvain Petreolle wrote:
>With your new patch applied to a cvs version of valgrind,
>valgrind fails to compile. I get :
>make[1]: Entre dans le répertoire `/home/valgrind/coregrind'
>source='vg_to_ucode.c' object='vg_to_ucode.o' libtool=no \
>depfile='.deps/vg_to_ucode.Po' tmpdepfile='.deps/vg_to_ucode.TPo' \
>depmode=gcc3 /bin/sh ../depcomp \
>gcc -DHAVE_CONFIG_H -I. -I. -I.. -I./demangle -I../include    
>-DVG_LIBDIR="\"/usr/local/lib"\" -Winline -Wall -Wshadow -O
>-fomit-frame-pointer -mpreferred-stack-boundary=2 -g -c `test -f
>'vg_to_ucode.c' || echo './'`vg_to_ucode.c
>vg_to_ucode.c: Dans la fonction « disInstr »:
>vg_to_ucode.c:4391: valeur de « case » double
>vg_to_ucode.c:4372: précédemment utilisé ici
>vg_to_ucode.c:4410: valeur de « case » double
>vg_to_ucode.c:4391: précédemment utilisé ici
>make[1]: *** [vg_to_ucode.o] Erreur 1
>make[1]: Quitte le répertoire `/home/valgrind/coregrind'
>make: *** [all-recursive] Erreur 1

a (small) part of the valgrind patch has been committed to CVS - I have just updated
the patch on sourceforge to remove this bit. New patch includes Eric Pouech's patch for
the gettid() system call:

Real Programmers don't comment their code. If it was hard to write,
it should be hard to read, and even harder to modify.
These are all my own opinions.

More information about the wine-devel mailing list