public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* cleaning
@ 1999-06-15  8:10 Mike Stump
  1999-06-30 15:43 ` cleaning Mike Stump
  0 siblings, 1 reply; 3+ messages in thread
From: Mike Stump @ 1999-06-15  8:10 UTC (permalink / raw)
  To: egcs

There is a rule to remove *~ in the toplevel makefile when people do a make
clean, this is wrong, wrong, wrong.  See gcc/Makefile for a more
proper place.  If you want me to submit a patch, in what rule do you want
to see them?  Same goes for \#* files as well.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* cleaning
  1999-06-15  8:10 cleaning Mike Stump
@ 1999-06-30 15:43 ` Mike Stump
  0 siblings, 0 replies; 3+ messages in thread
From: Mike Stump @ 1999-06-30 15:43 UTC (permalink / raw)
  To: egcs

There is a rule to remove *~ in the toplevel makefile when people do a make
clean, this is wrong, wrong, wrong.  See gcc/Makefile for a more
proper place.  If you want me to submit a patch, in what rule do you want
to see them?  Same goes for \#* files as well.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* cleaning
@ 2006-11-15  1:39 Mike Stump
  0 siblings, 0 replies; 3+ messages in thread
From: Mike Stump @ 2006-11-15  1:39 UTC (permalink / raw)
  To: GCC Mailing List

While trying to clean, I noticed that

   $ make -k -j6 clean

does:

make[5]: *** [insn-recog.o] Interrupt
make[5]: *** [s-attrtab] Interrupt
make[4]: *** [all-stage1-gcc] Interrupt
make[3]: *** [stage1-bubble] Interrupt
Reaping losing child 0x00383f20 PID 18728
make[2]: *** [all] Interrupt
Removing child 0x00383f20 PID 18728 from chain.
make[1]: *** [stage1-start] Interrupt
make: *** [clean-stage1-libiberty] Interrupt

:-(  Building the entire compile to clean it isn't reasonable, honest.

Comes from:

maybe-clean-stage1-libiberty: clean-stage1-libiberty
clean-stage1: clean-stage1-libiberty
clean-stage1-libiberty:
         @[ -f $(HOST_SUBDIR)/libiberty/Makefile ] || [ -f $ 
(HOST_SUBDIR)/stage1-libiberty/Makefile ] \
           || exit 0 ; \
         [ $(current_stage) = stage1 ] || $(MAKE) stage1-start; \
         cd $(HOST_SUBDIR)/libiberty && \
         $(MAKE) $(FLAGS_TO_PASS)  \
                 CFLAGS="$(STAGE1_CFLAGS)" LIBCFLAGS="$ 
(STAGE1_CFLAGS)"  clean

where we do stage1-start.


Also, now make clean isn't reliable:

$ make -k clean
rm -f stage_current
mv: rename stage1-libdecnumber to prev-libdecnumber/stage1- 
libdecnumber: Directory not empty
make[1]: *** [stage2-start] Error 1
make[1]: *** No rule to make target `clean'.
make: *** [clean-stage2-gcc] Error 2
rm -f *.a TEMP errs core *.o *~ \#* TAGS *.E *.log
make: Target `clean' not remade because of errors.
morgan $ echo $?
2

If I just configure and then do a make clean, it doesn't work either:

rm -f *.a TEMP errs core *.o *~ \#* TAGS *.E *.log
cat: stage_last: No such file or directory
make: invalid option -- a
Usage: make [options] [target] ...
Options:
   -b, -m                      Ignored for compatibility.
[ ... ]
make: Target `clean' not remade because of errors.


:-(


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2006-11-14 23:09 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-06-15  8:10 cleaning Mike Stump
1999-06-30 15:43 ` cleaning Mike Stump
2006-11-15  1:39 cleaning Mike Stump

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).