dev-perl:Parse-Yapp-1.210.0-r1:20220223-110411.log

dev-perl:Parse-Yapp-1.210.0-r1:20220223-110411.log (text/plain), 5.90 KB, created by Toralf Förster on 2022-02-23 12:16:59 UTC

 * Package:    dev-perl/Parse-Yapp-1.210.0-r1
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox

>>> Unpacking source...
>>> Unpacking Parse-Yapp-1.21.tar.gz to /var/tmp/portage/dev-perl/Parse-Yapp-1.210.0-r1/work
>>> Source unpacked in /var/tmp/portage/dev-perl/Parse-Yapp-1.210.0-r1/work
>>> Preparing source in /var/tmp/portage/dev-perl/Parse-Yapp-1.210.0-r1/work/Parse-Yapp-1.21 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-perl/Parse-Yapp-1.210.0-r1/work/Parse-Yapp-1.21 ...
 * Using ExtUtils::MakeMaker
 * perl Makefile.PL PREFIX=/usr INSTALLDIRS=vendor INSTALLMAN3DIR=none DESTDIR=/var/tmp/portage/dev-perl/Parse-Yapp-1.210.0-r1/image
Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for Parse::Yapp
Writing MYMETA.yml and MYMETA.json
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-perl/Parse-Yapp-1.210.0-r1/work/Parse-Yapp-1.21 ...
 * emake OTHERLDFLAGS=-Wl,-O1 -Wl,--as-needed -Wl,--defsym=__gentoo_check_ldflags__=0 OPTIMIZE=-pipe -march=native -fno-diagnostics-color -O2
make -j4 'OTHERLDFLAGS=-Wl,-O1 -Wl,--as-needed -Wl,--defsym=__gentoo_check_ldflags__=0' 'OPTIMIZE=-pipe -march=native -fno-diagnostics-color -O2' 
cp lib/Parse/Yapp/Grammar.pm blib/lib/Parse/Yapp/Grammar.pm
cp lib/Parse/Yapp/Lalr.pm blib/lib/Parse/Yapp/Lalr.pm
cp lib/Parse/Yapp.pm blib/lib/Parse/Yapp.pm
cp lib/Parse/Yapp/Options.pm blib/lib/Parse/Yapp/Options.pm
cp lib/Parse/Yapp/Parse.pm blib/lib/Parse/Yapp/Parse.pm
cp lib/Parse/Yapp/Driver.pm blib/lib/Parse/Yapp/Driver.pm
cp lib/Parse/Yapp/Output.pm blib/lib/Parse/Yapp/Output.pm
cp yapp blib/script/yapp
"/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/yapp
Manifying 1 pod document
Manifying 1 pod document
>>> Source compiled.
 * Skipping make test/check due to ebuild restriction.
>>> Test phase [disabled because of RESTRICT=test]: dev-perl/Parse-Yapp-1.210.0-r1

>>> Install dev-perl/Parse-Yapp-1.210.0-r1 into /var/tmp/portage/dev-perl/Parse-Yapp-1.210.0-r1/image
make -j4 pure_install 
Manifying 1 pod document
Manifying 1 pod document
Installing /var/tmp/portage/dev-perl/Parse-Yapp-1.210.0-r1/image/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp.pm
Installing /var/tmp/portage/dev-perl/Parse-Yapp-1.210.0-r1/image/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp/Output.pm
Installing /var/tmp/portage/dev-perl/Parse-Yapp-1.210.0-r1/image/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp/Driver.pm
Installing /var/tmp/portage/dev-perl/Parse-Yapp-1.210.0-r1/image/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp/Parse.pm
Installing /var/tmp/portage/dev-perl/Parse-Yapp-1.210.0-r1/image/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp/Options.pm
Installing /var/tmp/portage/dev-perl/Parse-Yapp-1.210.0-r1/image/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp/Lalr.pm
Installing /var/tmp/portage/dev-perl/Parse-Yapp-1.210.0-r1/image/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp/Grammar.pm
Installing /var/tmp/portage/dev-perl/Parse-Yapp-1.210.0-r1/image/usr/share/man/man1/yapp.1
Installing /var/tmp/portage/dev-perl/Parse-Yapp-1.210.0-r1/image/usr/share/man/man3/Parse::Yapp.3
Installing /var/tmp/portage/dev-perl/Parse-Yapp-1.210.0-r1/image/usr/bin/yapp
 * Fixing installed file permissions
 * Fixing packlist file //usr/lib64/perl5/vendor_perl/5.34/x86_64-linux/auto/Parse/Yapp/.packlist
>>> Completed installing dev-perl/Parse-Yapp-1.210.0-r1 into /var/tmp/portage/dev-perl/Parse-Yapp-1.210.0-r1/image

 * Final size of build directory: 476 KiB
 * Final size of installed tree:  228 KiB


 * checking 16 files for package collisions
 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at https://bugs.gentoo.org/ unless you report exactly
 * which two packages install the same file(s). See
 * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
 * to solve the problem. And once again, please do NOT file a bug report
 * unless you have completely understood the above message.
 * 
 * Detected file collision(s):
 * 
 * 	/usr/share/man/man3/Parse::Yapp.3.bz2
 * 	/usr/share/man/man1/yapp.1.bz2
 * 	/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp.pm
 * 	/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp/Output.pm
 * 	/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp/Driver.pm
 * 	/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp/Parse.pm
 * 	/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp/Options.pm
 * 	/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp/Lalr.pm
 * 	/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp/Grammar.pm
 * 	/usr/bin/yapp
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * dev-perl/PerlMol-0.3500:0::gentoo
 * 	/usr/bin/yapp
 * 	/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp.pm
 * 	/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp/Driver.pm
 * 	/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp/Grammar.pm
 * 	/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp/Lalr.pm
 * 	/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp/Options.pm
 * 	/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp/Output.pm
 * 	/usr/lib64/perl5/vendor_perl/5.34/Parse/Yapp/Parse.pm
 * 	/usr/share/man/man1/yapp.1.bz2
 * 	/usr/share/man/man3/Parse::Yapp.3.bz2
 * 
 * Package 'dev-perl/Parse-Yapp-1.210.0-r1' NOT merged due to file
 * collisions. If necessary, refer to your elog messages for the whole
 * content of the above message.