Some redundancies in toolchain checks

[chris@…]

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?

[bdubbs@…]

This ticket is not completely clear. Are you *only* referring to 6.10. Adjusting the Toolchain?

Second part:

I think the two different checks for the dynamic linker are checking two slightly different things. The first is asking what linker is specifying in a.out. The second is whether that linker is actually found on the correct path by ld. Admittedly it would be difficult for one to pass and the other to fail. However, I don't see a problem with leaving the tests as is.

[chris@…]

Yes, sorry, this is referring to the toolchain checks in Chapter 6, both in Adjust the Toolchain and the GCC page (though most of them are the same anyway, with xincludes).

[bdubbs@…]

Fixed at revision 10693.