Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please drop AM_C_PROTOTYPES/de-ANSI-fication from configure.ac #261

Closed
cbiedl opened this issue Jul 21, 2019 · 4 comments
Closed

Please drop AM_C_PROTOTYPES/de-ANSI-fication from configure.ac #261

cbiedl opened this issue Jul 21, 2019 · 4 comments
Labels
question This issue is a question

Comments

@cbiedl
Copy link

cbiedl commented Jul 21, 2019

Hi Alex,
we had already discussed this: The Debian build ecosystem wishes to run autoreconf and friends when building a package while ngircd still uses de-ANSI-fication to support very old compilers. That feature however was removed in autoconf a while ago, therefore autoreconf breaks.
While it still is possible to work around the situation I expect rather sooner than later this will no longer be possible. Therefore I'm asking you to either remove that support, indeed losing support for some old platforms. Or any other solution like an alternative set of configure.ac/Makefile.am without ansi2knr. I tried to create that but failed.

@alexbarton alexbarton added the question This issue is a question label Oct 26, 2019
@cbiedl
Copy link
Author

cbiedl commented Nov 13, 2019

We discussed this again at the ngIRCd WWDC ten days ago. Result was I'll disable autoreconf in the Debian packaging for the time being. Worst thing that could happen was the generated files ngircd ships are not correct, probably for some exotic or new build architecture. If that ever happens, I should be possible to update the related files in ngircd.

@thesamesam
Copy link
Contributor

thesamesam commented Apr 20, 2020

The same problem exists in Gentoo. Depending on the specific automake version for now.

gentoo-bot pushed a commit to gentoo/gentoo that referenced this issue Aug 5, 2021
We're not actually using it right now anyway and
we should work with upstream to avoid the
requirement for such an old version of automake somehow
(by possibly porting away from the removed macro).

(Revbump to allow folks to depclean the now-obsolete
BDEPEND, especially given it's about to be masked.)

See: ngircd/ngircd#261
Signed-off-by: Sam James <sam@gentoo.org>
@alexbarton alexbarton closed this as not planned Won't fix, can't repro, duplicate, stale Jan 2, 2023
@thesamesam
Copy link
Contributor

I can look into this if the work will be merged. Modern C compilers are planning to drop support for obsolete prototypes anyway (https://lwn.net/Articles/913505/).

@alexbarton
Copy link
Member

@thesamesam thanks for offering to help!

But one goal of ngIRCd was to support really old systems, like old versions of Apple A/UX, AIX, SunOS, … some of which do not come with an ANSI C compiler (at least not out of the box). And that's why I depend on the legacy ansi2knr tool here, which was supported by legacy versions of the GNU autotools. Therefore I build the distribution archives using an old Debian version and old versions of GNU autoconf and automake – and these versions depend on the AM_C_PROTOTYPES

Therefore it is not an option to get rid of it …

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question This issue is a question
Projects
None yet
Development

No branches or pull requests

3 participants