Hi Dan,
Am Dienstag, 30. Dezember 2008 19:48:52 schrieb Dan Fandrich:
> The autocurl script does something similar, in case you haven't seen it
> already: http://curl.haxx.se/auto/autocurl.txt
whoups! Of course not - blind on both eyes, as usual, smile.....
Thanks! Already playing with it....

Two other things regarding autobuilds:
my SuSE hosts have named the default IPv6 entry in /etc/hosts ipv6-localhost
instead of ip6-localhost as the testsuite assumes; do you have any idea how
we probably can support both? I've seen a resolve call there, may this can be
extended to test for both? I also tried to add the ip6-localhost, but now get
another error:
http://curl.haxx.se/auto/log.cgi?id=20081230210353-26217#prob1

this build has same 'cant resolve ip6-localhost' as I had before:
http://curl.haxx.se/auto/log.cgi?id=20081230143209-6638
and this too:
http://curl.haxx.se/auto/log.cgi?id=20081230102420-16550
so there seem to be other platforms too which dont have ip6-localhost...

strange though that on all these we see:
TESTINFO: "Resolving IPv6 'ip6-localhost' didn't work" 2 times (241, 1083)
but now with my recent build 252 fails?

the other thing is that it seems to me that something of the testsuite runs to
early, probably buildconf? I've seen some ?*.m4 during cvs update, and I
thought that any action should take place only in the copied build-dir, and
not in the cvs tree? I could swear that I saw this directly after a fresh
checkout, so impossible that I manually did a build inside the cvs tree;
the build logs though seem to filter these things out....
or is this all normal, and we must add these *.m4 files to .cvsignore?

greetz, Gün.
Received on 2008-12-31