Hello Harlan, Paul,
* Harlan Stenn wrote on Wed, Nov 07, 2007 at 02:00:15AM CET:
On Tue, 2007-11-06 at 19:46 +, Harlan Stenn wrote:
I'm getting bitten by the VPATH-handling differences between FreeBSD's
make and gmake.
The automake manual says (somewhere) that the only version of
Hey folks,
I found the code I was using to detect broken vpath support.
The culprits seemed to be:
*-*-irix6.2 (and later. ie, *-*-irix6.1* was OK)
solaris2.5.1
*-*-unicosmp
And just to reaffirm, I agree with Ralf that the particular issue has to
do with the way FreeBSD avoids (as I
I'm getting bitten by the VPATH-handling differences between FreeBSD's
make and gmake.
I have a .y file and I currently distribute the bison-generated .[ch]
files in the distribution.
On a stock FreeBSD machine (at least) when doing a build outside of the
source tree, FreeBSD's make doesn't see
On Tue, 2007-11-06 at 19:46 +, Harlan Stenn wrote:
I'm getting bitten by the VPATH-handling differences between FreeBSD's
make and gmake.
The automake manual says (somewhere) that the only version of make that
correctly supports out-of-the-tree builds is GNU make. The VPATH
capability in
Paul,
Thanks for your response.
On Tue, 2007-11-06 at 19:46 +, Harlan Stenn wrote:
I'm getting bitten by the VPATH-handling differences between FreeBSD's
make and gmake.
The automake manual says (somewhere) that the only version of make that
correctly supports out-of-the-tree builds
On Wed, 2007-11-07 at 01:00 +, Harlan Stenn wrote:
IME, that position is excessive. It was true, as far as I can recall,
for SGI's make, but this is the first time this particular issue has
bitten me (or any of the users of the package) in a *long* time.
Hm. Maybe automake works around
