|
From: Daniel K. <da...@ke...> - 2004-04-28 22:01:39
|
The current dev snapshot's "make install" behaves badly
in that, even if you have done a 'make' beforehand,
'make install' insists on modifying the build tree.
This is bad because in some environments, root doesn't
have permission to do that. Here's an example error log:
...
make[4]: Entering directory `/home/dkegel/tarballs/valgrind-2.1.1/coregrind'
mkdir -p ../.in_place
for i in valgrind stage2 libpthread.so vg_inject.so; do \
to=../.in_place/$(echo $i | sed 's,libpthread.so,libpthread.so.0,'); \
rm -f $o; \
ln -sf ../coregrind/$i $to; \
done
ln: cannot remove `../.in_place/valgrind': Permission denied
ln: cannot remove `../.in_place/stage2': Permission denied
ln: cannot remove `../.in_place/libpthread.so.0': Permission denied
ln: cannot remove `../.in_place/vg_inject.so': Permission denied
make[4]: *** [all-local] Error 1
I had to chmod 777 .in_place to get 'sudo make install' to work.
Can you please make 'make install' not modify anything in the build
directory if run immediately after a 'make all'?
Thanks!
- Dan
|