valgrind{,-devel} +gcc48 +openmpi not building on mountain lion

[Russell-Jones-OxPhys (Russell Jones)]

The ports

openmpi-default @1.7.4_0+gcc48+threads (active)
openmpi-gcc48 @1.7.4_0+fortran+threads (active)
dragonegg-3.3-gcc-4.8 @3.3_5 (active)
gcc48 @4.8.2_0 (active)

are installed. I've followed the license step at #39762. Logs for valgrind and valgrind-devel installed.

The error seems to be

/opt/local/bin/gcc-mp-4.8 -DHAVE_CONFIG_H -I. -I..  -I.. -I../include -I../VEX
/pub -DVGA_amd64=1 -DVGO_darwin=1 -DVGP_amd64_darwin=1 -DVGPV_amd64_darwin_van
illa=1 -I../coregrind -DVG_LIBDIR="\"/opt/local/lib/valgrind"\" -DVG_PLATFORM=
"\"amd64-darwin\"" -I/opt/local/include  -arch x86_64 -O2 -g -Wall -Wmissing-p
rototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations 
-Wno-format-zero-length -fno-strict-aliasing -fno-builtin -mmacosx-version-min
=10.5 -fno-stack-protector  -Wno-long-long -pipe -Os -Wwrite-strings -fno-stac
k-protector -MT libcoregrind_amd64_darwin_a-m_tooliface.o -MD -MP -MF .deps/li
bcoregrind_amd64_darwin_a-m_tooliface.Tpo -c -o libcoregrind_amd64_darwin_a-m_
tooliface.o `test -f 'm_tooliface.c' || echo './'`m_tooliface.c
m_syscall.c:534:1: error: unknown type name '__private_extern__'
 __private_extern__ UWord 
 ^
m_syscall.c:535:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'do_syscall_unix_WRK'
 do_syscall_unix_WRK ( UWord a1, UWord a2, UWord a3, /* rdi, rsi, rdx */
 ^
m_syscall.c:558:1: error: unknown type name '__private_extern__'
 __private_extern__ UWord 
 ^
m_syscall.c:559:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'do_syscall_mach_WRK'
 do_syscall_mach_WRK ( UWord a1, UWord a2, UWord a3, /* rdi, rsi, rdx */
 ^

[seanfarley (Sean Farley)]

@raimue, I have the fix for this and other things about the valgrind{,-devel} ports. Would you mind if I add 'openmaintainer' to these ports and combine them into one portfile using subport for valgrind-devel?

[raimue (Rainer Müller)]

Replying to sean@…:

@raimue, I have the fix for this and other things about the valgrind{,-devel} ports. Would you mind if I add 'openmaintainer' to these ports and combine them into one portfile using subport for valgrind-devel?

No objections at all! I added openmaintainer in r118752. As I am on Mavericks, valgrind isn't that useful to me at the moment anyway...

[dstrubbe (David Strubbe)]

This appears to have been fixed in r118773.

[raimue (Rainer Müller)]

Indeed, marking as fixed.