automake --version
automake (GNU automake) 1.9.2
Written by Tom Tromey <[email protected]>.

Copyright 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.



autoconf (GNU Autoconf) 2.59
Written by David J. MacKenzie and Akim Demaille.

Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


If these are too old, then I'll have to nag my sysadmin to update them... But 
the valgrind website says here:
http://valgrind.org/downloads/repository.html
that I only need versions 1.7...

Amos.



--- On Tue, 4/14/09, Nicholas Nethercote <[email protected]> wrote:

> From: Nicholas Nethercote <[email protected]>
> Subject: Re: [Valgrind-users] can't compile valgrind, fails in make
> To: [email protected]
> Cc: [email protected]
> Date: Tuesday, April 14, 2009, 4:29 PM
> On Wed, Apr 15, 2009 at 8:35 AM, AA
> <[email protected]> wrote:
> >
> > hi -- i've just followed the instructions from the
> valgrind webpage to get the source from SVN, and it's
> failing with the first thing it tries to compile during
> "make" with the error pasted below. I followed
> exactly the instructions on the website, with my only
> modification --prefix=/ul/amosa
> >
> > The only thing suspicious in the preceding steps was
> this summary from the ./configure stage:
> >         Maximum build arch: amd64
> >         Primary build arch: amd64
> >                   Build OS: linux
> >       Primary build target: AMD64_LINUX
> >     Secondary build target: X86_LINUX
> >         Default supp files: exp-ptrcheck.supp
> xfree-3.supp xfree-4.supp glibc-2.X-drd.supp
> glibc-2.34567-NPTL-helgrind.supp glibc-2.3.supp
> >
> > which is odd, because my system is not AMD, it's
> an Intel Dual-Core Xeon Processor 5100 (Woodcrest), 65nm,
> running CentOS 4.5 / RHEL 4... But I can't figure out
> how it drew this conclusion, or how to set it straight,
> assuming this is a problem.
> 
> "AMD64" is just another name for the architecture
> also known as
> "x86-64", it doesn't indicate what company
> made your chip.
> 
> > In file included from m_cpuid.S:31:
> > pub_core_basics_asm.h:42:33: pub_tool_basics_asm.h: No
> such file or directory
> > pub_core_basics_asm.h:45:20: config.h: No such file or
> directory
> > make[3]: *** [libcoregrind_x86_linux_a-m_cpuid.o]
> Error 1
> > make[2]: *** [all] Error 2
> > make[1]: *** [all-recursive] Error 1
> > make: *** [all] Error 2
> 
> I've seen this before, I think it's due to an old
> version of automake
> or autoconf.  What versions of those are you running?
> 
> Nick


      

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to