Re: [HACKERS] configure in snapshout == configure.in

2000-12-28 Thread Peter Eisentraut
Tom Lane writes: > >> FWIW, I'm running GNU Make version 3.79.1, which is the latest release > >> last I checked. > > > ... but not necessarily the best. :-( > > What do you recommend? IIRC, I updated to this version because it fixed > a bug that was biting me in gmake 3.78.1. 3.76.1 works best

AW: [HACKERS] configure in snapshout == configure.in

2000-12-28 Thread Zeugswetter Andreas SB
> > There is something busted in the snapshots, that leads to a wrong > > configure file. The file is equal to configure.in (not autoconf'ed). > > First noticed shortly before Christmas. > > Last week I tried to do a "make clean" in some subdirectory that's > not cleaned by a toplevel clean -- I

Re: [HACKERS] configure in snapshout == configure.in

2000-12-27 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > when configure.in is older than configure, which is not all that unlikely. Newer than, I think you meant. Yes, that's quite possible just after a "cvs update". > I guess the rule in rserv's makefile needs to be qualified better. Agreed. >> FWIW,

Re: [HACKERS] configure in snapshout == configure.in

2000-12-27 Thread Peter Eisentraut
Tom Lane writes: > Last week I tried to do a "make clean" in some subdirectory that's > not cleaned by a toplevel clean -- I think it was doc/src/sgml, but it > might have been a contrib dir -- and make went absolutely nuts. When > the dust settled I had a toplevel configure file that was identi

Re: [HACKERS] configure in snapshout == configure.in

2000-12-27 Thread Tom Lane
Zeugswetter Andreas SB <[EMAIL PROTECTED]> writes: > There is something busted in the snapshots, that leads to a wrong > configure file. The file is equal to configure.in (not autoconf'ed). > First noticed shortly before Christmas. Last week I tried to do a "make clean" in some subdirectory that

[HACKERS] configure in snapshout == configure.in

2000-12-27 Thread Zeugswetter Andreas SB
There is something busted in the snapshots, that leads to a wrong configure file. The file is equal to configure.in (not autoconf'ed). First noticed shortly before Christmas. Andreas