Bug 211214

Summary:	Valgrind autoconf finds wrong install script on Mac OSX 10.5
Product:	[Developer tools] valgrind	Reporter:	Chris Pettitt <cpettitt>
Component:	general	Assignee:	Rhys Kidd <rhyskidd>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	pjfloyd, rhyskidd
Priority:	NOR
Version:	3.5.0
Target Milestone:	---
Platform:	Compiled Sources
OS:	macOS
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Chris Pettitt 2009-10-20 16:46:17 UTC

On Mac OSX 10.5, "sudo make install" fails with the following error:

test -z "/usr/local/lib/valgrind" || /Users/cpettitt/downloads/valgrind-3.5.0/install-sh -d "/usr/local/lib/valgrind"
 /local/ant/bin/install -c -m 644 'libvex-x86-darwin.a' '/usr/local/lib/valgrind/libvex-x86-darwin.a'
/bin/sh: /local/ant/bin/install: Permission denied
make[4]: *** [install-pkglibLIBRARIES] Error 126
make[3]: *** [install-am] Error 2
make[2]: *** [install] Error 2
make[1]: *** [install-recursive] Error 1
make: *** [install] Error 2

It appears that ./configure picked up the wrong "install" (ant's install documentation, which is not executable). Modifying config.status and Makefile to point to the correct install binary, in /usr/bin, allowed the install to continue successfully.

For what it's worth, I haven't had configure choose install incorrectly for other projects I've compiled. A specific example I can think of recently is wireshark.

Potentially, some relevant details:

> uname -a
Darwin cpettitt 9.5.0 Darwin Kernel Version 9.5.0: Wed Sep  3 11:29:43 PDT 2008; root:xnu-1228.7.58~1/RELEASE_I386 i386

> echo $PATH
/Users/cpettitt/bin:/Users/cpettitt/Dropbox/bin:/Users/cpettitt/.cabal/bin:/usr/texbin:/local/ant/bin:/usr/local/bin:/opt/local/bin:/usr/bin:/bin:/usr/local/sbin:/opt/local/sbin:/usr/sbin:/sbin

I suspect that this issue is related to the fact that /local/ant/bin comes earlier in my path than /usr/bin. Configure should probably check that the "install" it finds has the executable bit set.

Comment 1 Rhys Kidd 2015-07-13 01:50:43 UTC

Hello Chris,
Apologies that wasn't responded to early.
At present OS X 10.5 is very old. Whilst we haven't formally adopted to no longer support Valgrind on that platform, it is unlikely to see much further developer time dedicated to it. For instance, I have development systems back to OS X 10.7, but not earlier.

Is it possible for you to upgrade to a more recent OS X release, that is still supported by Apple?

We do not see this autoconf issue with modern autotools, OS X and Valgrind SVN trunk.

Comment 2 Paul Floyd 2022-05-20 10:54:57 UTC

This is now just too old to deal with.