On 04/05/2010 01:14 AM, stosss wrote: > On Sun, Apr 4, 2010 at 10:40 PM, James Richard Tyrer<[email protected]> wrote: >> I made the error of updating my GLibc to 2.11.1 and my GCC to 4.4.3 and >> all HELL (DLL HELL that is) has broken loose. :-( >> >> The major problem appears to be with various "locale" objects in the >> headers for GLibc and possibly in the headers for LibStdC++-4.4.3. >> >> Do we, I hope, have a patch in the works for this problem, or it it >> possible that down grading to GCC-4.4.1 would improve the problem (I >> consider this to be very low probability unless there is a specific >> regression). >> > > Doesn't it say in the book that binutils, gcc glibc all need to be > done together and if you are going to change them it is better to > rebuild the entire system? It also says you could do upgrades if you > do it in the proper order but it is not recommended. >
Technically it's not in the book, but it is mentioned in the FAQ. However upgrading GCC a mere couple of patch versions (assuming your comment about 4.4.1 means that you started with that) shouldn't cause any issues as it should be nothing but bugfixes, but then there never is any real guarantee. You also didn't say what Glibc version you started with, but generally you *really* don't want to upgrade that in place as everything depends on it, though like GCC a patch version upgrade shouldn't theoretically cause issues, so if you went from 2.11 -> 2.11.1 that shouldn't typically be a problem, but again no guarantee. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
