Re: make-3.79.1 on glibc-2.1.91 (2)

2000-07-23 Thread Paul Eggert
From: Bruno Haible [EMAIL PROTECTED] Date: Mon, 17 Jul 2000 17:23:34 +0200 (CEST) Here is a patch to convert this 'if' test to a configure time test, thus avoiding the dependency on librt when the function clock_gettime is not really used. That looks like a good approach to work

make 3.79.1 configure shouldn't cache --disable-nsec-timestamps

2000-07-23 Thread Paul Eggert
When configuring GNU make 3.79.1, if I run "configure --disable-nsec-timestamps" and then run "configure" again, the fact that I disabled nsec timestamps in the earlier run is cached. This is inconsistent with the other --disable options. Here's a patch. 2000-07-23 Paul Eggert [EMAIL

Re: make 3.79.1 configure shouldn't cache --disable-nsec-timestamps

2000-07-23 Thread Paul D. Smith
OK, thanks; I didn't realize these settings aren't typically cached. I guess I'm on the fence about this: I can see where caching them could confuse newbies, but it seems like it would annoy slightly more sophisticated users. I guess keeping the newbies less confused is more important. Is

Re: make-3.79.1 on glibc-2.1.91 (2)

2000-07-23 Thread Paul D. Smith
Thanks. -- --- Paul D. Smith [EMAIL PROTECTED] Find some GNU make tips at: http://www.gnu.org http://www.paulandlesley.org/gmake/ "Please remain calm...I may be mad, but I am a

Re: make 3.79.1 configure shouldn't cache --disable-nsec-timestamps

2000-07-23 Thread Paul Eggert
Date: Sun, 23 Jul 2000 20:33:27 -0400 (EDT) From: "Paul D. Smith" [EMAIL PROTECTED] Is there anything about this in the GNU standards? Not that I can see. The GNU standards don't talk about the cache. But the tradition is pretty clear. E.g. "configure --disable-nls" isn't cached. I