Re: [Valgrind-users] pthread_mutexattr_setpshared

[Nicholas N. <nj...@ca...>]

On Thu, 3 Jul 2003, Matt Peebles wrote:

> I changed the code in vg_libpthread.c and vg_libpthread_unimp.c, but
> when I compile it I get the following:
>
> make  all-recursive
> make[1]: Entering directory `/usr/src/valgrind-1.9.6'
> Making all in coregrind
> make[2]: Entering directory `/usr/src/valgrind-1.9.6/coregrind'
> Making all in demangle
> make[3]: Entering directory `/usr/src/valgrind-1.9.6/coregrind/demangle'
> g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../coregrind -I../../include     -Winline -Wall -Wshadow -O -fomit-frame-pointer -g -Wno-unused -Wno-shadow -c cp-demangle.c -UHAVE_CONFIG_H
> In file included from cp-demangle.c:43:
> ../../coregrind/vg_include.h:1545: variable or field `vgPlain_helper_idiv_64_32
>    ' declared void
> ../../coregrind/vg_include.h:1546: variable or field `vgPlain_helper_div_64_32'
>    declared void

That's odd.  What version of gcc are you using?  Not that knowing that
would help me work out the problem.  Did the same problem occur before you
applied the patch?

I assume that the 'void' errors are causing all the ones that follow.
Maybe try changing the troublesome declarations in vg_include.h from
"extern void" to "extern Int"?  Sure it's a hack, but I can't think what
else to do...

N