[10] in SIPB_Linux_Development

home help back first fref pref prev next nref lref last post

Making mh

daemon@ATHENA.MIT.EDU (ghudson@athena.mit.edu)
Mon Jul 5 02:21:20 1993

From: ghudson@athena.mit.edu
Date: Fri, 14 May 93 08:03:20 -0400
To: linux-dev@athena.mit.edu



Ugh.  I have to congratulate the authors of mh for making a simple
job as complicated as possible.

I rewrote the offensive piece of code in getfld.c, but now there seems
to be a problem with the makefiles.  It's not clear to me how these
makefiles were generated, but they seem to be intent on relinking
every executable each time they run, using rules like:

	ap:	xap

	xap:	ap.o trmsbr.o $(LIBS)
		$(LD) $(LDFLAGS) -o $@ ap.o trmsbr.o $(LDLIBS) $(LDCURSES)

(Curses?  Why on earth are they using curses?)

Anyway, whatever generated the makefile is putting a $@ where it
should be putting (in this case) ap.  Rather than make ap, this
creates xap and then tries to use its default rule for making ap from
ap.o, which involves linking ap.o and xap together.  This is rather
spectacular.

For now, I'm trying copying xap to ap and so forth (there are at least
two dozen of these files).  It'd be sort of neat to have makefiles
that work, though.  Does anyone know how they were created?

--GBH


home help back first fref pref prev next nref lref last post