[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: autoconf problem, related to Swish-e install
From: |
Paul Eggert |
Subject: |
Re: autoconf problem, related to Swish-e install |
Date: |
Thu, 23 Sep 2004 12:16:10 -0700 |
User-agent: |
Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) |
Richard Morin <address@hidden> writes:
> Curiously, this behavior is not present under GNU make.
The Autoconf manual says this:
You can support compiling a software package for several architectures
simultaneously from the same copy of the source code. The object files
for each architecture are kept in their own directory.
To support doing this, @command{make} uses the @code{VPATH} variable to
find the files that are in the source directory. @acronym{GNU} Make
and most other recent @command{make} programs can do this. Older
@command{make} programs do not support @code{VPATH}; when using them, the
source code must be in the same directory as the object files.
To support doing this, @command{make} uses the @code{VPATH} variable to
find the files that are in the source directory. @acronym{GNU} Make
and most other recent @command{make} programs can do this. Older
You're running into the problem described above: Sun's implementation
is an "older" make and doesn't support VPATH correctly. To work
around the problem, either use GNU make, or don't put the object files
anywhere other than the source directory.