bug-gnu-utils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gettext makefile bug


From: Richard Pixley
Subject: Re: gettext makefile bug
Date: Mon, 13 Aug 2001 11:59:33 -0700 (PDT)

   X-Coding-System: undecided-unix
   From: Bruno Haible <address@hidden>
   Date: Mon, 13 Aug 2001 20:18:23 +0200 (CEST)
   Cc: address@hidden
   References: <address@hidden>
           <address@hidden>
           <address@hidden>

   After I asked
   >    Would you mind telling which version of 'make' on which platform
   >    you use, to reproduce the problem? And whether you configured with
   >    builddir = srcdir or builddir != srcdir.

   Richard Pixley answers:

   > builddir != srcdir, and "clearmake -C gnu", (gnu make compatibility
   > mode).

   Note that builddir != srcdir requires a 'make' program that supports
   the 'VPATH' variable, says the gettext/INSTALL file.

Yes, I know.  Clearmake uses a hacked version of gnu make as a
preprocessor.

address@hidden> /usr/atria/bin/Gmake --version
Atria Gmake version 3.74
Copyright (C) 1992 Atria Software, Inc.
Copyright (C) 1988, 89, 90, 91, 92, 93, 94, 95 Free Software Foundation, Inc.
This is free software. There is NO warranty; 
not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

It handles VPATH (and vpath) sufficiently for nearly all gnu packages.
I just checked, but 3.74 isn't on ftp.gnu.org anymore, so I can't
really compare.

It's not really a VPATH issue; I think it's a semantic issue.  Since
the target exists in $(srcdir), and is out of date, it is the srcdir
location which is rebuilt with clearmake.  If there is no target file
in srcdir, then clearmake behaves as expected and builds into the
current directory.  I can understand both semantics.

But, *shrug*, I can understand your reluctance to support anything
other than gnu.

--rich



reply via email to

[Prev in Thread] Current Thread [Next in Thread]