id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
3654	Some redundancies in toolchain checks	chris@…	lfs-book@…	"First, most of the sentences mentioning what the output should be start with ""If everything is working correctly, there should be no errors[...]"" and I think there's no need to keep repeating that. It's also inaccurate anyway, since those are all just grep commands, so of course there wouldn't be any errors, just lack of output at worst.

Second, I don't see why the dynamic linker location is checked twice. First a readelf command is run on the compiled test program, then the last command in the series of checks is to look for the linker name in the log - is there any situation where these commands would give different output?"	task	closed	normal	7.6	Book	SVN	normal	fixed