simons@THINK.COM (04/12/89)
I have a makefile that works using Sun make, but fails with GNU make. I think this may be a GNU bug. Here is the makefile in question: ---------- SHELL=/bin/csh all: -@echo 'header' ; -@echo -n 'enter text: ' ; \ set a=$$< ; echo $$a ; ---------- The problem is that the user never gets a chance to enter a value for the shell variable 'a'...the makefile just cruises right through without stopping. I can workaround this by using the following: ---------- SHELL=/bin/csh all: -@echo 'header' ; \ echo -n 'enter text: ' ; \ set a=$$< ; echo $$a ; ---------- I'd like to hear if you think this is a bug. Thanks. -josh simons
simons@THINK.COM (04/13/89)
I am using GNU make to give me a consistent make interface on both SunOS and Ultrix. I am having trouble with Ultrix and GNU make interacting. I don't really view this as a bug in GNU make...it is Ultrix brain-damage. Can you suggest a workaround for this? I am really wedged. problem: the builtin rule for converting from a .c to a .o in GNU make is something of (roughly) the form: cc -c file.c -o file.o Ultrix barfs on this, believe it or not. It won't let you specify a file with a .o (or a .a) extension for the -o argument. I repeat. This is completely brain-damaged on the part of Ultrix cc. It gives the error message "cc: -o would overwrite file.o" even if there is no file file.o help? -josh simons
simons@THINK.COM (04/13/89)
My apologies for bothering you. I found the NO_MINUS_C_MINUS_O option! Thanks for the foresight! -josh simons