On Jun 18, 2021, at 2:28 AM, Edgar Fuß <ef%math.uni-bonn.de@localhost> wrote:
Then adding --with-build-config=bootstrap-debug would work around the problem.
As I read the comments at the bottom of said Hombrew issue, that doesn't work
and you need --with-dwarf2 instead.
Am I mis-reading the Hombrew issue (which seems to relate to an older Xcode)?
I read through that too and thought it really meant —with-dwarf2 as well.
However, we use that option for older versions of Darwin:
.if !empty(MACHINE_PLATFORM:MDarwin-[0-8].*-*)
CONFIGURE_ARGS+= --with-dwarf2
.endif
This is Darwin 20.2.0, so I don’t think that matches.
In any case, the discussion of including differing debug information seems more plausible, although I have not had a chance to check and I don’t know the implications of that. For reference, here is what the gcc docs [1] say about that option:
‘bootstrap-debug’
Verifies that the compiler generates the same executable code, whether or not it is asked to emit debug information. To this end, this option builds stage2 host programs without debug information, and uses contrib/compare-debug to compare them with the stripped stage3 object files. If BOOT_CFLAGS is overridden so as to not enable debug information, stage2 will have it, and stage3 won’t. This option is enabled by default when GCC bootstrapping is enabled, if strip can turn object files compiled with and without debug info into identical object files. In addition to better test coverage, this option makes default bootstraps faster and leaner.
Perhaps someone who knows this better than I will chime in.
Thanks.
Cheers,
Brook
[1] https://gcc.gnu.org/install/build.html