Subject: Re: Detecting statvfs without autoconf
To: Christoph Kaegi <firstname.lastname@example.org>
From: Julio M. Merino Vidal <email@example.com>
Date: 01/06/2006 17:43:53
On 1/6/06, Quentin Garnier <firstname.lastname@example.org> wrote:
> On Fri, Jan 06, 2006 at 04:55:56PM +0100, Hubert Feyrer wrote:
> > 3) Reading that, you see that the change was not present with 200030000
> > and went in with 200040000.
> > Which is what I wrote in my original mail.
> Except it is not convenient to test for that, as 2.1 is 201000000,
> because of the number dance we did after 2.0 release. (2.1 doesn't have
> That's why I think pkgsrc tests after 2.99.9, which was the first
> re-numbered version. That effectively means support for 2.0D to 2.0H
> was dropped.
And this (all the possible combinations) is why relying on OS names and
versions to detect specific features brings all kinds of problems when
porting an application to a "new" platform (in this case, a new NetBSD
You (the starter of this thread) should really consider using autoconf
(or any other method, in case you hate autoconf) to automatically detect
whether to use statfs or statvfs and how. The following talk about this
a bit more:
Julio M. Merino Vidal <email@example.com>
The Julipedia - http://julipedia.blogspot.com/
The NetBSD Project - http://www.NetBSD.org/