Marc,
I can probably be persuaded to check for fixed OpenBSD earlier (if we
have a version number that can guarantee a fix, the better). But it
would really help if you showed some minimal cooperation by proving
to me that, as you claimed, the install-sh script (which scriptversion?)
contained a
On Wed, Jan 02, 2008 at 10:48:34PM +0100, Ralf Wildenhues wrote:
> Hello Marc,
>
> Thanks for the report.
>
> * Marc Espie wrote on Thu, Dec 27, 2007 at 05:29:37PM CET:
> > On Thu, Dec 27, 2007 at 05:25:56PM +0100, Marc Espie wrote:
> > > the mkdir -p macro arbitrarily restricts itself to GNU mkd
Hello Marc,
Thanks for the report.
* Marc Espie wrote on Thu, Dec 27, 2007 at 05:29:37PM CET:
> On Thu, Dec 27, 2007 at 05:25:56PM +0100, Marc Espie wrote:
> > the mkdir -p macro arbitrarily restricts itself to GNU mkdir by passing
> > it a --version.
Not arbitrarily.
> > This is a bit offensiv
And yet another problematic package, jpilot fails to install correctly
when built in parallel mode for the same reason.
Even if detecting OpenBSD is not easy, I don't understand why this test
is hardcoded.
In general, most autoconf/automake tests DO set a cache entry, and you
can later rely on th
On Thu, Dec 27, 2007 at 05:25:56PM +0100, Marc Espie wrote:
> the mkdir -p macro arbitrarily restricts itself to GNU mkdir by passing
> it a --version.
>
> This is a bit offensive. On OpenBSD, this particular issue does not exist.
> It was fixed 8 years ago, published as OpenBSD 2.4, and all newer
the mkdir -p macro arbitrarily restricts itself to GNU mkdir by passing
it a --version.
This is a bit offensive. On OpenBSD, this particular issue does not exist.
It was fixed 8 years ago, published as OpenBSD 2.4, and all newer versions
are not affected.
Could we get an OS test and use mkdir on
