Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 829859 - xfce-base/exo-4.16.3 - error: po/Makefile.in.in was not created by intltoolize.
Summary: xfce-base/exo-4.16.3 - error: po/Makefile.in.in was not created by intltoolize.
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: XFCE Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-23 10:30 UTC by Jakov Smolić
Modified: 2022-02-15 22:36 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (info,5.70 KB, text/plain)
2021-12-23 10:30 UTC, Jakov Smolić
Details
config.log (exo-config.log,73.56 KB, text/plain)
2021-12-23 10:31 UTC, Jakov Smolić
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jakov Smolić archtester gentoo-dev 2021-12-23 10:30:58 UTC
Created attachment 760143 [details]
emerge --info

* Package:    xfce-base/exo-4.16.3
 * Repository: gentoo
 * Maintainer: xfce@gentoo.org
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking exo-4.16.3.tar.bz2 to /var/tmp/portage/xfce-base/exo-4.16.3/work
>>> Source unpacked in /var/tmp/portage/xfce-base/exo-4.16.3/work
>>> Preparing source in /var/tmp/portage/xfce-base/exo-4.16.3/work/exo-4.16.3 ...
 * Applying exo-4.16.0-allow-cross.patch ...
 [ ok ]
 * Running eautoreconf in '/var/tmp/portage/xfce-base/exo-4.16.3/work/exo-4.16.3' ...
 * Running 'intltoolize --automake --copy --force' ...
 [ ok ]
 * Running 'gtkdocize --copy' ...
 [ ok ]
 * Running 'libtoolize --install --copy --force --automake' ...
 [ ok ]
 * Running 'aclocal -I m4' ...
 [ ok ]
 * Running 'glib-gettextize --copy --force' ...
 [ ok ]
 * Running 'aclocal -I m4' ...
 [ ok ]
 * Running 'autoconf --force' ...
 [ ok ]
 * Running 'autoheader' ...
 [ ok ]
 * Running 'automake --add-missing --copy --foreign --force-missing' ...
 [ ok ]
 * Running elibtoolize in: exo-4.16.3/
 *   Applying portage/1.2.0 patch ...
 *   Applying sed/1.5.6 patch ...
 *   Applying as-needed/2.4.3 patch ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/xfce-base/exo-4.16.3/work/exo-4.16.3 ...
 * econf: updating exo-4.16.3/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating exo-4.16.3/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-silent-rules --docdir=/usr/share/doc/exo-4.16.3 --htmldir=/usr/share/doc/exo-4.16.3/html --with-sysroot=/ --libdir=/usr/lib64
configure: loading site script /usr/share/config.site
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/lib/portage/python3.9/ebuild-helpers/xattr/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether UID '250' is supported by ustar format... yes
checking whether GID '250' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether make supports nested variables... (cached) yes
checking whether make supports the include directive... yes (GNU style)
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to enable C11 features... none needed
checking whether x86_64-pc-linux-gnu-gcc understands -c and -o together... yes
checking dependency style of x86_64-pc-linux-gnu-gcc... none
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for wchar.h... yes
checking for minix/config.h... no
checking for sys/param.h... yes
checking whether it is safe to define __EXTENSIONS__... yes
checking whether _XOPEN_SOURCE should be defined... no
checking for library containing strerror... none required
checking if building for some Win32 platform... no
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by x86_64-pc-linux-gnu-gcc... /usr/x86_64-pc-linux-gnu/bin/ld
checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/x86_64-pc-linux-gnu-nm -B
checking the name lister (/usr/bin/x86_64-pc-linux-gnu-nm -B) interface... BSD nm

[snip]

