lld status on the freebsd ports

Tue Dec 13 05:37:29 PST 2016

> Sorry, I am probably missing something, but doesn't poudriere logs is what you want ?
> For example I have one in file:///usr/local/poudriere/data/logs/bulk/freebsd10_3-HEAD/2016-12-10_20h05m24s/build.html,
> I am able to open it, filter packages that has "linker_error" as a fail reason and see how many packages were blocked from each failture.
>
> Currently I see 33 ports failed because of "linker_error" from 274 total failed for me.
> Them are:
> #	Package	                        Origin	                        Phase	Skipped	Log
> 13	openal-soft-1.17.2	audio/openal-soft	build	22	linker_error
> 19	rtl-sdr-20140210_8	comms/rtl-sdr	build	2	linker_error
> 23	mono-4.6.1.5	lang/mono	build	34	linker_error
> 30	libunwind-20121006_2	devel/libunwind	build	3	linker_error
> 32	linux-f10-tcl85-8.5.3_2	lang/linux-f10-tcl85	stage	2	linker_error
> 33	linux-f10-tk85-8.5.3_2	x11-toolkits/linux-f10-tk85	stage	0	linker_error
> 37	postgresql94-contrib-9.4.10	databases/postgresql94-contrib	build	2	linker_error
> 52	libproj4-3.20081120	math/libproj4	build	0	linker_error
> 55	linux-c6-tcl85-8.5.7_1	lang/linux-c6-tcl85	stage	1	linker_error
> 56	linux-c6-tk85-8.5.7_2	x11-toolkits/linux-c6-tk85	stage	0	linker_error
> 57	linux-c7-tcl85-8.5.13	lang/linux-c7-tcl85	stage	1	linker_error
> 58	linux-c7-tk85-8.5.13	x11-toolkits/linux-c7-tk85	stage	0	linker_error
> 64	openhbci-0.9.17.2_1	finance/openhbci	build	1	linker_error
> 66	postgresql93-contrib-9.3.15	databases/postgresql93-contrib	build	1	linker_error
> 82	x11rdp-0.5.0.299_1	x11-servers/x11rdp	build	1	linker_error
> 91	ap24-mod_jk-1.2.41,1	www/mod_jk	build	0	linker_error
> 94	bash-static-4.4	shells/bash-static	build	0	linker_error
> 97	busybox-1.24.2	sysutils/busybox	build	0	linker_error
> 102	ccl-1.11	lang/ccl	build	0	linker_error
> 134	heimdal-1.5.3_6	security/heimdal	build	0	linker_error
> 141	nefu-1.5_2	net-mgmt/nefu	build	0	linker_error
> 145	openprinting-1.0_5	print/openprinting	build	0	linker_error
> 150	pam_p11-0.1.5_3	security/pam_p11	build	0	linker_error
> 160	postgresql92-contrib-9.2.19	databases/postgresql92-contrib	build	0	linker_error
> 161	postgresql95-contrib-9.5.5	databases/postgresql95-contrib	build	0	linker_error
> 162	postgresql96-contrib-9.6.1	databases/postgresql96-contrib	build	0	linker_error
> 166	qmail-dk-0.54_1	mail/qmail-dk	build	0	linker_error
> 171	mpich-3.2_1	net/mpich	build	0	linker_error
> 172	safecat-1.13	sysutils/safecat	build	0	linker_error
> 181	smlnj-110.77	lang/smlnj	stage	0	linker_error
> 185	unieject-6_5	sysutils/unieject	build	0	linker_error
> 187	wrk-4.0.2	benchmarks/wrk	build	0	linker_error
> 188	yate-5.5.0.p1	net/yate	build	0	linker_error
>
> As far I understand, ports that have skipped > 0 are our problem for now as they might be a reason of failture for much more ports.
> Though what unclear for me is for example "openal-soft-1.17.2" is a
> reason of 22 skipped ports, is that 22 a final value or each of that
> 22 can be a dependency for other N ports, so total number can be
> greater ?

That might be it. I really had no time to dig further. Note that looking
just for linker_error is not sufficient as it misses cases like a
configure failing because of the linker.

Cheers,
Rafael