On Thu, 2017-09-21 at 18:05 -0500, DJ Lucas wrote: > > On 09/18/2017 08:47 PM, Armin K. wrote: > > On 19.9.2017 0:48, Bruce Dubbs wrote: > > > NOTE: Please trim when replying. > > > > > > > > > With the above info, the question is how to incorporate it into > > > LFS/BLFS. To install meson/ninja into LFS requires four new > > > packages: > > > libffi, python3, ninja, and meson. I've tested this and they > > > work > > > fine. The only issue in my mind is whether we need to keep some > > > of > > > these in BLFS. libffi will not be needed, but Python3 and ninja > > > have > > > several optional dependencies not in LFS. meson appears to only > > > need > > > Python3. > > > > > > > I have incorporated libffi, python3, ninja and meson into LFS > > chapter 5 > > on my end. It did require an UTF-8 locale to be generated when > > building > > chapter 5 glibc, but it wasn't a big deal. I do think Dj has a > > working > > prototype. I did not take a look at it, however, so I can't speak > > about it. > > I also had OpenSSL in my patchset, but Bruce was able to test > without > it. Any particular reason for Chapter 5 instead of Chapter 6? I'm > thinking go ahead and install in chapter 6. You can rebuild Python > for > TK and OpenSSL later without modification to the existing BLFS > instructions. Ninja can make a mention of something to the effect of > "If > you use emacs and want the syntax lisp files installed..." Meson can > take advantage of several other languages to complete the test suite > later on as well, but I'm thinking libffi, ninja, and meson can be > in > LFS only if we go for Chapter 6. > > --DJ >
Your solution is also fine. Note that I dislike rebuilding the packages for extra features in chapter 6 because of my package management which makes it hard to script and to be predictable. -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
