|
From: Tom H. <to...@co...> - 2008-05-12 19:31:39
|
Bart Van Assche wrote: > I would like to modify the Valgrind configure.in and Makefile.am files > such that Valgrind can be cross-compiled. One issue I encountered was > that VEX/auxprogs/genoffsets has to be executed while Valgrind is > built. I have modified configure.in locally such that it not only > detects the name of the cross-compiler, but also the path of the > native compiler. I modified various makefiles such that > VEX/auxprogs/genoffsets is built natively. I hope this is safe and > that the output of the genoffsets program does not depend on the CPU > it is run on, but only on the -m32/-m64 flags ? I'm sure Julian will comment, but I think it needs to run on the target processor. > There is one other issue with regard to cross compiling, namely ar > versus ranlib. autoconf only has support for detecting ranlib and not > for detecting ar. Is it safe to replace all references to ar in > Valgrind and VEX makefiles by references to ranlib ? Certainly not - they do completely different things. On any vaguely modern system ranlib is not needed as ar does the necessary magic when updating the library. On really ancient systems you needed to run ranlib after building the archive with ar. Tom -- Tom Hughes (to...@co...) http://www.compton.nu/ |