Re: timestamp bug when files are created just before make is run

worry about this problem. That would be safe in that it would have no visible impact, but I'm not inclined to do so unless it would actually be used. Anyone out there who wants it? --thanks, karl.

recipe failed message even if ignored

rtainly don't want to see it. That's why I ignored errors on the command in the first place ... Thanks, Karl P.S. Actually, as I wrote before, I wish there was a way to turn off that new message entirely, but that's a different issue. __

failure anoucement during installation of cinelerra-4.4

Failure:This program built for x86_64-unknown-linux-gnu after running "make install -h" the above mentioned message appears! before I get some different messages as follow: 1.make install -ik make -f build/Makefile.cinelerra install make[1]: Entering directory `/home/heinrich/Downloads/cinelerr

Re: @dircategory for make

ory cleaned up in the same way, but so far have been unable to attract anyone's attention. (I haven't tried for a while.) Thanks, Karl ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make

@dircategory for make

Hi Paul, In make.texi, could you please change @dircategory GNU Packages to @dircategory Software development ? (The goal is to make Info dir categories be the same as the Free Software Directory categories, where possible.) Thanks, Karl ___ Bug

make.texi @dircategory

for GNU manuals. Let me know if questions or problems. Thanks, karl (Texinfo maintainer) *** /usr/local/gnu/src/make-3.80/doc/ORIG/make.texi Wed Sep 18 13:51:58 2002 --- /usr/local/gnu/src/make-3.80/doc/make.texi Sun Mar 9 06:08:27 2003 *** *** 25,31 @c Combine the prog

recursive make considered harmful?

d into the manual. (Unfortunately, for automake/autoconf projects, I'm not sure there's an obvious way to apply these methods, because recursive make is built so deeply into those tools.) Just a suggestion ... karl ___ Bug-make mailing l

make 3.79.1 basename bug with absolute filenames

make 3.79.1, solaris 2.7, compiled with gcc 2.95.2. Here's a two-line GNUmakefile: default: @echo $(basename /src/foo) And here's the output of running it: $ make -f m /src/foo Shouldn't that just be `foo'? Thanks, [EMAIL PROTECTED] ___ Bug-

Configure bug in Make 3.79.1

large file support on HP-UX, but GCC does not. I removed the assertion from "configure", and the program built cleanly. Thanks for your help and all of your good work. A Open Source fan, but unfortunately not a C programmer, Karl ----- Karl Bolingbrok

future is coming too soon

go back to just syncing the clock via rdate every few minutes. I looked at the code in remake.c that generates the message, it would seem you could just have a default adjustment of, say, a tenth of second or something? Thanks, karl ___ Bug-make mailing

*** not correct for time skew

In make's time skew warning message: make[2]: *** Warning: File `file' has modification time in the future (2001-01-16 05:55:30.3184 > 2001-01-16 05:55:30.170387819) I really strongly believe the *** should not be used. This is a warning, not an error. In every other case that I know o

commands commence before first target?

Make 3.79, solaris 2.7. I run make -n on the following Makefile (which is just a long variable assignment). Get following error: Makefile:25: *** commands commence before first target. Stop. Removing a single space from the beginning of the line with changingprivacy.html makes the error go awa

Patch

A patch to make make-3.79.1 really compile with MSC 6. Use at your own discretion. Regards Karl M. Syring make-3.79.1.patch.gz