Subject: Re: can't build latest exiscan package on current
To: Jeremy C. Reed <firstname.lastname@example.org>
From: Dick Davies <email@example.com>
Date: 08/30/2004 08:25:54
* Jeremy C. Reed <firstname.lastname@example.org> [0708 17:08]:
> On Thu, 1 Jul 2004, Dick Davies wrote:
> > > > receive.c:118: error: storage size of `statbuf' isn't known
> > >
> > > > NetBSD lb 2.0E NetBSD 2.0E (LITTLEBIRD) #3: Tue May 4 23:07:32 BST 2004 rasputin@lb:/usr/obj/usr/src/sys/arch/i386/compile/LITTLEBIRD i386
> > >
> > > That NetBSD (since 2.0D) has a different usage of statfs/statvfs(2).
> > >
> > > Several other packages have similar build problems. And there are a few
> > > PRs about it.
Sorry for the huge delay here, I have a fix but need a hand implementing it.
All we need to do is patch a header if we're on current:
rasputin@lb:exim$ diff -u work/exim-4.42/OS/os.h-NetBSD work/exim-4.42/OS/os.h-NetBSD.orig
--- work/exim-4.42/OS/os.h-NetBSD 2004-08-30 08:20:16.000000000 +0100
+++ work/exim-4.42/OS/os.h-NetBSD.orig 2004-08-30 08:19:18.000000000 +0100
@@ -10,6 +10,4 @@
#define os_strsignal strsignal
/* End */
This fixes current builds, but I guess it would break 1.6?
(Any 1.6 users that want ot correct me, you'd be doing me a favour..)
trouble is, I have no idea how to conditionally apply a patch.
My naive implementation would be to check OSVERSION and echo that line
to the end of the header, does that sound OK?
If so, does anyone happen to know when currents STATVFS changed?
In Seattle, Washington, it is illegal to carry a concealed weapon that
is over six feet in length.
Rasputin :: Jack of All Trades - Master of Nuns