|
From: Nicholas N. <nj...@ca...> - 2004-03-16 21:14:56
|
On Tue, 16 Mar 2004, John Roberts wrote: > >That's strange... and the fact that it worked when you added an empty > >Makefile is even stranger... is 'build/' the name of Valgrind's top-level > >directory, from which the install is being done? > > My directory structure has the "build" directory at the same > level as "valgrind-2.1.1", which contains the valgrind sources. > > In "build" I did a "../valgrind-2.1.1/configure --prefix=/export/jroberts/tmp" > > Then, while still in the "build" directory, I typed make. > > Since the error said it was looking for a Makefile in the source > tree, I cd-ed into the source tree (valgrind-2.1.1/coregrind) > and added the empty Makefile to satisfy the depend requirements. > > The build restarted and completed then, when I did "make". Right... we don't normally use separate build/ directories. Interesting that this was required to get it to work... N |