On Mon, Aug 1, 2022 at 3:54 AM Andreas Schwab <sch...@suse.de> wrote: > > On Jul 31 2022, Eric Gallager via Gcc-patches wrote: > > > It just makes the configure script respect the --with-build-time-tools > > flag. > > Why does it make any difference? >
See the original bug report: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43301 > > diff --git a/configure b/configure > > index 65d7078dbe7..4d46b94ebc4 100755 > > --- a/configure > > +++ b/configure > > @@ -12850,7 +12850,9 @@ fi > > # Check whether --with-build-time-tools was given. > > if test "${with_build_time_tools+set}" = set; then : > > withval=$with_build_time_tools; case x"$withval" in > > - x/*) ;; > > + x/*) > > + with_build_time_tools=$withval > > This just reassigns the value that was retrieved a couple of lines > above from the very same variable. > Oh, ok, so I guess this isn't necessary after all? In which case we can just close 43301 as INVALID then? > -- > Andreas Schwab, SUSE Labs, sch...@suse.de > GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 > "And now for something completely different."
