build of valgrind 3.7.0 on Leopard fails; gcc version not detected properly

[mrosenstihl@…]

valgrind fails to compile on Leopard with gcc-4.0. The configure script does not detect the gcc version correctly.

This is the relevant part the attached main.log.

:info:configure checking dependency style of /usr/bin/gcc-4.0... gcc3
:info:configure checking for diff -u... yes
:info:configure checking for a supported version of gcc... no (686)
:info:configure configure: error: please use gcc >= 3.0 or clang >= 2.9
:info:configure shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_valgrind/valgrind/work/valgrind-3.7.0" && ./configure --prefix=/opt/local --mandir=/opt/local/share/man --without-mpicc --enable-only32bit " returned error 1
:error:configure Target org.macports.configure returned: configure failure: shell command failed (see log for details)
:debug:configure Backtrace: configure failure: shell command failed (see log for details)
    while executing
"$procedure $targetname"
:info:configure Warning: the following items did not execute (for valgrind): org.macports.install org.macports.configure org.macports.build org.macports.destroot
:notice:configure Log for valgrind is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_valgrind/valgrind/main.log

If one changes in "configure":

5132 gcc_version=`${CC} --version \
5133              | head -n 1 \
5134              | $SED 's/i686-apple-darwin10//' \
5135              | $SED 's/i686-apple-darwin11//' \
5136              | $SED 's/^[^0-9]*\([0-9.]*\).*$/\1/'`

to:

5132 gcc_version=`${CC} --version \
5133              | head -n 1 \
5134              | $SED 's/i686-apple-darwin9//' \
5135              | $SED 's/i686-apple-darwin10//' \
5136              | $SED 's/i686-apple-darwin11//' \
5137              | $SED 's/^[^0-9]*\([0-9.]*\).*$/\1/'`

it works.

[mrosenstihl@…]

main.log of valgrind update

[mf2k (Frank Schima)]

In the future, please Cc the port maintainer(s).

[raimue (Rainer Müller)]

Hm, the configure script also says this:

        # jseward 21 Sept 2011: I seriously doubt whether V 3.7.0 will work
        # on OS X 10.5.x; I haven't tested yet, and only plan to test 3.7.0
        # on 10.6.8 and 10.7.1.  Although tempted to delete the configure
        # time support for 10.5 (the 9.* pattern just below), I'll leave it
        # in for now, just in case anybody wants to give it a try.  But I'm
        # assuming that 3.7.0 is a Snow Leopard and Lion-only release.

Can you tell if valgrind works correctly on Mac OS X 10.5 Leopard?

[mrosenstihl@…]

Replying to raimue@…:

Hm, the configure script also says this:

        # jseward 21 Sept 2011: I seriously doubt whether V 3.7.0 will work
        # on OS X 10.5.x; I haven't tested yet, and only plan to test 3.7.0
        # on 10.6.8 and 10.7.1.  Although tempted to delete the configure
        # time support for 10.5 (the 9.* pattern just below), I'll leave it
        # in for now, just in case anybody wants to give it a try.  But I'm
        # assuming that 3.7.0 is a Snow Leopard and Lion-only release.

Can you tell if valgrind works correctly on Mac OS X 10.5 Leopard?

I hardly use it. Though a test with a small program of mine seems to give reasonable results. If it is not supported on Leopard maybe it should give a warning when installing, or offer an older version. Kind regards, Markus

[raimue (Rainer Müller)]

Is this still an issue with valgrind @3.8.0?

[cooljeanius (Eric Gallager)]

Replying to raimue@…:

Is this still an issue with valgrind @3.8.0?

Wondering the same thing with @3.9.0 now...

[cooljeanius (Eric Gallager)]

Cc Me!

[someuser12]

This is still an issue with valgrind @3.11.0 on Mac OS 10.8.5. (According to #45291, valgrind @3.11.0 should be supported on Mac OS 10.8).

See also #49161.

[someuser12]

Cc Me!

[raimue (Rainer Müller)]

As I got no more feedback for Leopard, assuming this has been fixed.

[mojca (Mojca Miklavec)]

See also #53525.