On 2021/11/15 10:43, Tracey Emery wrote: > On Mon, Nov 15, 2021 at 05:46:44PM +0100, Theo Buehler wrote: > > On Mon, Nov 15, 2021 at 07:39:10AM -0700, Tracey Emery wrote: > > > On Sun, Nov 14, 2021 at 11:17:13PM +0100, Theo Buehler wrote: > > > > This port failed to build in my last amd64 bulk. Not sure how that's > > > > best handled (i.e., if and where the gsed dependency should be added) > > > > and if other gcc flavors have the same problem. > > > > > > > > gsed was present at the start of the build and was removed while > > > > configuring zlib: > > > > > > > > mkdir ./zlib > > > > Configuring in ./zlib > > > > [...] > > > > checking for a sed that does not truncate output... /usr/local/bin/gsed > > > > checking for grep that handles long lines and -e... /usr/bin/grep > > > > checking for egrep... /usr/bin/grep -E > > > > checking for fgrep... /usr/bin/grep -F > > > > checking for ld used by cc... > > > > /tmp/pobj/xtensa-lx106-elf-gcc-10.2.0/gcc-10.2.0/zlib/configure[4583]: > > > > /usr/local/bin/gsed: not found > > > > /usr/bin/ld > > > > > > > > lots of '/usr/local/bin/gsed: not found' later the build failed. > > > > > > Ok? > > > > ok > > > > That's what I'd have done. What's not clear to me is whether this is the > > only gcc version that needs this. > > Unsure. I know I needed this for the xtensa-esp32-elf update, but didn't > think about it for lx106. > > -- > > Tracey Emery >
It's a fairly common thing for all autoconf scripts, which is why ports infrastructure handles it specially (see CONFIG_SITE_LIST in gnu.port.mk which disables them unless explicitly listed as a BDEP), but unfortunately the various gcc builds don't use this part of infrastructure so miss out on it. I think we gave up trying to figure out how to pass it into all the necessary places in lang/gcc and just added the BDEP, so it probably makes sense if all the various ports building their own copies of gcc do the same.
