Michael Schwern asked (in response to me): !> 1) coerce the output of the new MakeMaker to put the important !> 'all :' target first. ! !Since 'all' should, in theory, be the first target... what's putting !things in front of it? I know this was discussed before, but I didn't !quite follow. Sounds like something is doing MakeMaker Hackery and !getting it somewhat wrong. Something about ext/util/make_ext?
As it turns out there is an all that is first and perhaps I have mischaracterized the nature of the true problem. From looking at the generated DESCRIP.MMS file I do see that there is first top /^all/, but there is also an erroneus second /^all/ that confuses MMS. Here they are with line numbers from my generated DESCRIP.MMS: 278 # --- MakeMaker top_targets section: 279 280 all :: pure_all manifypods 281 $(NOECHO) $(NOOP) 282 283 pure_all :: config pm_to_blib subdirs linkext 284 $(NOECHO) $(NOOP) [snip] 393 # --- MakeMaker installbin section: 394 395 EXE_FILES = [.bin]instmodsh 396 397 all :: $(INST_SCRIPT)instmodsh 398 $(NOECHO) $(NOOP) 399 400 realclean :: 401 $(RM_F) $(INST_SCRIPT)instmodsh 402 It seems very bizarre that an install type of target is called all rather than depends on all, hence I would suspect an erroneous key<->value switch in a hash structure somewhere. I'll enclose the full descrip.mms in separate email to you personally. (I'll also try to answer your longer previous reply). Peter Prymmer
