Bernd Eckenfels writes ("adns: last problem hcommon.c.m4"):
> Hello Ian, me again :)Thanks for all your work :-). > there is a last problem, hcommon.c.m4 is missing ENOTSOCK, which will cause > a false regression failure. However since it is shipping hcommon.c, it > depends on the file timestamps on which system it will be used. I just > uploaded an 1.1-3 which adds ENOTSOCK to .c.m4. So this means no matter if > the generated or shipped file is used, the tests suceed. I had noticed this myself. It's very silly of me. > However, as already discussed in Bug #236243 it might be good to actually > remove hcommon.c on clean, and/or not ship it? No, I don't think so. I wanted it to be possible to build it even if you had a broken `m4' (or none at all). The build-for-release arrangements are supposed to make sure that the timestamps are correct and I will have to check this since obviously the shipped hcommon.c was out of date. Ian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
