Re: vine make auxprogs/genoffsets.c problem
Stephen McCamant
JW> Making all in VEX
JW> make[1]: Entering directory `/home/imtl/vine-1.0/VEX'
JW> cc -Wall -g -o auxprogs/genoffsets auxprogs/genoffsets.c
JW> cc: auxprogs/genoffsets.c: No such file or directory
JW> cc: no input files
JW> make[1]: *** [pub/libvex_guest_offsets.h] Error 1
JW> make[1]: Leaving directory `/home/imtl/vine-1.0/VEX'
JW> make: *** [all-recursive] Error 1
JW> I get this error when "sudo make" vine
JW> having trouble figuring this out
JW> need help : (
One meta-answer is that I don't believe you would see this error if
you unpacked a fresh copy of the vine-1.0.tar.gz archive and then
compiled it exactly according to the directions in the manual. When in
doubt it's a good idea to try following directions as closely as
possible, at least when you're trying to compile something for the
first time. Then if you later find that doing something else causes
problems, you always have "don't do that" as a workaround, and looking
at what you did differently may make it easier to understand what went
wrong.
In this case, I believe that the proximate cause of the failure is
that you ran "make clean" in the VEX directory, which also happens
automatically if you run "make clean" in the top-level Vine
directory. When we created the copy of the VEX source code for the
Vine 1.0 release, we copied the generated header file
VEX/pub/libvex_guest_offsets.h, but not the program in the
VEX/auxprogs directory that can be used to recreate that file. The
first time you try to compile, everything works fine, but if you "make
clean" the Makefile will delete the header file, and then when you try
to compile again it will fail in trying to create the header. The
error message you see specifically is when it's trying to compile the
program that it would use to recreate the header file, and the source
code doesn't exist where it expects it.
The easiest workaround is to re-extract the
vine-1.0/VEX/pub/libvex_guest_offsets.h file from the tarball, and
then not to run "make clean" in the top-level or VEX directories.
Another workaround would be to copy an appropriate "auxprogs"
directory into your vine-1.0/VEX tree. You can find the VEX SVN
repository linked to as part of the Valgrind repository at
http://www.valgrind.org/; the version in Vine 1.0 is based on VEX SVN
revision r1856. If you're downloading your own copy of VEX you can
also use it in place of the version in the release by supplying the
--with-vex option to Vine's configure script.
Also, I don't think this is related to your problem, but there should
be no reason to compile Vine as root using "sudo".
Hope this helps,
-- Stephen
Alex Bazhanyuk
I am not sure....