yes, that's what is supposed to do, but apparently it's not doing that. Now configured with --with-fpu=vfpv3-d16 again, which lets the boost build at least succeed again.
Still need to figure out if we need to re-upload packages built after the gcc-defaults change and before the gcc fix.
yes, that's what is supposed to do, but apparently it's not doing that. Now configured with --with- fpu=vfpv3- d16 again, which lets the boost build at least succeed again.
Still need to figure out if we need to re-upload packages built after the gcc-defaults change and before the gcc fix.