perl5.38 @5.38.2 builds, tests, and installs quite fine on PPC Tiger, Mac OS X 10.4.11, and could become the new standard (since 5.36 does not build due to -rpath)

[ballapete (Peter "Pete" Dyballa)]

The test results are:

Failed 3 tests out of 2609, 99.89% okay.
	../cpan/ExtUtils-Constant/t/Constant.t
	../cpan/ExtUtils-MakeMaker/t/02-xsdynamic.t
	../cpan/ExtUtils-MakeMaker/t/04-xs-rpath-darwin.t

The detailed list is hopefully recorded in main.log. Right now the advertised env DYLD_LIBRARY_PATH=pwd:/opt/local/lib:/usr/lib ./perl harness test is running.

Almost no Perl modules support this second to last Perl version. This situation needs an improvement.

[ballapete (Peter "Pete" Dyballa)]

Main.log from PPC Tiger, Mac OS X 10.4.11, testing Perl 5.38

[ryandesign (Ryan Carsten Schmidt)]

Replying to ballapete:

Almost no Perl modules support this second to last Perl version. This situation needs an improvement.

I believe the lack of p5.36 and p5.38 modules is covered by #67830.

[ballapete (Peter "Pete" Dyballa)]

Main.log from PPC Tiger, Mac OS X 10.4.11, testing Perl 5.38

[ballapete (Peter "Pete" Dyballa)]

Main.log from PPC Tiger, Mac OS X 10.4.11, testing Perl 5.34

[ballapete (Peter "Pete" Dyballa)]

Manually performed './perl harness' with Perl 5.38

[ballapete (Peter "Pete" Dyballa)]

Manually performed './perl harness' with Perl 5.34

[ballapete (Peter "Pete" Dyballa)]

Excerpt results from 'port test perl5.38'

[ballapete (Peter "Pete" Dyballa)]

Excerpt results from 'port test perl5.34'

[ballapete (Peter "Pete" Dyballa)]

The tests port performs on Perl 5 contain unnecessary errors because inadequate compiler options are used:

cc1: error: unrecognized command line option "-Wc++-compat"
cc1: error: unrecognized command line option "-Werror=declaration-after-statement"
cc1: error: unrecognized command line option "-Werror=pointer-arith"
cc1: error: unrecognized command line option "-Wno-error=implicit-function-declaration"

Can these be removed on Tiger?

(I am preparing a comparison of test results on PPC Toiger, and later Leopard, from Perl 5.3{4,8}. This will show where these are used.)

[ballapete (Peter "Pete" Dyballa)]

On PPC Tiger, Mac OS X 10.4.11, in the end port test … reports (left Perl 5.34, right Perl 5.38):

Failed 2 tests out of 2533, 99.92% okay.		| Failed 3 tests out of 2609, 99.89% okay.
	../cpan/ExtUtils-Constant/t/Constant.t		| 	../cpan/ExtUtils-Constant/t/Constant.t
	../cpan/ExtUtils-MakeMaker/t/02-xsdynamic.t	| 	../cpan/ExtUtils-MakeMaker/t/02-xsdynamic.t
							| 	../cpan/ExtUtils-MakeMaker/t/04-xs-rpath-darwin.t

Clearly the third failure in Perl 5.38 is no failure, it's an inappropriate test that should be switched off. The first fault does not seem to be a fault, because:

cc1: error: unrecognized command line option "-Werror=pointer-arith"			| cc1: error: unrecognized command line option "-Werror=pointer-arith"
cc1: error: unrecognized command line option "-Wc++-compat"				| cc1: error: unrecognized command line option "-Wc++-compat"	    
cc1: error: unrecognized command line option "-Werror=declaration-after-statement"	| make[1]: *** [ExtTest.o] Error 1				    
make[1]: *** [ExtTest.o] Error 1							| FAILED at test 3						    
FAILED at test 3

The second fault is ambiguous: Failed test '"make" exited normally'. Why is a "normal exit" a "failure"?

I am attaching the comparison.

[ballapete (Peter "Pete" Dyballa)]

Comparison of test failures on PPC Tiger from 'port test …', Perl 5.34 vs. Perl 5.38

[ballapete (Peter "Pete" Dyballa)]

There is one more problem: The tests are performed with /usr/bin/cc…

[ballapete (Peter "Pete" Dyballa)]

Finally finished the comparison of the manual tests!

[ballapete (Peter "Pete" Dyballa)]

Comparison of the manual tests

[ballapete (Peter "Pete" Dyballa)]

The manually performed tests, ./perl harness, seem to need some additional Perl modules:

AnyEvent		--> p5-anyevent
Import::Into		--> p5-import-into
Math::BigInt::GMP	--> p5-math-bigint-gmp
Math::BigInt::Pari	--> ? => p5-math-pari
Pod::Coverage		--> p5-pod-coverage 
POE			--> p5-poe
Test::Deep		--> p5-test-deep
Test::LeakTrace		--> p5-test-leaktrace
Test::More		--> ? => p5-test-more-utf8
Test::NoWarnings	--> p5-test-nowarnings
Test::Pod		--> p5-test-pod
Test::Taint		--> p5-test-taint
Tk			--> p5-tk

[ballapete (Peter "Pete" Dyballa)]

In order to proof that the installation of Perl 5.38 can safely be used I am testing the more than 600 modules. Some new Portfiles were created to satisfy needed module chains. Some tests now are real kind and output for example:

# === Configure Requires ===
# 
#     Module              Want Have
#     ------------------- ---- ----
#     ExtUtils::MakeMaker 6.78 7.70
# 
# === Build Requires ===
# 
#     Module              Want Have
#     ------------------- ---- ----
#     ExtUtils::MakeMaker  any 7.70
# 
# === Test Requires ===
# 
#     Module              Want     Have
#     ------------------- ---- --------
#     ExtUtils::MakeMaker  any     7.70
#     File::Spec           any     3.75
#     Test::More          0.96 1.302204
#     Test::Tester         any 1.302204
# 
# === Test Recommends ===
# 
#     Module         Want     Have
#     ---------- -------- --------
#     CPAN::Meta 2.120900 2.150010
# 
# === Runtime Requires ===
# 
#     Module                 Want     Have
#     ---------------------- ---- --------
#     CPAN::Meta              any 2.150010
#     Exporter                any     5.78
#     File::Find::Rule        any     0.34
#     File::Find::Rule::Perl  any     1.16
#     Perl::MinimumVersion   1.32     1.40
#     Test::Builder           any 1.302204
#     base                    any     2.27
#     strict                  any     1.12

How can I code those requirements in Portfile?