Chris Staub wrote: > 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.
I believe that if you try building a kernel module with a different compiler than the original kernel, then there is a high probability of an error. Of course you can rebuild the whole kernel, including all modules, with the new compiler. > 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. To me the linchpin of the system is glibc. If you are going to change that, rebuild everything. Even binutils can be changed on a current system, but there is little value in that unless you have a very specific problem. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
