Nicholos, apply the following patch to ...mailbox/mailer.c in your mailutils 1.2 source code. This has been fixed in the cvs code already. I am not sure about your cvs problem, but apply the below patch to tarball code and run make... Shouldn't need to reconfig.
Regards, darel henmamn --- mailer.c 2007-08-24 06:18:54.437500000 +0900 +++ mailer.c.fixed 2007-08-24 05:21:00.296875000 +0900 @@ -28,6 +28,8 @@ #include <unistd.h> #include <errno.h> +#include <sys/time.h> + #include <mailutils/address.h> #include <mailutils/debug.h> #include <mailutils/errno.h> ---------------------------------------------------------------- REF: Nicolas Reimen <[EMAIL PROTECTED]> wrote: > Hi Darel, > > I have made some progress. The 0xOD was indeed the source of the problem. I > reinstalled cygwin with the "UNIX line ending" option and the configure script > finished sucessfully (or so it seems). > > But the build still fails. I tried both the current CVS version and the 1.2 > snapshot and they both fail, althought appartently for different reasons. > These > reasons are not vrey obvious to my untrained eye so any help from your part, > or > anyone, is most welcome, as usual. > > Attached are text files containing the full command line message sequence for > both > the current CVS code and the 1.2 snapshot. > > Cheers, > > N. > > On 8/23/07, d.henman <[EMAIL PROTECTED]> wrote: > > Nicolas, > > d.henman <[EMAIL PROTECTED]> wrote: > > > (2) Why do you have <CR>'s, aka \m or 0x0d, codes in your config.log > file? > > This could seriously scew parsing up. > > Are you using a dos type editor to edit the config.log file? > > Actually, configure doesn't use config.log. I checked this. > The CR's are still in there, but.... did they get there by an editting > accident > or during real processing? > > regards, > darel henman > _______________________________________________ Bug-mailutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-mailutils
