[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: automake-1.8.2 and newer fails on FreeBSD 5.x
From: |
Alexandre Duret-Lutz |
Subject: |
Re: automake-1.8.2 and newer fails on FreeBSD 5.x |
Date: |
Sun, 06 Jun 2004 21:58:12 +0200 |
User-agent: |
Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux) |
>>> "Pav" == Pav Lucistnik <address@hidden> writes:
Pav> Heya,
Howdy,
Pav> rev. 1.2.2.3 of automake/m4/mkdirp.m4 introduced a problem for users of
Pav> FreeBSD 5.x, where invocation `mkdir -p --version .` returns error
Pav> $ mkdir -p --version . && echo true
Pav> mkdir: illegal option -- -
Pav> usage: mkdir [-pv] [-m mode] directory ...
Pav> On FreeBSD 4.x it returns 0
Pav> $ mkdir -p --version . && echo true
Pav> true
These shoudn't be a problem. Please run the Automake test-suite
to be sure (see tests/README if something fails).
[...]
Pav> On FreeBSD 5.x
Pav> mkdir_p = $(mkinstalldirs), and mkinstalldirs = $(mkdir_p), this leads
Pav> to recursive variable and build failure.
That's indeed unhealthy :)
mkdir_p is defined by configure, and it can be set to
$(mkinstalldirs) only if the mkinstalldirs script exist in the
package.
$(mkinstalldirs) is defined in Makefile.in when automake.in is
run, and it can be set to $(mkdir_p) only if the mkinstalldirs
does NOT exist.
Also, automake will not install mkinstalldirs by itself. So my
guess is that the person who autoconfiscated the package in
which you observed this somehow managed to put a copy of
mkinstalldirs after automake ran.
Do not do that. Either install mkinstalldirs before running
automake, or do not install it at all (automake no longer
requires it these days; but some other tools might do).
[...]
--
Alexandre Duret-Lutz