Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 939468 - media-gfx/gnuclad-0.2.4-r1 - [gcc-15] Automake "maintainer mode" detected:
Summary: media-gfx/gnuclad-0.2.4-r1 - [gcc-15] Automake "maintainer mode" detected:
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Andreas K. Hüttel
URL:
Whiteboard:
Keywords: PullRequest
Depends on:
Blocks:
 
Reported: 2024-09-11 12:43 UTC by Toralf Förster
Modified: 2024-09-24 11:52 UTC (History)
4 users (show)

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


Attachments
emerge-info.txt (emerge-info.txt,20.28 KB, text/plain)
2024-09-11 12:43 UTC, Toralf Förster
Details
emerge-history.txt (emerge-history.txt,240.19 KB, text/plain)
2024-09-11 12:43 UTC, Toralf Förster
Details
etc.portage.tar.xz (etc.portage.tar.xz,31.15 KB, application/x-xz)
2024-09-11 12:43 UTC, Toralf Förster
Details
media-gfx:gnuclad-0.2.4-r1:20240911-120142.log (media-gfx:gnuclad-0.2.4-r1:20240911-120142.log,539 bytes, text/plain)
2024-09-11 12:43 UTC, Toralf Förster
Details
qlist-info.txt.xz (qlist-info.txt.xz,63.34 KB, application/x-xz)
2024-09-11 12:43 UTC, Toralf Förster
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Toralf Förster gentoo-dev 2024-09-11 12:43:44 UTC
QA Notice: Automake "maintainer mode" detected:

	(CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh '/var/tmp/portage/media-gfx/gnuclad-0.2.4-r1/work/gnuclad-0.2.4/build-aux/missing' autoheader)

If you patch Makefile.am, configure.in,  or configure.ac then you
should use autotools.eclass and eautomake or eautoreconf. Exceptions
are limited to system packages for which it is impossible to run
autotools during stage building. See https://wiki.gentoo.org/wiki/Proj

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 23.0_desktop-20240907-083002

  The build log matches a QA pattern or sth. requested by a dev.
  The attached etc.portage.tar.xz has all details.
  -------------------------------------------------------------------
Comment 1 Toralf Förster gentoo-dev 2024-09-11 12:43:45 UTC
Created attachment 902649 [details]
emerge-info.txt
Comment 2 Toralf Förster gentoo-dev 2024-09-11 12:43:47 UTC
Created attachment 902650 [details]
emerge-history.txt
Comment 3 Toralf Förster gentoo-dev 2024-09-11 12:43:48 UTC
Created attachment 902651 [details]
etc.portage.tar.xz
Comment 4 Toralf Förster gentoo-dev 2024-09-11 12:43:49 UTC
Created attachment 902652 [details]
media-gfx:gnuclad-0.2.4-r1:20240911-120142.log
Comment 5 Toralf Förster gentoo-dev 2024-09-11 12:43:50 UTC
Created attachment 902653 [details]
qlist-info.txt.xz
Comment 6 Eli Schwartz gentoo-dev 2024-09-11 15:04:44 UTC
autotools.eclass runs autoheader without options (and in particular without --force). This will only remake config.h.in if there are actual changes to the content, which in turn means that it will be out of date compared to aclocal.m4 (which we very much expect to have changes).

So `make` sees that the header is out of date, and runs autoheader yet again, this time updating the timestamp for `make` purposes.


Possibly an eclass bug...
Comment 7 Larry the Git Cow gentoo-dev 2024-09-24 11:52:32 UTC
The bug has been closed via the following commit(s):

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

commit 5ff4a902b3706209c6fe148d9e3c621f6cc53ba4
Author:     YiFei Zhu <zhuyifei1999@gmail.com>
AuthorDate: 2024-09-13 04:38:04 +0000
Commit:     Sam James <sam@gentoo.org>
CommitDate: 2024-09-24 11:51:20 +0000

    autotools.eclass: Run eautoheader with --force
    
    To quote Eli [1] (I can't explain it better than this):
    
      autotools.eclass runs autoheader without options (and in
      particular without --force). This will only remake config.h.in
      if there are actual changes to the content, which in turn means
      that it will be out of date compared to aclocal.m4 (which we very
      much expect to have changes).
    
      So `make` sees that the header is out of date, and runs autoheader
      yet again, this time updating the timestamp for `make` purposes.
    
    This causes QA warning that "maintainer mode" is detected.
    
    autoheader and autoconf added --force option at the same time [2],
    so no reason only autoconf has that option in the eclass and not
    autoheader.
    
    Like, autoconf, a check on WANT_AUTOCONF != 2.1 is added because the
    feature was added in autoconf 2.52.
    
    [1] https://bugs.gentoo.org/939468#c6
    [2] https://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=dbf7fc61
    
    Closes: https://bugs.gentoo.org/939468
    Closes: https://bugs.gentoo.org/939535
    Signed-off-by: YiFei Zhu <zhuyifei1999@gmail.com>
    Closes: https://github.com/gentoo/gentoo/pull/38588
    Signed-off-by: Sam James <sam@gentoo.org>

 eclass/autotools.eclass | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)