|
From: Alejandro L. <ja...@gm...> - 2010-05-19 21:04:11
|
Hi Everyone, I have installed in a Quadcore machine Valgrind and it's working. But when I try in this "Intel(R) Xeon(R) CPU E5506" machine, I cannot. Anyone have experience in that architecture or any idea? OS: Ubuntu 9.10, 64 bit Thanks for your time, Regards, -- Alejandro Llanos Fuentes |
|
From: Brad H. <br...@fr...> - 2010-05-19 22:04:00
|
On Thursday 20 May 2010 07:03:43 am Alejandro Llanos wrote: > I have installed in a Quadcore machine Valgrind and it's working. But when > I try in this "Intel(R) Xeon(R) CPU E5506" machine, I cannot. You need to provide more details. Can you not install? Can you install but not start? Can you start but it crashes or appears to otherwise behave incorrectly? What are the errors / warnings that lead you to the "cannot"? Brad |
|
From: Alejandro L. <ja...@gm...> - 2010-05-20 01:47:44
|
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
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-NPTLhelgrind.supp glibc-2.X.supp
---
When I do "make", I think everything is ok.
"
.
.
.
mkdir -p ../.in_place; \
for f in ; do \
rm -f ../.in_place/$f.dSYM; \
ln -f -s ../mpi/$f.dSYM ../.in_place; \
done
make[2]: Leaving directory `/home/allanos/valgrind/valgrind-3.5.0/mpi'
Making all in docs
make[2]: Entering directory `/home/allanos/valgrind/valgrind-3.5.0/docs'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/allanos/valgrind/valgrind-3.5.0/docs'
make[1]: Leaving directory `/home/allanos/valgrind/valgrind-3.5.0'
"
--------
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
make[3]: *** [install-nobase_pkgincludeHEADERS] Error 1
make[3]: Leaving directory `/home/allanos/valgrind/valgrind-3.5.0/include'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory `/home/allanos/valgrind/valgrind-3.5.0/include'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/allanos/valgrind/valgrind-3.5.0'
make: *** [install] Error 2
Any idea?
Thanks,
On Wed, May 19, 2010 at 6:03 PM, Brad Hards <br...@fr...> wrote:
> On Thursday 20 May 2010 07:03:43 am Alejandro Llanos wrote:
> > I have installed in a Quadcore machine Valgrind and it's working. But
> when
> > I try in this "Intel(R) Xeon(R) CPU E5506" machine, I cannot.
> You need to provide more details.
>
> Can you not install?
>
> Can you install but not start?
>
> Can you start but it crashes or appears to otherwise behave incorrectly?
>
> What are the errors / warnings that lead you to the "cannot"?
>
> Brad
>
--
Alejandro Llanos Fuentes
|
|
From: David C. <dcc...@ac...> - 2010-05-20 02:22:07
|
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 dcc...@ac...
Chapman Consulting -- San Jose, CA
|
|
From: Alejandro L. <ja...@gm...> - 2010-05-20 02:02:16
|
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 <dcc...@ac...> 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 dcc...@ac... > Chapman Consulting -- San Jose, CA > > -- Alejandro Llanos Fuentes |
|
From: Julian S. <js...@ac...> - 2010-05-20 07:23:01
|
On Thursday 20 May 2010 04:01:49 Alejandro Llanos wrote: > 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? Doesn't matter. Should run just fine on Intel CPUs. J |