Closed MikeFultonDev closed 2 years ago
Building with ASCII and with EBCDIC (and with 64-bit and without)...
For ascii, a difference shows up: /bin/env LIBPATH=/app/temp/perlport/perl5:/lib:/usr/lib ./miniperl -Ilib configpm written lib/Config.pod updated lib/Config.pm updated lib/Config_heavy.pl /bin/env LIBPATH=/app/temp/perlport/perl5:/lib:/usr/lib ./miniperl -Ilib make_ext.pl cpan/Archive-Tar/pm_to_blib MAKE="make" LIBPERL_A=libperl.so Generating a Unix-style Makefile Writing Makefile for Archive::Tar cp lib/Archive/Tar/Constant.pm ../../lib/Archive/Tar/Constant.pm cp lib/Archive/Tar/File.pm ../../lib/Archive/Tar/File.pm cp lib/Archive/Tar.pm ../../lib/Archive/Tar.pm
vs
/bin/env LIBPATH=/app/temp/perlport/ebcdic/perl5:/lib:/usr/lib ./miniperl -Ilib configpm written lib/Config.pod updated lib/Config.pm updated lib/Config_heavy.pl /bin/env LIBPATH=/app/temp/perlport/ebcdic/perl5:/lib:/usr/lib ./miniperl -Ilib make_ext.pl cpan/Archive-Tar/pm_to_blib MAKE="make" LIBPERL_A=libperl.so Generating a Unix-style Makefile Writing Makefile for Archive::Tar
return qw(av.h config.h cop.h cv.h dosish.h embed.h embedvar.h form.h gv.h handy.h hv.h hv_func.h intrpvar.h iperlsys.h keywords.h mg.h nostdio.h op.h opcode.h pad.h parser.h patchlevel.h perl.h perlio.h perliol.h perlsdio.h
Difference is 'expected' because sort order is by collation sequence - one is EBCDIC and one is ASCII
still not clear why files are being copied only in one case - have to see where copy is done
running the perl debugger is useful. Here is an example: PERLDB_OPTS="N f=2 LineInfo=/tmp/results" /bin/env LIBPATH=/app/temp/perlport/perl5:/lib:/usr/lib ./miniperl -Ilib -I../perl5/dist/PathTools -d make_ext.pl cpan/Archive-Tar/pm_to_blib MAKE="make" LIBPERL_A=libperl.so
The PERLDB_OPTS="N f=2" says to run non-interactive and trace 2 levels (i.e. caller/callee). If you don't specify the LineInfo, it will write to /dev/tty and it's binary (e.g. ascii)
fixed rebasing to 'blead'
Error that there is no rule to build perldoc...