develooper Front page | perl.perl5.porters | Postings from October 2017

default_inc_exclude_dot breaks miniperl?

Thread Next
From:
Philip Prindeville
Date:
October 16, 2017 01:20
Subject:
default_inc_exclude_dot breaks miniperl?
Message ID:
811F8ABD-4382-42A0-B322-E04D84B23D02@cpan.org
I tried updating LEDE/OpenWrt from 5.24.1 to 5.26.1 and turned on default_inc_excludes_dot=‘define’ since it’s more secure and seems like a good idea.

Problem is this immediately seems to break the ‘miniperl’ build target:


x86_64-openwrt-linux-musl-gcc -c -DPERL_CORE -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Os -pipe -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable -Wno-error=unused-result -I/home/philipp/bertram/lede/staging_dir/target-x86_64_musl_powercode-bmu/usr/include -I/home/philipp/bertram/lede/staging_dir/target-x86_64_musl_powercode-bmu/include -I/home/philipp/bertram/lede/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/usr/include -I/home/philipp/bertram/lede/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/include/fortify -I/home/philipp/bertram/lede/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/include -std=c89 -O2 -Wall -Werror=declaration-after-statement -Wextra -Wc++-compat -Wwrite-strings -fPIC miniperlmain.c
rm: cannot remove 'miniperl': No such file or directory
Makefile:359: recipe for target 'lib/buildcustomize.pl' failed
make[3]: [lib/buildcustomize.pl] Error 1 (ignored)
/bin/ln -s /home/philipp/bertram/lede/staging_dir/hostpkg/usr/bin/perl miniperl
LD_LIBRARY_PATH=/home/philipp/bertram/lede/build_dir/target-x86_64_musl_powercode-bmu/perl/perl-5.26.1 ./miniperl -w -Ilib -Idist/Exporter/lib -MExporter -e '<?>' || sh -c 'echo >&2 Failed to build miniperl.  Please run make minitest; exit 1'
LD_LIBRARY_PATH=/home/philipp/bertram/lede/build_dir/target-x86_64_musl_powercode-bmu/perl/perl-5.26.1 ./miniperl -Ilib -f write_buildcustomize.pl 'osname' "linux"
do "lib/buildcustomize.pl" failed, '.' is no longer in @INC; did you mean do "./lib/buildcustomize.pl"? at write_buildcustomize.pl line 101.
Can't load generated lib/buildcustomize.pl:  at write_buildcustomize.pl line 112.
Makefile:359: recipe for target 'lib/buildcustomize.pl' failed
make[3]: *** [lib/buildcustomize.pl] Error 2


My naive question is why not add “-I.” to the args to miniperl?

Even after doing that, however, other things fail:


LD_LIBRARY_PATH=/home/philipp/bertram/lede/build_dir/target-x86_64_musl_powercode-bmu/perl/perl-5.26.1 ./miniperl -Ilib -I. mkppport
running "/home/philipp/bertram/lede/staging_dir/hostpkg/usr/bin/perl" -I../../lib PPPort_pm.PL
Can't locate parts/ppptools.pl in @INC (@INC contains: ../../lib /home/philipp/bertram/lede/staging_dir/hostpkg/usr/lib/perl5/site_perl/5.26.1/x86_64-linux-thread-multi /home/philipp/bertram/lede/staging_dir/hostpkg/usr/lib/perl5/site_perl/5.26.1 /home/philipp/bertram/lede/staging_dir/hostpkg/usr/lib/perl5/5.26.1/x86_64-linux-thread-multi /home/philipp/bertram/lede/staging_dir/hostpkg/usr/lib/perl5/5.26.1) at PPPort_pm.PL line 18.
"/home/philipp/bertram/lede/staging_dir/hostpkg/usr/bin/perl" -I../../lib PPPort_pm.PL failed: 512
Makefile:379: recipe for target 'makeppport' failed
make[3]: *** [makeppport] Error 2



Also, as an aside, does anyone else find the warnings from the “-@rm ...” rules annoying?

Why not just use “@(RMS) ...” instead?

Thanks,

-Philip

Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About