After upgrading to dev-lang/perl-5.34.0, (re)building mod_perl fails with: x86_64-pc-linux-gnu-gcc -I/var/tmp/portage/www-apache/mod_perl-2.0.11/work/mod_perl-2.0.11/src/modules/perl -I/var/tmp/portage/www-apache/mod_perl-2.0.11/work/mod_perl-2.0.11/xs -I/usr/include/apr-1 -I/usr/include/apr-1 -I/usr/include/apache2 -fwrapv -fno-strict-aliasing -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib64/perl5/5.34/x86_64-linux/CORE -DMOD_PERL -DMP_COMPAT_1X -fgnu89-inline -DLINUX -D_REENTRANT -D_GNU_SOURCE -march=core2 -freorder-blocks-and-partition -O2 -pipe -fPIC \ -c modperl_const.c && mv modperl_const.o modperl_const.lo modperl_perl.c: In function ‘modperl_hash_seed_set’: modperl_perl.c:271:16: error: lvalue required as unary ‘&’ operand 271 | memcpy(&PL_hash_seed, &MP_init_hash_seed, | ^ make[1]: *** [Makefile:114: modperl_perl.lo] Error 1 make[1]: *** Waiting for unfinished jobs.... This is a known issue upstream, see $URL. Applying upstream's patch to otherwise standard mod_perl-2.0.11 works; I'll submit a PR. mod_perl with that patch still builds correctly against perl-5.32, so I think no perl-version-checking logic is required.
Thanks for the report, but this should've been fixed just a little ago. I don't see your emerge --info to confirm your tree's timestamp, but please emerge --sync and try again. *** This bug has been marked as a duplicate of bug 791403 ***
(In reply to Ionen Wolkens from comment #1) > Thanks for the report, but this should've been fixed just a little ago. Indeed! It was fixed between when I found the problem & patch last night, and when I deployed and finished testing the fix today. Never mind :)
