On 18 June 2017 at 03:35, Bruce Dubbs <bruce.du...@gmail.com> wrote: > Warning: This is quite long. If replying, please trim the response to > just the relevant portion. > > Starting out, there are several packages needed to really get things > going. In my case openssh, wget, nfs (libtirpc/nfs-utils/rpcbind), and > sudo. Using the order generated by jhalfs indicates to me some problems we > have in the blfs book. Most of these are issues with dependencies. For > instance with gptfdisk, popt should be recommended. >
I reported a dependency issue in v4l-utils a couple of days ago; it read thus:- "None of the dependencies shown in the book as "Required" is, in fact, a build dependency. They should all be listed as "Recommended" or "Optional". Mesa and GLU are only needed if building against X windows. Libjpeg-turbo is a compile-time option. I've just built v4l-utils with libjpeg-turbo installed (because I wanted that support), but I don't have Mesa or GLU installed as I'm not building for X windows. v4l-utils built just fine with no issues." I'll bet that there are a number of packages in the book that have misleading dependencies listed. > Back to jhalfs. > > As I was going through the list of packages, I was unsure of the versions > I had vs what was in the book. In the script names, is would be helpful if > the package version was also listed. for instance: > > 120-z-cmake vs > 120-z-cmake-3.8.2 > I had the same issue in my build and came up with a similar solution. I think it's a good idea. Richard
-- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
