Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PUSHED] sim: fixes for libopcodes styled disassembler
Date: Mon, 5 Sep 2022 12:38:59 +0200	[thread overview]
Message-ID: <20220905103859.gguimq3alkeacnwq@lug-owl.de> (raw)
In-Reply-To: <20220904170417.GA745711@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 939 bytes --]

On Sun, 2022-09-04 18:04:17 +0100, Andrew Burgess <aburgess@redhat.com> wrote:
> * Jan-Benedict Glaw <jbglaw@lug-owl.de> [2022-09-03 08:57:32 +0200]:
> > On Mon, 2022-04-04 22:46:32 +0100, Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org> wrote:
> > > Sorry for the breakage, and thank you for your understanding.
> > 
> > .../configure --prefix=... --target=sparc-linux
> > make V=1 all-gdb
> > /var/cache/git/binutils-gdb/sim/erc32/interf.c:247: undefined reference to `fprintf_styled'
> > collect2: error: ld returned 1 exit status
> > make[1]: *** [Makefile:2142: gdb] Error 1
> > make[1]: Leaving directory '/tmp/sparc/b/gdb'
> > make: *** [Makefile:13193: all-gdb] Error 2
> 
> Thanks for pointing this out.
> 
> I pushed the patch below which should fix this problem.   Let me know
> if you still have any problems with the build.

Fixes all affected / tested targets.

Thanks!
  Jan-Benedict

-- 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2022-09-05 10:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 21:46 Andrew Burgess via Gdb-patches
2022-09-03  6:57 ` Jan-Benedict Glaw
2022-09-04 17:04   ` Andrew Burgess via Gdb-patches
2022-09-05 10:38     ` Jan-Benedict Glaw [this message]

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=20220905103859.gguimq3alkeacnwq@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.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: link
Be 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