On Wed, 2020-03-11 at 17:15 +0000, Jonathan Wakely wrote: > My thinking was to build GCC inside the container, then package up the > results and install that on your dev machines (outside a container). > But actually that won't work because you'd also need to package the > glibc from the container, and at that point you're basically back to > using a sysroot.
Yes. It's actually much simpler to use RPMs for this, and far more accurate. I have a vague memory of trying to extract the necessary files from a live system, sometime in the past. Hopefully I only attempted this for a few minutes before realizing that getting the RPMs was a far more reliable and efficient way to generate a sysroot :). Thanks!
