Hi all, I'm just about finished building the GCC4 branch of LFS which is (I believe) trunk using GCC-4.0.1. Everyone is by now aware that there will be difficulties with some BLFS packages using GCC-4.x.
I am going to begin building BLFS packages using GCC-4.0.1 and I'm looking for ideas on how to go about making whatever changes might be necessary to the package instructions available to the community. One idea I have is to create a GCC4 branch of BLFS and as packages are confirmed (or instructions updated to work) they are added into this branch. The branch would essentially be empty of packages, with the ones missing having instead a placeholder in place of the real instructions. We would add real instructions as they are confirmed to work. This wouldn't take a great deal of time and would not interfere with trunk. This way folks can have access to updated BLFS instructions which work with GCC-4.x, and we don't have to worry about interfering with package instructions that use GCC-3.4.x to compile. Other suggestions are welcome and appreciated. -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 13:21:00 up 121 days, 12:54, 2 users, load average: 0.48, 0.85, 0.73 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
