public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com> To: Mark Wielaard <mark@klomp.org> Cc: "H.J. Lu" <hjl.tools@gmail.com>, "Indu Bhagat" <indu.bhagat@oracle.com>, "Jan Beulich" <jbeulich@suse.com>, "Jin Ma" <jinma@linux.alibaba.com>, "Mike Frysinger" <vapier@gentoo.org>, "Tamar Christina" <tamar.christina@arm.com>, "Tejas Joshi" <TejasSanjay.Joshi@amd.com>, "Tom de Vries" <tdevries@suse.de>, binutils@sourceware.org, gdb-testers@sourceware.org, "Arsen Arsenović" <arsen@aarsen.me>, "Sam James" <sam@gentoo.org> Subject: Re: ☠ Buildbot (Sourceware): binutils-gdb-autoregen - failed 'git diff ...' (failure) (master) Date: Tue, 9 Jan 2024 09:58:25 +1030 [thread overview] Message-ID: <ZZyFGX69m/QvjCMy@squeak.grove.modra.org> (raw) In-Reply-To: <20240108215146.GB26453@gnu.wildebeest.org> On Mon, Jan 08, 2024 at 10:51:46PM +0100, Mark Wielaard wrote: > Hi Alan, > > On Mon, Jan 08, 2024 at 10:54:09AM +1030, Alan Modra wrote: > > On Sun, Jan 07, 2024 at 06:29:36PM +0100, Mark Wielaard wrote: > > > So the autogen tester would like to move these entries back to where > > > they were before. > > > > So why are the aclocal.m4 dependencies being sorted differently? It > > seems to me that what is currently in libcollector/aclocal.m4: > > > > m4_include([../../config/depstand.m4]) > > m4_include([../../config/lead-dot.m4]) > > m4_include([../../config/override.m4]) > > m4_include([../../config/warnings.m4]) > > m4_include([../../libtool.m4]) > > m4_include([../../ltoptions.m4]) > > m4_include([../../ltsugar.m4]) > > m4_include([../../ltversion.m4]) > > m4_include([../../lt~obsolete.m4]) > > > > is sorted correctly. This is the result I get by configuring with > > --enable-maintainer-mode, and until I see others getting a different > > result with --enable-maintainer-mode and the "correct" versions of > > auto tools, I'm going to say the tester is doing something wrong. > > You are right. There is a difference between what > --enable-maintainer-mode does and what autoregen.py does. > autoregen.py doesn't fully handle the (order of directories) of > AC_CONFIG_MACRO_DIRS in gprofng/libcollector/configure.ac. Yes, I squinted at that one a little after I posted my previous email, and found that swapping the order of AC_CONFIG_MACRO_DIRS args didn't help.. > We can make this the same by using the following hack in autoregen.py Thanks for fixing this. -- Alan Modra Australia Development Lab, IBM
next prev parent reply other threads:[~2024-01-08 23:28 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-07 5:24 builder 2024-01-07 17:29 ` Mark Wielaard 2024-01-08 0:24 ` Alan Modra 2024-01-08 21:51 ` Mark Wielaard 2024-01-08 23:28 ` Alan Modra [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-03-11 17:03 builder 2024-01-16 3:24 builder 2024-01-15 22:57 builder 2024-01-15 18:05 builder 2024-01-15 14:13 builder 2024-01-15 14:11 builder 2024-01-15 14:10 builder 2024-01-12 22:50 builder 2024-01-11 2:29 builder 2024-01-05 15:01 builder 2024-01-05 10:25 builder 2024-01-04 13:35 builder
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=ZZyFGX69m/QvjCMy@squeak.grove.modra.org \ --to=amodra@gmail.com \ --cc=TejasSanjay.Joshi@amd.com \ --cc=arsen@aarsen.me \ --cc=binutils@sourceware.org \ --cc=gdb-testers@sourceware.org \ --cc=hjl.tools@gmail.com \ --cc=indu.bhagat@oracle.com \ --cc=jbeulich@suse.com \ --cc=jinma@linux.alibaba.com \ --cc=mark@klomp.org \ --cc=sam@gentoo.org \ --cc=tamar.christina@arm.com \ --cc=tdevries@suse.de \ --cc=vapier@gentoo.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).