|
From: Tom H. <to...@co...> - 2012-05-18 03:23:36
Attachments:
diffs.txt
|
valgrind revision: 12567
VEX revision: 2329
C compiler: gcc (GCC) 4.3.0 20080428 (Red Hat 4.3.0-8)
Assembler: GNU assembler version 2.18.50.0.6-2 20080403
C library: GNU C Library stable release version 2.8
uname -mrs: Linux 3.3.4-3.fc16.x86_64 x86_64
Vendor version: Fedora release 9 (Sulphur)
Nightly build on bristol ( x86_64, Fedora 9 )
Started at 2012-05-18 03:41:26 BST
Ended at 2012-05-18 04:23:19 BST
Results differ from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... failed
Last 20 lines of verbose log follow echo
Checked out revision 12567.
At revision 2329.
Configuring valgrind ... cd valgrind-new && ./autogen.sh && ./configure --prefix=/tmp/vgtest-1464/2012-05-18/valgrind-new/Inst
running: aclocal
configure.in:1791: warning: macro `AM_COND_IF' not found in library
configure.in:1794: warning: macro `AM_COND_IF' not found in library
running: autoheader
running: automake -a
configure.in:25: installing `./compile'
configure.in:152: installing `./config.guess'
configure.in:152: installing `./config.sub'
configure.in:14: installing `./install-sh'
configure.in:14: installing `./missing'
Makefile.vex.am: installing `./depcomp'
running: autoconf
configure.in:1798: error: possibly undefined macro: AM_COND_IF
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
error: while running 'autoconf'
=================================================
== Results from 24 hours ago ==
=================================================
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... failed
Regression test results follow
== 600 tests, 1 stderr failure, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
memcheck/tests/err_disable4 (stderr)
none/tests/amd64/sse4-64 (stdout)
=================================================
== Difference between 24 hours ago and now ==
=================================================
*** old.short 2012-05-18 04:21:45.743112194 +0100
--- new.short 2012-05-18 04:23:19.911182867 +0100
***************
*** 2,12 ****
Checking out valgrind source tree ... done
! Configuring valgrind ... done
! Building valgrind ... done
! Running regression tests ... failed
! Regression test results follow
!
! == 600 tests, 1 stderr failure, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
! memcheck/tests/err_disable4 (stderr)
! none/tests/amd64/sse4-64 (stdout)
--- 2,25 ----
Checking out valgrind source tree ... done
! Configuring valgrind ... failed
! Last 20 lines of verbose log follow echo
+ Checked out revision 12567.
+ At revision 2329.
+ Configuring valgrind ... cd valgrind-new && ./autogen.sh && ./configure --prefix=/tmp/vgtest-1464/2012-05-18/valgrind-new/Inst
+ running: aclocal
+ configure.in:1791: warning: macro `AM_COND_IF' not found in library
+ configure.in:1794: warning: macro `AM_COND_IF' not found in library
+ running: autoheader
+ running: automake -a
+ configure.in:25: installing `./compile'
+ configure.in:152: installing `./config.guess'
+ configure.in:152: installing `./config.sub'
+ configure.in:14: installing `./install-sh'
+ configure.in:14: installing `./missing'
+ Makefile.vex.am: installing `./depcomp'
+ running: autoconf
+ configure.in:1798: error: possibly undefined macro: AM_COND_IF
+ If this token and others are legitimate, please use m4_pattern_allow.
+ See the Autoconf documentation.
+ error: while running 'autoconf'
|
|
From: Florian K. <br...@ac...> - 2012-05-18 13:00:43
|
It appears, that AM_COND_IF is not available in automake < 1.11 according to this note here: http://lists.gnu.org/archive/html/automake/2010-12/msg00033.html automake 1.11.1 was released Dec 2009 whereas 1.10 which we currently require was released in Oct 2006. My preference would be to not require 1.11.1. It seems there is an easy work around mentioned in that post that we could use. Florian On 05/17/2012 11:23 PM, Tom Hughes wrote: > Checked out revision 12567. > At revision 2329. > Configuring valgrind ... cd valgrind-new && ./autogen.sh && ./configure --prefix=/tmp/vgtest-1464/2012-05-18/valgrind-new/Inst > running: aclocal > configure.in:1791: warning: macro `AM_COND_IF' not found in library > configure.in:1794: warning: macro `AM_COND_IF' not found in library > running: autoheader |
|
From: Dave G. <go...@mc...> - 2012-05-18 13:08:01
|
That's my fault, I didn't realize that AM_COND_IF was substantially more modern than the AM_CONDITIONAL support. I'll write up a patch in a few hours to avoid the AM_COND_IF. -Dave On May 18, 2012, at 8:00 AM CDT, Florian Krohm wrote: > It appears, that AM_COND_IF is not available in automake < 1.11 > according to this note here: > > http://lists.gnu.org/archive/html/automake/2010-12/msg00033.html > > automake 1.11.1 was released Dec 2009 whereas 1.10 which we currently > require was released in Oct 2006. > > My preference would be to not require 1.11.1. It seems there is an easy > work around mentioned in that post that we could use. > > Florian > > > On 05/17/2012 11:23 PM, Tom Hughes wrote: >> Checked out revision 12567. >> At revision 2329. >> Configuring valgrind ... cd valgrind-new && ./autogen.sh && ./configure --prefix=/tmp/vgtest-1464/2012-05-18/valgrind-new/Inst >> running: aclocal >> configure.in:1791: warning: macro `AM_COND_IF' not found in library >> configure.in:1794: warning: macro `AM_COND_IF' not found in library >> running: autoheader > > > ------------------------------------------------------------------------------ > 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-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers |
|
From: Philippe W. <phi...@sk...> - 2012-05-18 13:21:33
|
On Fri, 2012-05-18 at 08:07 -0500, Dave Goodell wrote: > I'll write up a patch in a few hours to avoid the AM_COND_IF. When patch is available, I will test it and commit it asap. Thanks |
|
From: Dave G. <go...@mc...> - 2012-05-18 15:58:32
Attachments:
vg_am_cond_if.patch
|
On May 18, 2012, at 8:22 AM CDT, Philippe Waroquiers wrote: > On Fri, 2012-05-18 at 08:07 -0500, Dave Goodell wrote: >> I'll write up a patch in a few hours to avoid the AM_COND_IF. > When patch is available, I will test it and commit it asap. Patch is attached. I did some testing on darwin with (autoconf, automake, libtool) tuples of (2.67, 1.10, 2.2.6b) and (2.69, 1.12, 2.4.2). The Dave Hart macro I used makes sense to me and generated sensible code in configure during my testing. If that ends up being unsatisfactory for some odd reason then there are at least two other ways to address this problem, including one which does not require any m4 shenanigans. -Dave |
|
From: Philippe W. <phi...@sk...> - 2012-05-18 16:27:34
|
On Fri, 2012-05-18 at 10:58 -0500, Dave Goodell wrote: > On May 18, 2012, at 8:22 AM CDT, Philippe Waroquiers wrote: > > > On Fri, 2012-05-18 at 08:07 -0500, Dave Goodell wrote: > >> I'll write up a patch in a few hours to avoid the AM_COND_IF. > > When patch is available, I will test it and commit it asap. > > Patch is attached. I did some testing on darwin with (autoconf, automake, libtool) tuples of (2.67, 1.10, 2.2.6b) and (2.69, 1.12, 2.4.2). > > The Dave Hart macro I used makes sense to me and generated sensible code in configure during my testing. If that ends up being unsatisfactory for some odd reason then there are at least two other ways to address this problem, including one which does not require any m4 shenanigans. > > -Dave > > Looks not ok with automake 1.10.3 autoconf 2.67 libtool 2.2.6b checking for utimensat... yes checking for process_vm_readv... no checking for process_vm_writev... no ./configure: line 8848: syntax error near unexpected token `VGCONF_OS_IS_LINUX,' ./configure: line 8848: `AM_COND_IF(VGCONF_OS_IS_LINUX,' make: *** [config.status] Error 2 Command exited with non-zero status 2 Philippe |
|
From: Philippe W. <phi...@sk...> - 2012-05-18 16:46:43
|
On Fri, 2012-05-18 at 18:28 +0200, Philippe Waroquiers wrote: > On Fri, 2012-05-18 at 10:58 -0500, Dave Goodell wrote: > > Patch is attached. I did some testing on darwin with (autoconf, automake, libtool) tuples of (2.67, 1.10, 2.2.6b) and (2.69, 1.12, 2.4.2). > Looks not ok with automake 1.10.3 autoconf 2.67 libtool 2.2.6b Looks better once I first apply the patch :). => will commit and check the nightly build ... Thanks Philippe |