Re: [hosers-talk] jon scratches his dandruffy head

[Joel Uckelman <uckelman@xxxxxxxxx>]

Thus spake "Jon Stewart":
> > > Anyone know what gives?
> > 
> > Make determines whether a target should be remade by looking at the 
> > modification dates of the files that it depends on. Take a look at the
> > Makefile and see what install depends on, and then 'touch' at least one of
> > those files. That should coax it to install.
> 
> 
> Okay, here are what look to be relevant snippets of Makefile (disclaimer: 
> I don't know make):
> 
[snip]

>  ---
> 
> Ok, I neither know make nor shell, but there are some suspicious things 
> here. INSTALL, INSTALL_PROGRAM, and INSTALL_DATA are not referenced 
> at all in the makefile after they're defined. So, that seems retarded.

configure creates most of the Makefile, and it puts some stuff in that isn't
necessary for all builds.

> And 
> I really don't understand why we're doing the same shit as the 
> all-recursive target (except using $@ instead of all).

$@ is an automatic variable that holds the name of the make target. When you
'make install', make does a 'make install' in all of the specified 
subdirectories. Contrast that with the all-recursive target: it does a 'make
all' in those same subdirs, not a 'make all-recursive'. So the same target
won't work for both. 

I think you should try the build process again, but do a 'make superclean'
first.

BTW, how'd you get a CS degree without learning how to use make? :)

_______________________________________________
hosers-talk mailing list
hosers-talk@xxxxxxxxxxx
http://lists.ellipsis.cx/mailman/listinfo/hosers-talk