|
From: Nicholas N. <nj...@ca...> - 2004-11-11 19:24:05
|
On Thu, 11 Nov 2004, Kevin Webb wrote: > Thank you for your response. > > It was a virgin install, the following are the sequence > of events. > > Yesterday I clicked on the link (bzip2'd source, 965KB) > -->developer.kde.org/~sewardj/valgrind-2.2.0.tar.bz2 > > transferred the file to the target host, executed bunzip2 > and tar -xvf on the file, cd .../valgrind-2.2.0, read the > README and INSTALL files and went right down the series of > instructions to install - ./configure, make, make check, > and make install (as root). > > Followed by 'valgrind --tool=memcheck ls -al' > with the resulting output I sent to the list. This was a > virgin install and I will say that I had not updated my > LD_LIBRARY_PATH, or PATH variables on yesterday's test. > > Today, to try to rectify the situation I executed a make clean, > followed by a make distclean, and then re-executed the > build/install sequence this time starting with and explicit > ./configure --prefix=/usr/local ... > > After getting the same error message I looked at the FAQ, > looked at the previous postings to the list, did some Google > USENET searches, and fiddled with env variables with no luck. > My last resort was to post the tale of woe to the list. That's really strange. I've never seen this problem before for a clean install. It should only happen if you update part of an existing Valgrind, but not all of it. I've no idea what the problem is. Can you please file a bug report? (See valgrind.kde.org/bugs.html) N |