checking for gtkdoc-mkpdf... /usr/bin/gtkdoc-mkpdf
checking whether to build gtk-doc documentation... no
checking for GTKDOC_DEPS... yes
checking whether to build with debugging support... minimum
checking whether /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64 accepts --as-needed... yes
checking whether /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64 accepts -O1... yes
checking whether x86_64-pc-linux-gnu-gcc supports the GNUC visibility attribute... yes
checking if x86_64-pc-linux-gnu-gcc supports -DGSEAL_ENABLE... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating docs/Makefile
config.status: creating docs/reference/Makefile
config.status: creating docs/man/Makefile
config.status: creating exo/Makefile
config.status: creating exo/exo-2.pc
config.status: creating exo/exo-config.h
config.status: creating exo-desktop-item-edit/Makefile
config.status: creating exo-open/Makefile
config.status: creating icons/Makefile
config.status: creating icons/24x24/Makefile
config.status: creating icons/48x48/Makefile
config.status: creating pixmaps/Makefile
config.status: creating po/Makefile.in
config.status: creating tests/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing default-1 commands
config.status: executing po/stamp-it commands
config.status: error: po/Makefile.in.in was not created by intltoolize.

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/xfce-base/exo-4.16.3/work/exo-4.16.3/config.log
 * ERROR: xfce-base/exo-4.16.3::gentoo failed (configure phase):
 *   econf failed
 * 
 * Call stack:
 *               ebuild.sh, line  127:  Called src_configure
 *             environment, line 1591:  Called default
 *      phase-functions.sh, line  858:  Called default_src_configure
 *      phase-functions.sh, line  893:  Called __eapi2_src_configure
 *        phase-helpers.sh, line  828:  Called econf
 *        phase-helpers.sh, line  711:  Called __helpers_die 'econf failed'
 *   isolated-functions.sh, line  112:  Called die
 * The specific snippet of code:
 *   		die "$@"
 * 
 * If you need support, post the output of `emerge --info '=xfce-base/exo-4.16.3::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=xfce-base/exo-4.16.3::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/xfce-base/exo-4.16.3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/xfce-base/exo-4.16.3/temp/environment'.
 * Working directory: '/var/tmp/portage/xfce-base/exo-4.16.3/work/exo-4.16.3'
 * S: '/var/tmp/portage/xfce-base/exo-4.16.3/work/exo-4.16.3'
Comment 1 Jakov Smolić archtester gentoo-dev 2021-12-23 10:31:23 UTC
Created attachment 760144 [details]
config.log
Comment 2 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2021-12-23 10:51:50 UTC
I can't reproduce.  What's your intltool version?
Comment 3 Jakov Smolić archtester gentoo-dev 2021-12-23 10:53:00 UTC
(In reply to Michał Górny from comment #2)
> I can't reproduce.  What's your intltool version?

~ ➭ intltoolize --version
intltoolize (GNU intltool) 0.51.0
Comment 4 Jakov Smolić archtester gentoo-dev 2022-02-11 11:07:23 UTC
I'm once again hitting this on my amd64/x86 testing systems, but interestingly, this error doesn't appear on my local system nor on the arm64 test machine...
I'm going to unblock the stabilization
Comment 5 Norman Rieß 2022-02-12 11:49:50 UTC
I just ran into this issue on my arm64 VM.
Comment 6 Will Simoneau 2022-02-14 17:03:35 UTC
Same issue here with xfce-base/exo-4.16.3 on both amd64 and arm64.  Both have:
dev-util/intltool-0.51.0-r2
sys-devel/gettext-0.21-r1
Both are "clean" chroots used exclusively to build binpkgs.

Note: I use heavily customized cascading profiles on both arches, though most of the cross-arch differences involve relatively inconsequential feature USE-flags.  My package versions and build environments are nearly identical otherwise.
Comment 7 Marcus Comstedt 2022-02-15 09:54:28 UTC
I just got this issue, on arm64.  Looking a little bit closer, the check in
config.status requires the text "# INTLTOOL_MAKEFILE" to appear on a separate
line in po/Makefile.in.in.  There is no such line there, but if I simply add
the line, then everything compiles and installs just fine.  So it seems that
the check is either outdated, or simply too cautious...
Comment 8 Jakov Smolić archtester gentoo-dev 2022-02-15 22:04:52 UTC
The root cause seems to be in xfce4-dev-tools-4.16.0 which contains various gettext macros which were removed in version 4.17.0 (https://github.com/xfce-mirror/xfce4-dev-tools/commit/008475ee9a08aaa458df8ff650d739889fb377a0, https://github.com/xfce-mirror/xfce4-dev-tools/commit/6f651e4a6b1e78d4745cba1b8bb193d73e38af2b)
autotools.eclass checks for those macros, and executes 'glib-gettextize --copy --force' (as part of eautoreconf) if they are present on the system, the command is ran after `intltoolize`, hence the po/Makefile.in.in will get regenerated by gettext and cause the check to fail. As a workaround (until 4.17.0 is stable) we can simply invoke `intltoolize` again after eautoreconf to make sure that the Makefile.in.in is generated by it and not gettext.
Comment 9 Larry the Git Cow gentoo-dev 2022-02-15 22:21:32 UTC
The bug has been closed via the following commit(s):

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

commit 37a0a867d13cde822c22ad74d83ea029b0f9fdc0
Author:     Jakov Smolić <jsmolic@gentoo.org>
AuthorDate: 2022-02-15 22:11:41 +0000
Commit:     Jakov Smolić <jsmolic@gentoo.org>
CommitDate: 2022-02-15 22:20:18 +0000

    xfce-base/exo: Call intltoolize after eautoreconf
    
    - The build system wants the po/Makefile.in.in file to be created by
      intltoolize, so let's manually call it after eautoreconf to make sure
      it's ran after glib-gettextize.
    
    Closes: https://bugs.gentoo.org/829859
    Signed-off-by: Jakov Smolić <jsmolic@gentoo.org>

 xfce-base/exo/exo-4.16.3.ebuild | 2 ++
 1 file changed, 2 insertions(+)