| Subject: | MAP_TARGET in Makefile.PL |
Hello,
Is there any good reason for redefining MAP_TARGET in the Makefile.PL? For instance, App::Staticperl expects MAP_TARGET has default value 'perl'. You may see build log below.
cpan[2]>install IO::Pty
....
All tests successful.
Files=1, Tests=5, 3 wallclock secs ( 0.03 usr 0.00 sys + 0.24 cusr 0.30 csys = 0.57 CPU)
Result: PASS
TODDR/IO-Tty-1.10.tar.gz
/usr/bin/make test -- OK
Running make install
Skip blib/lib/IO/Tty.pm (unchanged)
Skip blib/lib/IO/Tty/Constant.pm (unchanged)
Skip blib/lib/IO/Pty.pm (unchanged)
Probably a static XS module, rebuilding perl
make: *** No rule to make target `perl'. Stop.
rm -f ./perlmain.o ./perlmain.c perltty Makefile.aperl blib/arch/auto/IO/Tty/extralibs.all
TODDR/IO-Tty-1.10.tar.gz
/home/tvv/.staticperl-5.18.1/perl/bin/SP-make-install-make install -- NOT OK
Failed during this command:
TODDR/IO-Tty-1.10.tar.gz : install NO
Ok, what is in Makefile?
$ grep -A5 -B5 makeaperl Makefile
# --- MakeMaker staticmake section:
# --- MakeMaker makeaperl section ---
MAP_TARGET = perltty
FULLPERL = /home/tvv/.staticperl-5.18.1/perl/bin/perl
$(MAP_TARGET) :: static $(MAKE_APERL_FILE)
$(MAKE) $(USEMAKEFILE) $(MAKE_APERL_FILE) $@
So, if I remove MAP_TARGET definition in Makefile.PL all is good. Patch is in attachement.
Ref. to staticperl: http://search.cpan.org/perldoc?staticperl
| Subject: | IO_Tty-01.diff |
--- Makefile.PL.orig 2013-12-23 10:50:43.353559493 +0400
+++ Makefile.PL 2013-12-23 10:51:09.983826393 +0400
@@ -406,7 +406,8 @@
'LIBS' => join(" ", @libs),
'clean' => {'FILES' => 'xssubs.c conf Tty.exp_old log'},
'realclean' => {'FILES' => 'Tty IO-Tty.ppd'},
- 'MAP_TARGET' => 'perltty',
+# staticperl expects MAP_TARGET = perl
+# 'MAP_TARGET' => 'perltty',
'AUTHOR' => 'Roland Giersig <RGiersig@cpan.org>',
'ABSTRACT' => 'Pseudo ttys and constants',
'LICENSE' => 'perl',