Re: Trying to configure bash

[Daniel Premo]

Hello,

Realized I forgot to paste the information I can get from Mainsail:

mcu(gd32f303xe)
Version: 38d96adc-dirty-20231016_135251-longer

mcu rpi(linux)
Version: v0.11.0-372-gb9ad7605

Host(mips, 32bit)
Version: 09faed31-dirty
OS: Buildroot 2020.02.1

I'm guessing there's no C compiler, based on skimming https://buildroot.org/ and https://www.busybox.net/ . (Spotted Buildroot in Mainsail and spotted Busybox in the /usr/bin/ folder -- many of the programs in /usr/bin/ are symlinks to /bin/busybox .)

I don't want to waste anyone's time; I get it if I'm barking up the wrong tree.  Are Buildroot and Busybox known quantities?  Are they easily worked around?  They're probably designed to be not easily worked around, right?

Thanks,

Daniel

On Tue, Feb 6, 2024 at 8:59 AM Zack Weinberg <zack@owlfolio.org> wrote:

On Mon, Feb 5, 2024, at 10:16 PM, Daniel Premo wrote:
> root@F005-068E /root/projects/bash/bash-5.2.21 [#] ./configure
> checking build system type... ././support/config.guess: unable to guess system type
>
> NOTE: MIPS GNU/Linux systems require a C compiler to fully recognize
> the system type. Please install a C compiler and try again.

*Do* you have a C compiler installed?  You're going to need one anyway,
in order to build bash, so you might as well make sure of that now.

The code that tries to find a C compiler, looks for it under the names
"cc", "gcc", "c89", and "c99", in that order.  Check not only that
it's installed, but that it *works*; for instance, your problem could
be that you have the compiler but not all of the C library, and so it
can't actually produce executables.

zw

@config-patches at large: maybe the "unable to guess system type"
diagnostics should report on the availability of a C compiler in
detail, as well as what they already produce?