|
From: Thomas L. <tho...@jr...> - 2005-09-15 07:16:02
|
Hi all, Sorry if it is a studip question: I installed Valgrind 3.0.1 on a Linux x86 2.4.20-xxx kernel. I works allright (but I only use memcheck on "classical" software). I saw in the configure script that the Kernel version (2.4 vs 2.6) was (perhaps) of relevance (Line 170 to 192 in configure.in). What happens if I compile and boot on a 2.6 kernel: do I have to re-install Valgrind? Thank you Thomas |
|
From: Tom H. <to...@co...> - 2005-09-15 07:26:17
|
In message <432...@jr...>
Thomas Lavergne <tho...@jr...> wrote:
> Sorry if it is a studip question:
> I installed Valgrind 3.0.1 on a Linux x86 2.4.20-xxx kernel. I works
> allright (but I only use memcheck on "classical" software). I saw in
> the configure script that the Kernel version (2.4 vs 2.6) was
> (perhaps) of relevance (Line 170 to 192 in configure.in).
>
> What happens if I compile and boot on a 2.6 kernel: do I have to
> re-install Valgrind?
The KERNEL_2_4 and KERNEL_2_6 defines are not currently used
anywhere so there should be no difference in the built code and
it should run find on a 2.6 kernel.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Thomas L. <tho...@jr...> - 2005-09-15 12:16:22
|
Tom Hughes wrote: >In message <432...@jr...> > Thomas Lavergne <tho...@jr...> wrote: > > > >>Sorry if it is a studip question: >>I installed Valgrind 3.0.1 on a Linux x86 2.4.20-xxx kernel. I works >>allright (but I only use memcheck on "classical" software). I saw in >>the configure script that the Kernel version (2.4 vs 2.6) was >>(perhaps) of relevance (Line 170 to 192 in configure.in). >> >>What happens if I compile and boot on a 2.6 kernel: do I have to >>re-install Valgrind? >> >> > >The KERNEL_2_4 and KERNEL_2_6 defines are not currently used >anywhere so there should be no difference in the built code and >it should run find on a 2.6 kernel. > >Tom > > > Thank you. That settles it! BTW, I had problems in installing Valgrind, because I tried to use a "gcc-like" installation (mkdir objdir;cd objdir;srcdir/configure --prefix=objdir ...) 1) the VEX library is by default taken to `pwd` (that was objdir/VEX and not srcdir/VEX) so I had to say --with-vex=srcdir/VEX 2) I wanted to use --prog-suffix=-3.0.1 (to get an executable valgrind-3.0.1), but at linking time (I think) the run-time-libraries (.so) where not created in a consistent manner: I think I remember make was searching for (e.g. vg_memcheck-3.0.1.so) but vg_memcheck.so had been created. 3) Finally, would not it be better if we could have a --with-db= on the configugre line? I did edit config.h before compiling to have db to point to /usr/local/bin/gdb-6.3. I know one can always have a valgrindrc to fix these things. I have no experience with editing the *.in files for autoconf/automake. I do not think I am able to help for points 1 and 2. However, I guess 3) can be done easily... should I give it a try? Thomas |
|
From: Tom H. <to...@co...> - 2005-09-15 13:12:44
|
In message <432...@jr...>
Thomas Lavergne <tho...@jr...> wrote:
> 1) the VEX library is by default taken to `pwd` (that was objdir/VEX
> and not srcdir/VEX) so I had to say --with-vex=srcdir/VEX
Can you raise a bug for this please and I'll see what I can do.
> 2) I wanted to use --prog-suffix=-3.0.1 (to get an executable
> valgrind-3.0.1), but at linking time (I think) the run-time-libraries
> (.so) where not created in a consistent manner: I think I remember
> make was searching for (e.g. vg_memcheck-3.0.1.so) but vg_memcheck.so
> had been created.
There is already a bug for this but I haven't managed to come up with
a fix yet - the problem is that we use a PROGRAMS target to create and
install shared libraries which causes them to get the suffix added
which is probably wrong.
I haven't come up with any other way to create shared libraries
without using libtool though.
It's a fairly minor issue though, and will become even more so once we
have proper dual architecture support in the amd64 build so I'm not
too worried about it.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Nicholas N. <nj...@cs...> - 2005-09-15 14:22:29
|
On Thu, 15 Sep 2005, Tom Hughes wrote:
>> 1) the VEX library is by default taken to `pwd` (that was objdir/VEX
>> and not srcdir/VEX) so I had to say --with-vex=srcdir/VEX
>
> Can you raise a bug for this please and I'll see what I can do.
I've improved this situation recently. The below diff for the trunk makes
VPATH builds work again.
Nick
Index: configure.in
===================================================================
--- configure.in (revision 4644)
+++ configure.in (working copy)
@@ -20,7 +20,7 @@
[AC_MSG_ERROR([Directory '$withval' does not exist, or does not
contain Vex])])
],
[
- VEX_DIR=`pwd`/VEX
+ VEX_DIR='$(top_srcdir)/VEX'
])
AC_SUBST(VEX_DIR)
|
|
From: Thomas L. <tho...@jr...> - 2005-09-15 14:30:19
|
I am no expert but it should do ok with this patch. I won't fill a bug-report. (I cannot find my bugzilla password ;-)) What about the --with-db= to point to the debugger software at configure time? Thomas Nicholas Nethercote wrote: > On Thu, 15 Sep 2005, Tom Hughes wrote: > >>> 1) the VEX library is by default taken to `pwd` (that was objdir/VEX >>> and not srcdir/VEX) so I had to say --with-vex=srcdir/VEX >> >> >> Can you raise a bug for this please and I'll see what I can do. > > > I've improved this situation recently. The below diff for the trunk > makes VPATH builds work again. > > Nick > > > > Index: configure.in > =================================================================== > --- configure.in (revision 4644) > +++ configure.in (working copy) > @@ -20,7 +20,7 @@ > [AC_MSG_ERROR([Directory '$withval' does not exist, or does > not contain Vex])]) > ], > [ > - VEX_DIR=`pwd`/VEX > + VEX_DIR='$(top_srcdir)/VEX' > ]) > AC_SUBST(VEX_DIR) > > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download it for free - -and be entered to win a 42" plasma tv or your > very > own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > |
|
From: Nicholas N. <nj...@cs...> - 2005-09-15 15:27:42
|
On Thu, 15 Sep 2005, Thomas Lavergne wrote: > What about the --with-db= to point to the debugger software at configure > time? I guess it wouldn't hurt, but it doesn't seem very important since (a) no-one else has mentioned it before and (b) you can control it via the command line. Nick |