Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: mipxtx39 sim build failure
Date: Fri, 11 Nov 2016 20:48:00 -0000	[thread overview]
Message-ID: <7e0f96fe-d8d9-ccab-3939-3cecc61e9fbc@oarcorp.com> (raw)
In-Reply-To: <20161111193219.GJ21655@vapier.lan>



On 11/11/2016 1:32 PM, Mike Frysinger wrote:
> On 11 Nov 2016 09:48, Joel Sherrill wrote:
>> On 11/11/2016 12:37 AM, Mike Frysinger wrote:
>>> at any rate, should be fixed now in master & the gdb-7.12 branch.
>>
>> Thanks. That turned it into a link error on the master:
>>
>> /home/joel/rtems-4.11-work/rtems-source-builder/rtems/sources/b-mips/sim/mips/../../../gdb-7.12/sim/mips/mips.igen:1254: undefined reference to `check_u64'
>
> i already pushed a fix for that too ... you should sync to master
> and not just apply a one-off patch :)

You are right. It built from master. :)

I am trying to find the 7.12 plus patches which we will
consider a packaged stable toolset. We try to avoid
grabbing a random git hash for that.

Is there a single other patch I should grab? Or just
leave our mipstx39 configuration back on an older gdb
until 7.12.1?

Thanks

> -mike
>


  parent reply	other threads:[~2016-11-11 20:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10 21:53 Joel Sherrill
2016-11-11  6:37 ` Mike Frysinger
2016-11-11 15:48   ` Joel Sherrill
     [not found]     ` <20161111193219.GJ21655@vapier.lan>
2016-11-11 20:48       ` Joel Sherrill [this message]
2016-11-12  4:40         ` Mike Frysinger

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=7e0f96fe-d8d9-ccab-3939-3cecc61e9fbc@oarcorp.com \
    --to=joel.sherrill@oarcorp.com \
    --cc=gdb@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