[Valgrind-users] Installation on OS X 10.7

2012-06-30 Thread Josh Reese
Hello, I am attempting to install valgrind-3.7.0 on a MacBook Pro with OS X 
Lion (10.7.4) and am experiencing some troubles. 

The output I'm receiving is as follows:
17:56@legolas:.+/valgrind-3.7.0$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether ln -s works... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for ranlib... ranlib
checking for a sed that does not truncate output... /usr/bin/sed
checking for ar... /usr/bin/ar
checking for perl... /usr/bin/perl
checking for gdb... /usr/bin/gdb
checking dependency style of gcc... gcc3
checking for diff -u... yes
checking for a supported version of gcc... ok (4.2)
checking build system type... i386-apple-darwin11.4.0
checking host system type... i386-apple-darwin11.4.0
checking for a supported CPU... ok (i386)
checking for a 64-bit only build... no
checking for a 32-bit only build... no
checking for a supported OS... ok (darwin11.4.0)
checking for the kernel version... Darwin 11.x (11.4.0) / Mac OS X 10.7 Lion
checking for a supported CPU/OS combination... ok (amd64-darwin)
checking for use as an inner Valgrind... no
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking features.h usability... no
checking features.h presence... no
checking for features.h... no
checking the GLIBC_VERSION version... Darwin
checking for CLOCK_MONOTONIC... no
checking for pthread_rwlock_t... yes
checking for PTHREAD_MUTEX_ADAPTIVE_NP... no
checking for PTHREAD_MUTEX_ERRORCHECK_NP... no
checking for PTHREAD_MUTEX_RECURSIVE_NP... no
checking for PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP... no
checking for pthread_mutex_t.__m_kind... no
checking for pthread_mutex_t.__data.__kind... no
checking for Altivec... no
checking for VSX... no
checking for pthread_create@GLIBC2.0()... no
checking for eventfd()... no
checking if gcc accepts -m32... yes
checking if gcc accepts -m64... yes
checking if gcc accepts -mmmx... yes
checking if gcc accepts -msse... yes
checking if gcc accepts -mpreferred-stack-boundary... no
checking if gcc accepts -Wno-pointer-sign... yes
checking if gcc accepts -Wno-empty-body... yes
checking if gcc accepts -Wno-format-zero-length... yes
checking if gcc accepts -Wno-nonnull... yes
checking if gcc accepts -Wno-overflow... yes
checking if gcc accepts -Wno-uninitialized... yes
checking if gcc accepts -Wextra or -W... -Wextra
checking if gcc accepts -fno-stack-protector... yes
checking if gcc accepts --param inline-unit-growth... yes
checking if the linker accepts -Wl,--build-id=none... no
checking if ppc32/64 as supports mtocrf/mfocrf... no
checking if x86/amd64 assembler speaks SSE3... yes
checking if x86/amd64 assembler speaks SSSE3... yes
checking if x86/amd64 assembler supports 'pclmulqdq'... no
checking if x86/amd64 assembler supports 'lzcnt'... no
checking if x86/amd64 assembler speaks SSE4.2... yes
checking for TLS support... no
checking for ANSI C header files... (cached) yes
checking asm/unistd.h usability... no
checking asm/unistd.h presence... no
checking for asm/unistd.h... no
checking endian.h usability... no
checking endian.h presence... no
checking for endian.h... no
checking mqueue.h usability... no
checking mqueue.h presence... no
checking for mqueue.h... no
checking sys/endian.h usability... no
checking sys/endian.h presence... no
checking for sys/endian.h... no
checking sys/epoll.h usability... no
checking sys/epoll.h presence... no
checking for sys/epoll.h... no
checking sys/eventfd.h usability... no
checking sys/eventfd.h presence... no
checking for sys/eventfd.h... no
checking sys/klog.h usability... no

Re: [Valgrind-users] Valgrind on MacBook Pro with OS X Lion

2012-06-30 Thread Josh Reese
Spike, 
Ah, I use homebrew and it looks like it's available through that system. Don't 
know why that didn't occur to me originally. Thanks for giving my brain a jump 
start :)

Cheers,
Josh
On Jun 30, 2012, at 6:23 PM, Spikey Dog wrote:

 Josh,
 
 I have the same system set up - I couldn't get it to install properly until I 
 used MacPorts to install it; if you don't have MacPorts, then I'd suggest it. 
 It will take awhile to install and upgrade, but it makes installation of many 
 UNIX tools much easier. 
 
 I hope that helps.
 
 Thanks,
 
 Spike

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users


Re: [Valgrind-users] Installation on OS X 10.7

2012-06-30 Thread Philippe Waroquiers
On Sat, 2012-06-30 at 18:00 +0100, Josh Reese wrote:
...
 ld: symbol(s) not found for architecture i386
 collect2: ld returned 1 exit status
 make[2]: *** [libmpiwrap-x86-darwin.so] Error 1
 make[1]: *** [all-recursive] Error 1
 make: *** [all] Error 2
 
 If anyone has any experience with this I would be most appreciative.

See
http://comments.gmane.org/gmane.comp.debugging.valgrind/12289

If I understood well: mpi wrappers are only supported in 64 bits.
So, either configure without mpi wrappers (if you do not need them),
or alternatively configure only for 64 bits (--enable-only64bit)

Philippe


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users