[Off-topic suggestion: you mailer's character-set seems to be
configured incorrectly, in that what should be quotation marks in
GCC's output are encoded as byte value 0xE2, but the message's headers
describe it as ISO-8859-1, a character set in which 0xE2 is "lowercase
a with circumflex"]

>>>>> "DMR" == Dilip Malinur Ramesh <[EMAIL PROTECTED]> writes:

DMR> Hi,
DMR> I have checked out Valgrind code from SVN. 

DMR> I am trying to add a dummy tool. I am referring "Writing New
DMR> Tool" section of the user manual.

DMR> I am successful with aclocal, autoheader, automake autoconf and
DMR> configure stages, "Make install" is exiting after generating
DMR> following errors:

DMR> In file included from pub_core_debuglog.h:50,
DMR>                  from launcher.c:48:
DMR> ../include/pub_tool_basics.h:47:31: error: libvex_basictypes.h:
DMR> No such file or directory

The header file libvex_basictypes.h is a necessary part of the VEX
library, and you won't be able to compile without it. If you have a
correctly checked-out copy of the source code, there should be a "VEX"
subdirectory under "valgrind", and this header file should be
"VEX/pub/libvex_basictypes.h". VEX is kept in a separate repository
that's linked to the Valgrind repository as an "externals definition";
recent versions of subversion should check it out for you
automatically, but perhaps you need to upgrade, or check it out
separately. Or, if you do have that file, something about the
configuration processes is giving you the wrong include paths.

DMR> In file included from pub_core_debuglog.h:50,
DMR>                  from launcher.c:48:
DMR> ../include/pub_tool_basics.h:77: error: expected "=", ",", ";", "asm" or 
"__attribute__" before "Off64T"
DMR> ../include/pub_tool_basics.h:92: error: expected "=", ",", ";", "asm" or 
"__attribute__" before "ThreadId"
DMR> ../include/pub_tool_basics.h:119: error: expected specifier-qualifier-list 
before "Bool"
DMR> In file included from launcher.c:48:
DMR> pub_core_debuglog.h:59: error: expected ")" before "level"
DMR> pub_core_debuglog.h:66: error: expected "=", ",", ";", "asm" or 
"__attribute__" before "vgPlain_debugLog_getLevel"
DMR> pub_core_debuglog.h:73: error: expected ")" before "level"
DMR> pub_core_debuglog.h:80: error: expected "=", ",", ";", "asm" or 
"__attribute__" before "vgPlain_debugLog_vprintf"

I believe the above errors are all side-effects of the missing include
above: GCC is unable to parse other declarations because it is missing
the typedefs in that file.

DMR> In file included from pub_core_libcproc.h:40,
DMR>                  from launcher.c:49:
DMR> ../include/pub_tool_libcproc.h:1: error: stray "\377" in program
DMR> ../include/pub_tool_libcproc.h:1: error: stray "\377" in program
DMR> ../include/pub_tool_libcproc.h:1: error: stray "\377" in program
DMR> ../include/pub_tool_libcproc.h:1: error: stray "\377" in program
DMR> ../include/pub_tool_libcproc.h:1: error: stray "\377" in program

These errors would seem to indicate that the file in question is
corrupted in your copy. I don't think that include file should have
any non-ASCII characters in it.

DMR> Due to some limitation, I have checked out the code in one system
DMR> and had to build it in anther.
DMR> Is the error due to this?

There's no reason why it shouldn't be possible to build the code on a
different machine than you checked it out to. However, since both of
the problems above appear to be about having the incorrect contents of
the source code directories, it seems likely that the way you copied
the files to the build machine is part of the problem you're
having. If you were able to build a release that was distributed as a
compressed .tar file, you might try using a .tar archive to do your
copying.

Hope this helps,

 -- Stephen

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Valgrind-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers

Reply via email to