On Sat, Jan 14, 2017 at 10:50 PM, Roger Koehler <[email protected]> wrote: > On Sat, Jan 14, 2017 at 9:44 PM, DJ Lucas <[email protected]> wrote: >> >> >> On 01/14/2017 05:29 PM, Roger Koehler wrote: >>> >>> On Fri, Jan 13, 2017 at 1:20 PM, Pierre Labastie >>> <[email protected]> wrote: >>>> >>>> >>>> Thanks for the heads up. Will look into this. But I think building >>>> blfs_root >>>> upon CLFS is asking for trouble, because I am not sure the /etc directory >>>> layout is the same as for LFS... Well, maybe it is with systemd. It >>>> definitely >>>> isn't with sys V. >>> >>> >>> So far, I have not been successful building ANY version of CLFS with >>> jhalfs. I first tried with my latest LFS build which uses GCC 6.3, >>> just to see if I could hit a home run - NOT. So, I repartitioned my >>> SSD to make room for another OS and installed Trisquel, which uses an >>> older version of GCC. Still no luck. >>> >>> What is a known good way to build CLFS x86_64 (multilib) from an amd64 >>> host? >>> >> >> You can do it after regular LFS, but that doesn't fix the CLFS book or its >> interaction with jhalfs. >> >> I just updated from local sources (without testing): >> >> http://www.linuxfromscratch.org/~dj/lfs-multilib-20170115.diff >> >> As long as you are not opposed to /lib and /usr/lib with /usr/lib32 for >> 32bit libs (Debian style). Also, with ISL and gold but ld.bfd default, this >> should work (though I haven't tested it in a while). >> >> --DJ > > Wow! You are awesome! I am still new at this. How would I use patch to > update the sources in jhalfs/trunk with your .diff?
Oh, I guess I would patch the LFS SVN area (revision 11171). (Still not sure how to do this to an entire directory structure - I guess I need to read up on patch), then run jhalfs with the newly generated working copy (haven't ever done this before either). -- http://lists.linuxfromscratch.org/listinfo/alfs-discuss FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
