Re: Host requirements to build the Tools binaries

"Greg A. Woods" <[email protected]> Sat, 31 Aug 2024 14:10:44 -0700
Newsgroups gmane.os.netbsd.devel.toolchain
Organization Planix, Inc.
Message-ID <[email protected]>
At Sat, 17 Aug 2024 19:21:10 +1200, Lloyd Parkes <[email protected]> wrote:
Subject: Re: Host requirements to build the Tools binaries
>
>    It was a mind boggling endless stream of fail just trying to
> build a plain old GNU make 3.81 on modern Linux with GCC 14.

I'm a little late in the game here, but I wonder if you told GCC-14 to
conform to the appropriate C Standard for that old legacy code or not.

I.e. did you add the appropriate "-std=gnu89", "-std=gnu99", or
whatever is right for an older GNU Make?


> This is not the first piece of GNU software that I seen fail to build
> on leading edge GNU systems.

It is, to me, crazy to try to use a newer compiler to compile legacy
code without first telling the compiler that it should treat the legacy
code as legacy code.  If you did not do this then that is most of your
problem.

It is my current (somewhat limited) experience with testing my own
legacy code and some few legacy packages against GCC-14 and Clang-16
that there are no "new" problems with this code when I tell those
compilers to conform to the appropriate language standard for the code
being compiled.

This probably applies to building the NetBSD toolchain on any foreign
host as well.  In my not-so-current current source tree I find only
xz-include/Makfile.inc setting the appropriate "-std=c99" flag.

--
					Greg A. Woods <[email protected]>

Kelowna, BC     +1 250 762-7675           RoboHack <[email protected]>
Planix, Inc. <[email protected]>     Avoncote Farms <[email protected]>
signature.asc (application/pgp-signature, 195 B)
-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQRuK6dmwVAucmRxuh9mfXG3eL/0fwUCZtOG1AAKCRBmfXG3eL/0
f/4lAJ4yQxkFnLAUsH8bQHdpAdDY2wXK5wCfVVQl+7+YZSNOhhfNfuhpd4+6/6U=
=ITOF
-----END PGP SIGNATURE-----