id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
102	Build order/hard-coded binary pathname issues...	chris@…	clfs-commits@…	"Many packages end up with hard-coded names to various binaries, which has usually been solved by either switching the build order around when needed to ensure that certain programs were in specific places when they were found by other packages, or creating symlinks to some binaries. However, this is essentially a completely different issue for the sysroot book since it will be looking at program locations on the host system. In a way it simplifies things because the build order is less important, but it can also cause problems when programs on the host system that packages hard-code paths to are not in the same place on the host system as on the final CLFS system.

The most obvious way to solve this is to create symlinks on the host to any such programs, but we do want to avoid touching the host whenever possible. Does anyone else have ideas for any other potential solution?"	task	new	major	CLFS Sysroot 1.0.0	BOOK	CLFS Sysroot GIT