Thanks for the quick response. My system complained that curl was not present. I also did not have wget, but the error didn't mention it (I'm pretty sure).
In any case, my suggestion would then be to require either one. BTW, I was running this on a (mostly) clean install of Debian 12 in WSL under Windows 11. Kind regards, Roosh On Fri, Oct 11, 2024 at 11:18 AM Jonathan Wakely <jwakely....@gmail.com> wrote: > > > On Fri, 11 Oct 2024 at 10:14, Roosh Fourtytwo via Gcc <gcc@gcc.gnu.org> > wrote: > >> Hi, Thanks for the clear and concise instructions. I'm building gcc-14, >> and have a small suggestion. >> >> Kind regards, >> Roosh42 >> >> *Webpage to update:* >> https://gcc.gnu.org/install/prerequisites.html >> >> *Suggestion:* >> Add curl as one of the prerequisites >> >> *Reason:* >> It is needed for ./contrib/download_prerequisites >> >> *Possible HTML to add to "Tools/packages necessary for building GCC":* >> <dt>curl</dt> >> <dd><p> >> If you use <code>./contrib/download_prerequisites</code> to download local >> copies of some prerequisites listed below (e.g. GMP, MPFR, MPC, ISL, >> gettext), the script will use curl. >> > > But it only uses curl if wget is not present: > > if type wget > /dev/null ; then > fetch='wget' > else > fetch='curl -LO' > fi > > But I agree that we should mention the download_prerequisites script more > prominently (and format it as code where it's already mentioned). > > >> </p> >> </dd> >> >> *Extra reasoning:* >> By adding this just before the list of deps, it is more likely that >> readers >> will become aware that they can take the easy-path* of downloading these >> via the contrib script, rather than trying to build/install them into >> their >> system. >> >> *easy-path references in https://gcc.gnu.org/wiki/InstallingGCC >> >
