On Mon, Apr 25, 2005 at 11:37:00PM -0700, Mike Castle wrote: > The root cause appears to be this: > > bin/ip2cc :: bin/ip2cc.PL > $(PERLRUN) bin/ip2cc.PL bin/ip2cc > > > If I change PERLRUN to PERLRUNINST (like it used to be in 6.17), it works. > > If you test this, make sure you don't have it installed, otherwise it picks > up the installed versions of the files, and it looks like it works.
Yes, that change was deliberate. ------------------------------------------------------------------------ r2332 | schwern | 2005-03-15 01:24:44 -0800 (Tue, 15 Mar 2005) | 4 lines [EMAIL PROTECTED]: schwern | 2005-03-15 01:24:56 -0800 - Fixed a circular dependency on processed PL files introduced as part of RT 6460 in 6.25_02. ------------------------------------------------------------------------ There is essentially two mutually contradicting ways it could work. 1) PL files are processed *after* pm_to_blib is run. If this happens then the .PL file can get at the module being installed. BUT this means that you can't generate something in lib/ and expect it to be copied into blib/lib/. ie. You can't generate a .pm file unless you target blib/lib directly which is undesirable. 2) PL files are processed *before* pm_to_blib is run. Anything you create will be considered for copying into blib. BUT this means you cannot rely on having the uninstalled module in your path. I have opted for #2 as it seems more important and natural to be able to generate any file and MakeMaker treat it as if it was there all along. I've made a small clarification to the PL_FILES docs about this.