Bug 696838 – sys-libs/gdbm-1.18.1 - *** error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.18 but the autoconf macros are from gettext version 0.20

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Hongpeng Cao 2019-10-06 09:42:43 UTC]

When I use the 'mips-linux-gnu-emerge --ask gdbm', I failed to install it.
The error message is:

make[1]: Entering directory '/usr/mips64el-unknown-linux-gnu/tmp/portage/sys-libs/gdbm-1.18.1/work/gdbm-1.18.1-abi_mips>Making all in po
make[2]: Entering directory '/usr/mips64el-unknown-linux-gnu/tmp/portage/sys-libs/gdbm-1.18.1/work/gdbm-1.18.1-abi_mips>*** error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.18 but the autoconf macros ar>make[2]: *** [Makefile:181: check-macro-version] Error 1
make[2]: Leaving directory '/usr/mips64el-unknown-linux-gnu/tmp/portage/sys-libs/gdbm-1.18.1/work/gdbm-1.18.1-abi_mips_>make[1]: *** [Makefile:460: all-recursive] Error 1
make[1]: Leaving directory '/usr/mips64el-unknown-linux-gnu/tmp/portage/sys-libs/gdbm-1.18.1/work/gdbm-1.18.1-abi_mips_>make: *** [Makefile:392: all] Error 2
 ^[[31;01m*^[[0m ERROR: sys-libs/gdbm-1.18.1::gentoo failed (compile phase):
 ^[[31;01m*^[[0m   emake failed
 ^[[31;01m*^[[0m
 ^[[31;01m*^[[0m If you need support, post the output of `emerge --info '=sys-libs/gdbm-1.18.1::gentoo'`,
 ^[[31;01m*^[[0m the complete build log and the output of `emerge -pqv '=sys-libs/gdbm-1.18.1::gentoo'`.

Above message is the part of my build.log. I try to install it many  times, and I attempted to alter the file named Makefile.in.in and change 8 to 20. Because I search for this problem on gentoo disscusion forum.The link is https://forums.gentoo.org/viewtopic-p-8376560.html#8376560.
However,it was still fail to install it. Maybe I think it was a bug of Gentoo.

[Comment 1 Jeroen Roovers (RETIRED) 2019-10-06 09:52:36 UTC]

Please attach the entire build log to this bug report.

[Comment 2 Jeroen Roovers (RETIRED) 2019-10-09 05:34:57 UTC]

*** Bug 697032 has been marked as a duplicate of this bug. ***

[Comment 3 Todd Walter 2020-01-20 21:49:27 UTC]

Happens when cross-compiling for ARM64 as well.

make[2]: Entering directory '/usr/aarch64-unknown-linux-gnu/tmp/portage/sys-libs/gdbm-1.18.1/work/gdbm-1.18.1-.arm64/po'
*** error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.18 but the autoconf macros are from gettext version 0.20
make[2]: *** [Makefile:181: check-macro-version] Error 1

[Comment 4 Todd Walter 2020-01-20 21:49:57 UTC]

Created attachment 603840 [details]
Build of aarch64 gdbm

[Comment 5 Todd Walter 2020-01-21 13:24:07 UTC]

FWIW 1.13-r2 works.

[Comment 6 tt_1 2020-05-04 09:11:40 UTC]

I just hit this when rebuilding parts of my cross compile prefix with the new bash/readline update from yesterday. It passes when editing the Makefile.in.in in question on the fly, which is a bit tricky with cross compile wrappers, but I made it. 

Is there no way to do some sed magic in the ebuild for a proper fix of this? I think I've hit the underlying bug with at least one other package in the tree a few weeks ago, but forgot which one it was.

[Comment 7 Stuart Shelton 2020-05-24 18:45:39 UTC]

I get the same error with a native (non-cross compile) on amd64, in this case when installing to a fresh directory specified by setting 'ROOT', and with minimal USE flags.

I don't get the same problem on the ROOT=/ install, though, suggesting that the error is a dependency issue?

[Comment 8 Stuart Shelton 2020-05-24 18:50:00 UTC]

Ah, and also this was with sys-libs/gdbm-1.13-r2 rather than gdbm-1.18.1

(In reply to Stuart Shelton from comment #7)
> I get the same error with a native (non-cross compile) on amd64, in this
> case when installing to a fresh directory specified by setting 'ROOT', and
> with minimal USE flags.
> 
> I don't get the same problem on the ROOT=/ install, though, suggesting that
> the error is a dependency issue?

[Comment 9 Marcus Comstedt 2020-06-13 17:35:46 UTC]

Created attachment 644566 [details, diff]
Patch to target gettext 0.20 instead of 0.18

This patch fixes the issue by making autopoint --force (which is run automatically) target gettext 0.20 instead of 0.18.

[Comment 10 Larry the Git Cow 2020-12-17 12:15:29 UTC]

The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ab4e2d7bbcd2621bf86330ffb992ac840088ee83

commit ab4e2d7bbcd2621bf86330ffb992ac840088ee83
Author:     Andreas K. Hüttel <[e-mail]>
AuthorDate: 2020-12-17 12:14:52 +0000
Commit:     Andreas K. Hüttel <[e-mail]>
CommitDate: 2020-12-17 12:15:16 +0000

    sys-libs/gdbm: Allow gettext 0.18 *or later*
    
    Closes: https://bugs.gentoo.org/696838
    Package-Manager: Portage-3.0.9, Repoman-3.0.2
    Signed-off-by: Andreas K. Hüttel <[e-mail]>

 sys-libs/gdbm/files/gdbm-1.18.1-gettext.patch | 12 ++++++++++++
 sys-libs/gdbm/gdbm-1.18.1-r1.ebuild           |  5 ++++-
 2 files changed, 16 insertions(+), 1 deletion(-)