Re: Fwd: SF.net SVN: net-snmp:[18567] trunk/net-snmp/testing/RUNFULLTESTS

2010-05-15 Thread Thomas Anders
Wes Hardaker wrote: It would be easier to simply wrap the older scripts in a giant I have no perl so run this simple sh script instead. Especially since these older scripts have been working without Perl before (and still do in the branches). +Thomas

trunk build errors

2010-05-15 Thread Thomas Anders
SVN trunk (r18754) throws build errors for all of the non-Linux nightly builds. I haven't determined what exact commit(s) broke it, but the configure changes are one likely candidate. E.g. on Solaris, linking libnetsnmp now misses to specify -lnsl. On AIX, linking libnetsnmpagent throws a

Re: trunk build errors

2010-05-15 Thread Bart Van Assche
On Sat, May 15, 2010 at 12:36 PM, Thomas Anders thomas.and...@blue-cable.de wrote: SVN trunk (r18754) throws build errors for all of the non-Linux nightly builds. I haven't determined what exact commit(s) broke it, but the configure changes are one likely candidate. E.g. on Solaris, linking

Re: SF.net SVN: net-snmp:[18726] trunk/net-snmp/ltmain.sh

2010-05-15 Thread Bart Van Assche
On Fri, May 14, 2010 at 9:10 PM, Thomas Anders thomas.and...@blue-cable.dewrote: Revision: 18726 http://net-snmp.svn.sourceforge.net/net-snmp/?rev=18726view=rev Author: bvassche Date: 2010-05-14 08:42:19 + (Fri, 14 May 2010) Log Message: --- libtool bug fix:

make test in trunk broken for srcdir!=builddir

2010-05-15 Thread Thomas Anders
In the nightly builds make test fails with fulltests/temptests/T001snmpv1get_olducd.t: No such file or directory at /my/src/net-snmp-5.6svn/testing/RUNFULLTESTS line 389. The nightly build systems have two things in common: - no TAP::Harness - the build happens outside the source dir

Re: make test in trunk broken for srcdir!=builddir

2010-05-15 Thread Thomas Anders
Thomas Anders wrote: In the nightly builds make test fails with fulltests/temptests/T001snmpv1get_olducd.t: No such file or directory at /my/src/net-snmp-5.6svn/testing/RUNFULLTESTS line 389. Hopefully fixed in r18756. +Thomas