On Mon, Sep 05, 2016 at 01:45:45AM +0200, Tim Tassonis wrote: > On 09/04/2016 10:12 AM, Rob wrote: > > Thanos Baloukas <baloukast...@sch.gr> wrote: > > http://lists.linuxfromscratch.org/pipermail/lfs-support/2016-September/050333.html > > > > In that thread, you linked to a script collection, on github. The > > instructions in there did not work (not surprising), and asking google just > > linked to a bunch of pages about installing multiarch packages using > > various distro package managers. Not useful here. > > So, I gave up on trying to build a multilib toolchain. > > > > There is a working instruction from Armin to quite easily get a 32-bit glibc > on a 64-bit lfs system. > > As I only needed a glibc to get my binary 32-bit brother printer drivers > working, that was enough for me. > > If that is all you need, I can send you the instructions. If you however > need more, I'm clueless as well. > Unlike 10 years ago, people building from source (which is what LFS is all about) only need multilib if they have to run 32-bit binary packages.
I'm sure Armin's instructions work, but whether somebody who has not yet successfully built LFS (plus whatever parts of BLFS appeal to him) has the experience to follow them seems unlikely. Building LFS for the first time is hard. Many people have trouble. And multilib is harder still (or perhaps just "more tedious", but "harder" is probably a better starting assumption). Cross-lfs may well be using older packages than LFS - they have even fewer developers and builders than we do - but to suggest they are "a few years behind" is an overstatement. In a cross-build it is not safe to assume that new versions of packages will just drop in without problems. Even in LFS we sometimes hit problems with newer versions. My suggestion to Rob is that he should build LFS, plus whichever parts of BLFS are useful to him. Perhaps more than once. the first time, do it manually, typing in the commands. After that, he should work out what went wrong, and *how* he can automate (script) his builds in a way that suits him. Most people will then need to learn what happens when their own take on scripting fails, but I will acknowledge that maybe he is more clever than I am, and can grasp that immediately, so that only one scripted LFS build is needed (I just wish, after using LFS for perhaps 12 or 14 years, that I had developed the ability to spot my own scripting errors before they break my builds). And after that, he should be in a position to either follow Armin's instructions for whatever 32-bit binary software he wants to use, or to follow cross-lfs for a full bi-arch system. ĸen -- `I shall take my mountains', said Lu-Tze. `The climate will be good for them.' -- Small Gods -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
