Yes, sorry, that is a noob error Thanks =)
But now I have a question about you said, Valgrind recognize my processor like a amd64, right?? So, Does it matter? if I want to run Cachegrind for example. Or What other consequences can I have? Regards, On Wed, May 19, 2010 at 9:55 PM, David Chapman <[email protected]> wrote: > Alejandro Llanos wrote: > >> Yes, sorry, you are right. >> >> This is the last part of the output when I do "./configure" >> >> Maximum build arch: amd64 >> Primary build arch: amd64 >> Secondary build arch: x86 >> > > Interesting that "configure" would say you are running on an AMD64 machine > when you are targeting a Xeon. This shouldn't matter, though. Your problem > is below: > > > The problem is when I do the "make install" >> >> $ make install >> make install-recursive >> make[1]: Entering directory `/home/allanos/valgrind/valgrind-3.5.0' >> Making install in include >> make[2]: Entering directory >> `/home/allanos/valgrind/valgrind-3.5.0/include' >> make[3]: Entering directory >> `/home/allanos/valgrind/valgrind-3.5.0/include' >> make[3]: Nothing to be done for `install-exec-am'. >> test -z "/usr/local/include/valgrind" || mkdir -p -- >> "/usr/local/include/valgrind" >> mkdir: cannot create directory `/usr/local/include/valgrind': Permission >> denied >> > > You need to have a privileged account (e.g. root) perform the installation > in /usr/local; the account "allanos" does not have permission to add files > to system directories. > > -- > David Chapman [email protected] > Chapman Consulting -- San Jose, CA > > -- Alejandro Llanos Fuentes
------------------------------------------------------------------------------
_______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
