Michael G Schwern wrote:
>Its time for another MakeMaker alpha! This one is mostly VMS fixes though
>I also discovered a conflict with Module::Install and undid an accidental
>change that broken Archive::Zip. As far as I know all outstanding issues
>are resolved, so this is release candidate... oh let's call it 4.
>
>http://www.pobox.com/~schwern/src/ExtUtils-MakeMaker-6.25_08.tar.gz
>
I've found a problem with this on Win32.
Using EU-MM-6.17 (in perl-5.8.6) I can build libwin32-0.191 OK, but
using 6.25 (in bleadperl) or 6.25_08 or even the latest svn (rev 2308)
something doesn't work:
The Win32API::File module in libwin32 uses a file called cFile.pc:
Win32API::File require()'s it as "Win32API/File/cFile.pc".
Using 6.17 I have these bits in the Makefile which accomplish the
necessary copy:
all :: pure_all
$(NOECHO) $(NOOP)
pure_all :: config pm_to_blib subdirs linkext
$(NOECHO) $(NOOP)
pm_to_blib: cFile_pc_to_blib
cFile_pc_to_blib: cFile.pc
@$(PERL) "-I$(INST_ARCHLIB)" "-I$(INST_LIB)" \
"-I$(PERL_ARCHLIB)" "-I$(PERL_LIB)" -MExtUtils::Install \
-e "pm_to_blib({
q[cFile.pc],q[$(INST_ARCHLIB)\Win32API\File\cFile.pc]
},q[$(INST_LIB)\auto])"
@$(TOUCH) cFile_pc_to_blib
However, using 6.25 and later we have these dislocated segments that
don't work together:
all :: pure_all
$(NOECHO) $(NOOP)
pure_all :: config pm_to_blib.ts subdirs linkext
$(NOECHO) $(NOOP)
# For backwards compat with anything that referenced this target.
pm_to_blib: pm_to_blib.ts
$(NOOP)
pm_to_blib: cFile_pc_to_blib
cFile_pc_to_blib: cFile.pc
[... as before ...]
Presumably we need to have:
pm_to_blib.ts: cFile_pc_to_blib
but I'm not sure how to accomplish that.
- Steve
------------------------------------------------
Radan Computational Ltd.
The information contained in this message and any files transmitted with it are
confidential and intended for the addressee(s) only. If you have received this
message in error or there are any problems, please notify the sender
immediately. The unauthorized use, disclosure, copying or alteration of this
message is strictly forbidden. Note that any views or opinions presented in
this email are solely those of the author and do not necessarily represent
those of Radan Computational Ltd. The recipient(s) of this message should
check it and any attached files for viruses: Radan Computational will accept no
liability for any damage caused by any virus transmitted by this email.
