Bug 1944514 - autoconf-2.71 regression with intltool IT_PROG_INTLTOOL/AC_PROG_INTLTOOL macro
Summary: autoconf-2.71 regression with intltool IT_PROG_INTLTOOL/AC_PROG_INTLTOOL macro
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: intltool
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-30 05:47 UTC by Jaroslav Škarvada
Modified: 2022-12-13 15:20 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-13 15:20:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jaroslav Škarvada 2021-03-30 05:47:27 UTC
Description of problem:
AC_PROG_INTLTOOL stopped working if there is 'tab' on the beginning of the line. See: https://issues.imfreedom.org/issue/PIDGIN-17509 for details.

Version-Release number of selected component (if applicable):
intltool-0.51.0-18.fc35
autoconf-2.71-1.fc34.noarch.rpm

How reproducible:
Always

Steps to Reproduce:
1. Rebuild pidgin without the pidgin-2.14.1-autoconf-2.71-build-fix.patch

Actual results:
$ autoreconf -fi
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
ERROR: 'IT_PROG_INTLTOOL' must appear in configure.ac for intltool to work.
autoreconf: error: intltoolize failed with exit status: 1

Expected results:
No error

Additional info:
It's failing because of the 'tab' before the AC_PROG_INTLTOOL. With autoconf < 2.71 it doesn't fail. Maybe it's intltool bug, I don't know, starting with the autoconf, because it breaks with the autoconf update.

Comment 1 Ondrej Dubaj 2021-04-01 06:31:27 UTC
Posted to upstream:

https://lists.gnu.org/archive/html/bug-autoconf/2021-04/msg00000.html

Thanks for your report!

Comment 2 Ondrej Dubaj 2021-04-01 08:05:20 UTC
Response from upstream:

"This appears to be a portability bug in intltool; see <https://bugs.launchpad.net/intltool/+bug/1921816>. So I wouldn't worry about it as an Autoconf developer."

I would change the component to intltool and re-assign it.

Comment 3 Ben Cotton 2021-08-10 12:57:31 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.

Comment 4 Ben Cotton 2022-11-29 16:54:42 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Ben Cotton 2022-12-13 15:20:34 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.