Re: possible bug: no escaping for preprocessor macro STDC_HEADERS warning
"Zack Weinberg" <[email protected]> Wed, 18 Feb 2026 13:08:37 -0500
| Newsgroups | gmane.comp.sysutils.autoconf.bugs |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Feb 18, 2026, at 12:08 PM, Emily Ammundsen wrote: > Thank you for your help, and your offer to help with particular code.=C2= =A0 I=20 > think I will put this project on the backburner until I am hit with a=20 > desire to learn the depths of gnu build tools and M4 as the project ha= s=20 > issues many warnings (including one about improperly quoted arguments)= ,=20 > and gnu build tools is something I would like to learn at some point. Fair enough. > http://deb.debian.org/debian/pool/main/l/lincity/lincity_1.13.1.orig.t= ar.gz I haven't checked, but there's a good chance that https://deb.debian.org/debian/pool/main/l/lincity/lincity_1.13.1-17.debi= an.tar.xz contains, among other things, a patch that will make this old program bu= ildable using current Autoconf. > As for building autoconf, it turns out that `./bootstrap -v` only fail= s if=20 > I do a shallow clone of the repository. I clearly don't know enough gi= t,=20 > as I assumed shallow clones would always be safe. Ah. Yes, that makes sense. When building from a git checkout, the build scripts (not just the bootstrap script) inspect the git *history* to det= ermine Autoconf's own version number, and that doesn't work with a shallow clon= e. I will add a note to README-hacking about this; thank you for bringing i= t to my attention. zw