public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org> To: builder@sourceware.org, "Maciej W. Rozycki" <macro@redhat.com>, Nick Clifton <nickc@redhat.com> Cc: binutils@sourceware.org, gdb-testers@sourceware.org Subject: Re: ☠ Buildbot (Sourceware): binutils-gdb-autoregen - failed 'git diff ...' (failure) (master) Date: Thu, 13 Jun 2024 18:34:56 +0200 [thread overview] Message-ID: <dcb6b903bc7da3b3fcf6136e8602d7ed922c9023.camel@klomp.org> (raw) In-Reply-To: <20240613141838.D8342388210C@sourceware.org> Hi Nick, On Thu, 2024-06-13 at 14:18 +0000, builder@sourceware.org wrote: > A failed build has been detected on builder binutils-gdb-autoregen while building binutils-gdb. > > Full details are available at: > https://builder.sourceware.org/buildbot/#/builders/270/builds/2447 > > Build state: failed 'git diff ...' (failure) > Revision: e8e10743f7b207b21a1efb0cc9e42487080db013 > Worker: bb3 > Build Reason: (unknown) > Blamelist: Maciej W. Rozycki <macro@redhat.com>, Nick Clifton <nickc@redhat.com> > > Steps: > > - 0: worker_preparation ( success ) > > - 1: git checkout ( success ) > Logs: > - stdio: https://builder.sourceware.org/buildbot/#/builders/270/builds/2447/steps/1/logs/stdio > > - 2: autoregen.py ( success ) > Logs: > - stdio: https://builder.sourceware.org/buildbot/#/builders/270/builds/2447/steps/2/logs/stdio > > - 3: git diff ( failure ) > Logs: > - stdio: https://builder.sourceware.org/buildbot/#/builders/270/builds/2447/steps/3/logs/stdio > It looks like not all autotool files were correctly regenerated. > diff --git a/ld/config.in b/ld/config.in > index 5f57a61def1..f7c9da3d02a 100644 > --- a/ld/config.in > +++ b/ld/config.in > @@ -31,6 +31,10 @@ > when a .note-GNU-stack section is missing. */ > #undef DEFAULT_LD_EXECSTACK > > +/* Define to 1 if you want to enable --rosegment in the ELF linker by default. > + */ > +#undef DEFAULT_LD_ROSEGMENT > + > /* The default method for DT_TEXTREL check in ELF linker. */ > #undef DEFAULT_LD_TEXTREL_CHECK > > @@ -49,10 +53,6 @@ > default. */ > #undef DEFAULT_LD_Z_MARK_PLT > > -/* Define to 1 if you want to enable --rosegment in the ELF linker by > - default. */ > -#undef DEFAULT_LD_ROSEGMENT > - > /* Define to 1 if you want to enable -z relro in ELF linker by default. */ > #undef DEFAULT_LD_Z_RELRO > I think the autoregen bot is right, DEFAULT_LD_ROSEGMENT should sort before DEFAULT_LD_TEXTREL_CHECK. > diff --git a/ld/configure b/ld/configure > index 83ea68f8e4b..4e8de840418 100755 > --- a/ld/configure > +++ b/ld/configure > @@ -11683,7 +11683,7 @@ else > lt_dlunknown=0; lt_dlno_uscore=1; lt_dlneed_uscore=2 > lt_status=$lt_dlunknown > cat > conftest.$ac_ext <<_LT_EOF > -#line 11684 "configure" > +#line 11686 "configure" > #include "confdefs.h" > > #if HAVE_DLFCN_H > @@ -11789,7 +11789,7 @@ else > lt_dlunknown=0; lt_dlno_uscore=1; lt_dlneed_uscore=2 > lt_status=$lt_dlunknown > cat > conftest.$ac_ext <<_LT_EOF > -#line 11790 "configure" > +#line 11792 "configure" > #include "confdefs.h" > > #if HAVE_DLFCN_H > Here I am not completely clear what happened. Did you use different autoconf version? Cheers, Mark
next prev parent reply other threads:[~2024-06-13 16:34 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-13 14:18 builder 2024-06-13 16:34 ` Mark Wielaard [this message] 2024-06-14 11:51 ` Nick Clifton 2024-06-14 12:14 ` Mark Wielaard -- strict thread matches above, loose matches on Subject: below -- 2024-06-20 9:44 builder 2024-06-14 9:31 builder 2024-06-09 23:18 builder 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-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 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=dcb6b903bc7da3b3fcf6136e8602d7ed922c9023.camel@klomp.org \ --to=mark@klomp.org \ --cc=binutils@sourceware.org \ --cc=builder@sourceware.org \ --cc=gdb-testers@sourceware.org \ --cc=macro@redhat.com \ --cc=nickc@redhat.com \ /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).