Ryan Oliver wrote: > No, I solve problems for which you have not catered for yet. > CLFS deals with building from non-linux hosts.
Off topic > Isn't your supposed goal technical perfection that us mere LFS mortals > can only aspire to? Not at all. Get the job done as quickly and efficiently as possible. And be easy to comprehend. I've proven that the path to a fully functional multiarch Ch6 toolchain does not require your levels of technical perfection. > WTF are you talking about, looks like theres a fair amount of "hacking > the source" in your build.. Note the "where possible" in my statement. > It would take 5 minutes to generate a simple patch to do this (even by Yep, of course. But even blind Freddie can see it won't be accepted by upstream. Feel free to try. Which reminds me, why has CLFS been carrying around the "Binutils Multilib Patch" for years without ever submitting upstream? Don't have the balls? Why hasn't anybody else needed it? Maybe the functionality isn't actually needed? It's disgraceful CLFS behavior. Please fix it. > I'll change the analogy: > > I fly in first class without having to lift a finger on my comfortable > ride to the destination > You are in economy trying to hold your seat together I'll pay that one :-) > Present build ensures our toolchain works by itself. DIY toolchain > without command line switches and generating and sed'ing specs cannot > find includes, libraries or produce a binary Irrelevant, as has been proven. You're *still* missing the point. > Congrats, there is nearly a valid argument in there this time. It's been a good discussion. Has made me think about the build a bit more. I'll be getting rid of a few warts in the DIY build. Regards Greg -- http://www.diy-linux.org/ -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
