Hello, luatex-0.65.0 fails to build with multiple --param options passed to gcc. This bug looks similar to bug 317475, but this time dev-libs/zziplib-0.13.60 seems to be guilty, because it installs compile flags into *.pc file. Without --param options in *FLAGS luatex will nevertheless fail if these options were used during zziplib compilation. Anyway luatex mechanism for the duplicated options stripping should be more clever, otherwise this error will occur here and there.
Created attachment 261065 [details] build.log
Created attachment 261066 [details] environment
Created attachment 261068 [details] emerge --info
Created attachment 261070 [details] zziplib.pc pkgconfig *.pc file from zziplib-0.13.60 installation.
zziplib installs all $LDFLAGS to the *.pc file. This should not be done.
Er, your LDFLAGS seem to include gcc flags and you should fix that. So the real problem is that LDFLAGS gets propagated into zziplib.pc. Here's mine: # generated by configure / remove this line to disable regeneration prefix=/usr exec_prefix=${prefix} bindir=${exec_prefix}/bin libdir=${exec_prefix}/lib datarootdir=${prefix}/share datadir=/usr/share sysconfdir=/etc includedir=${prefix}/include package=zziplib suffix= Name: zziplib Description: ZZipLib - libZ-based ZIP-access Library with an Easy-to-Use API Version: 0.13.60 Requires: zzip-zlib-config Libs: -L${libdir} -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -lzzip Cflags: -I${includedir} Which is a minor problem compared to yours.
# grep Libs:.*-Wl /usr/lib/pkgconfig/zzip* /usr/lib/pkgconfig/zzipfseeko.pc:Libs: -L${libdir} -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as -needed -lzzipfseeko /usr/lib/pkgconfig/zziplib.pc:Libs: -L${libdir} -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-ne eded -lzzip /usr/lib/pkgconfig/zzipmmapped.pc:Libs: -L${libdir} -Wl,-O1 -Wl,--hash-style=gnu -Wl,--a s-needed -lzzipmmapped
(In reply to comment #6) > Er, your LDFLAGS seem to include gcc flags and you should fix that. Why do you consider this inheritance as an error? This was done intentionally, because absolute majority of the packages use gcc for linking instead of plain ld and gcc can perform additional optimizations at the linking stage. The most prominent of them is upcoming -flto — yes, at this too buggy and unstable now, but it will definitely be production at some day — and for -flto to be effective you must use it on both compilation and linking stages. Further optimizations like -march or -On may affect linking as well, according to gcc manual. I had problems with LDFLAGS="${CFLAGS} -Wl,-O1 -Wl,--as-needed" with only two packages from 2336 installed: bintutils and live, and simple workaround is to use /etc/portage/env/ to set more conventional LDFLAGS. But ideally these packages should be fixed instead, however some people may argue that formally there is nothing to be fixed in them.
not a bug in zziplib itself ...
sent a patch to the AX_CREATE_PKGCONFIG_INFO authors and worked around the issue in zziplib-0.13.60-r1
