|
From: Bruce S. <bw...@re...> - 2010-11-20 03:49:20
|
>>> I’m contemplating on how the lfssystem for 1.5 should look like. >>> >>> DL 1.5 will be available as 32 and 64 bit version, so we need to either have >>> 2 different lfssystems or one multilib. >>> >>> I’m currently more leaning towards the multilib. >> >> Yes, I'd go with multilib. > You know, I've been trying to build 64bit DL during a couple of years. And I > even managed to get it several times, but the result didn't satisfy me. The main > problem we'll face is compilation failures due to multi-arch libs availability. > In my case a lot of 64bit applications try to link against 32lib :( Most cases > are autoconf mistakes, which are possible to minimize by libs separation, but > the efforts are huge. The easiest way was a pure 64bit lfssystems. However, I'm > not the best release engineer and my problems might be related to lack of > knowledge/experience/etc. So, lets try with the most attractive approach for > majority of developers. As a plan B, I'd suggest thinking about 2 pure 32bit and > 64bit systems, but single source and script base. Plus maybe some additional > logic for handling this environment. More difficulties here, but less > difficulties in the future. Good point, I hadn't thought of sloppy autoconf's in the packages. It's more work to make 2 LFSsystems up front, but much less work afterwords, not having to fix a bunch of packages. Plus with 2 LFS's, we're sure a 64 bit compile is really 64 bit. I change my vote to 2 LFS's. :-) - BS |