Bug#236243: adns: last problem hcommon.c.m4

2006-04-03 Thread Ian Jackson
Bernd Eckenfels writes ("Re: Bug#236243: adns: last problem hcommon.c.m4"): > I havent looked in detail what the m4 does, is it platform specific? wil > lthe result be the same on all linux systems? Otherwise I will enforce the > delete on clean. The m4 is platform-independ

Bug#236243: adns: last problem hcommon.c.m4

2005-12-09 Thread Bernd Eckenfels
On Fri, Dec 09, 2005 at 11:07:10AM +, Ian Jackson wrote: > 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. well... this might be related to the fact that i had patched both in the de

Bug#236243: adns: last problem hcommon.c.m4

2005-12-09 Thread Ian Jackson
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 timestamp

Bug#236243: adns: last problem hcommon.c.m4

2005-12-08 Thread Bernd Eckenfels
Hello Ian, me again :) 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 m