id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
598	Implement sanity check for the spec file edit(s)	greg@…	greg@…	"The lack of spec file edit will be the number 1 failure point for new readers of
the book. We have seen this lots in the post plfs hint period. I propose that we
put in a BIG FAT WARNING in the ""Locking in Glibc"" section. The test could be as
simple as something like this:-

$ echo 'main(){}' > dummy.c
$ gcc dummy.c
$ readelf -l a.out | grep tools

If there is no ouput then something went wrong and the user MUST be told to STOP
and fix up the mistake before continuing.

The same will be true (but in reverse) in Ch 6 so we really should do something
there as well.

I'll commit something appropriate then seek comment. But if you have any
concerns in the meanwhile then pls add them to this bug. Thanks."	defect	closed	lowest		Book	CVS	normal	fixed