Date: Thu, 4 Jan 2001 00:06:39 -0600 (CST) From: Mike Meyer <mwm@mired.org> To: lanehol@bellsouth.net Cc: questions@freebsd.org Subject: Re: vgrind: not found in make buildworld! EEEEKKKK!! Message-ID: <14932.4847.438068.54864@guru.mired.org> In-Reply-To: <106922544@toto.iv>
next in thread | previous in thread | raw e-mail | index | archive | help
lanehol@bellsouth.net types: > I should mention that I found vgrind in /usr/bin but when I type > /usr/bin/vgrind > I get: > /usr/bin/vgrind: not found > > What's up with that? > The permissions are -r-xr-xr-x and I'm logged in as root. > My confusion deepens. Chances are that vgrind is corrupt, or that /bin/csh is broken. See if your system matches the following, and fix it where it doesn't: bash-2.04$ which vgrind /usr/bin/vgrind bash-2.04$ file /usr/bin/vgrind /usr/bin/vgrind: C shell script text executable bash-2.04$ head -1 /usr/bin/vgrind #!/bin/csh -f bash-2.04$ file /bin/csh /bin/csh: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, stripped bash-2.04$ csh % The "not found" is an idiocy in the exec system call - it reports that script executables aren't even when they are if there is a failure in executing the script interpreter. So the shell quite reasonably reports that it can't find that executable on the path, even though the file exists and is executable. Fixing this should also fix your make problem. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14932.4847.438068.54864>