This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 02/22/2016 11:52 AM, Bin.Cheng wrote:
If there's a fundamental incompatibility, then you have to bootstrap, similar to bootstrapping a new architecture. That's rarely the case though.Hi, I still don't quite follow this method. If I pop up chroot environment with new glibc, it's still possible that the new glibc isn't compatible with the default gcc in chroot. Won't this a chicken-egg problem because we want to build our gcc against new glibc in the first place?
Most of the time it's sufficient to use mock or similar tools in this manner to build a new glibc or new gcc. You can then repeat using the just built glibc or gcc to catch any secondary effects.
jeff
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |