Bug 7465 - spamc/configure.in is deprecated in autoconf
Summary: spamc/configure.in is deprecated in autoconf
Status: NEW
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Building & Packaging (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: 4.0.0
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-29 13:05 UTC by Benny Pedersen
Modified: 2018-08-24 13:48 UTC (History)
2 users (show)



Attachment Type Modified Status Actions Submitter/CLA Status

Note You need to log in before you can comment on or make changes to this bug.
Description Benny Pedersen 2017-08-29 13:05:17 UTC
i list no specific version of autoconf since depending on specific version hide the depricated problem

will add more info from gentoo when i have it
Comment 1 Benny Pedersen 2017-11-07 04:45:10 UTC
https://bugs.gentoo.org/426262

sorry late add, i think we could follow it there, note check automake versions is needed, so more then just mv configure.in configure.ac
Comment 2 Kevin A. McGrail 2018-08-24 00:57:56 UTC
Benny, can you specify what you are trying to fix?  What problem you are seeing? 

On a 7.5 centos, I was able to run autoconf, autoheader and make spamc without any perceptible problem.
Comment 3 Benny Pedersen 2018-08-24 01:34:13 UTC
follow the gentoo bugzilla, no need to tell again here, autoconf <= 2.13 is not giving warning on deprication for configure.in, new versions gives warning if not using configure.ac

so hope configure.in is not in trunk anymore, that solves it
Comment 4 Kevin A. McGrail 2018-08-24 02:20:12 UTC
What real world problem occurs and how do I replicate it?
Comment 5 Benny Pedersen 2018-08-24 02:35:07 UTC
simple install gentoo

at the time i created this bug it was a bug atleast in gentoo, the link to bugzilla shows what gentoo devs did to resolve it

if thats not helpfull or even resolved i give up
Comment 6 Kevin A. McGrail 2018-08-24 12:41:08 UTC
Very funny, Benny.  That thread is quite long.  If you can give a synopsis of the problem, basic steps how to recreate it and pointers on a fix, that would be helpful.

Why should this be fixed?
What is the impact?
What is the priority?

For now, I'll target it for 4.0.0 but would appreciate more guidance.