On Mon, Dec 21, 2015 at 08:22:24PM -0600, Bruce Dubbs wrote: > Ken Moffat wrote: > > >>I wrote it to run after the builder thinks he or she has installed > >>all the packages in chapter 5. In that context, any failure _is_ an > >>error. > >> > >A revised version to run at any time in chapter 5. A couple of > >checks at the start which do complain if people did bad things, then > >just 'OK' or 'not installed' for each package (except, it notes > >broken symlinks, the original tests were not quite right), and some > >comments are output at the end (what to test if you think you > >compiled with a bad PATH, and why there will not be a similar script > >for chroot). > > > >This time, I've also left my debug code for checking the functions > >in-place but commented out. > > I'm a bit confused. For instance: > > check_file linux-headers /tools/include/xen/..install.cmd > > When I run 'find /mnt/lfs/tools -name install.cmd', I get no output. > > -- Bruce > The filename is '..install.cmd', it's easy to misread that as ../ (been there, done that). In 4.3.3 :
ken@ac4tv /tmp/linux-4.3 $ls -a dest/include/xen/ . .. evtchn.h gntalloc.h gntdev.h .install ..install.cmd privcmd.h If we are going to go with something like this (and I see William doesn't like it), I guess that just checking for the xen directory would do - on every other package I avoided checking for include files because header file names might change with newer releases. For the linux headers, we only install headers so I had to make an exception. ĸen -- This email was written using 100% recycled letters. -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
