Re: mipxtx39 sim build failure

Mike Frysinger <[email protected]>
Newsgroups gmane.comp.gdb.devel
Message-ID <[email protected]>
On 11 Nov 2016 14:47, Joel Sherrill wrote:
> 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?

i pushed them both to the 7.12 branch already too ...
-mike
signature.asc (application/pgp-signature, 819 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJYJp1EAAoJEEFjO5/oN/WBB4QP/1aUySIZVOpGuoyAMfqFeekv
YmOW1W4fwe9wWuErSkUvLeMvXQpxA9PipuGZMN+17ftmao98+nvXC6XfN6DpxBZ6
CwIdQRiE7Tx71G2vLa8qnTSlhCDGPji4Wh4VyaNkOSgIpPEpTF4IRBKJ0H9CiG65
bgGTTDH+CiiPETrsYc0xsPgP3qjgeYvBvCr0VAPueJxjKwyt8BxPLfdoQtwTJX80
iOlszoNfTie4NbZy/TvMmNE2AK7w6d26hWt9/DRrXpPTcUmOKLQw6V5MZXtzKHTS
WGQm4NY0me5U/GTeKvCQrY2GfxUPgO27iQkEq5tNEP6wMlgOD0HAhzdlL68ajUhi
Sh/1h0diSinByuLzAW3CR+s+lhOJZhbFbqbRP+05xhQRG7QEoNv22+IcSj6JKBvN
16lgnaPB9I7n7EU9e18AFjULF3mB26Xv+wTOi2kOudLi/jMa6xV9Y4tKdhDeHzM6
Dszz7jl5Tz6wmX1iEmTorT16rnGe91ByJoIVEk4BVlgo7VVz/CmDsLI9L85LIXKN
wmfNZK60ZR16fWH9ZgvLszTzTP4L+RDaWGDtGcQTHuwkSXwnoDx+Anp34rEm2ewM
LwOy45R9DRREIx7t+2X506KKF5bOZdVUdzo8uHtxFOvsiH5v2d1o8RfKc/zXv7HA
Toc10avPgbf3Luq6P4WT
=Lecn
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.