GNU bug report logs -
#63008
[PATCH core-updates] gnu: gdb@11: Update to 11.2.
Previous Next
Full log
Message #26 received at 63008 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Mon, Apr 24, 2023 at 10:12:35PM +0200, Andreas Enge wrote:
> Hello Pierre,
>
> Am Mon, Apr 24, 2023 at 08:04:18PM +0100 schrieb Pierre Langlois:
> > I think the main reason we still have gdb 11 is to make sure we don't
> > rebuild the rust world. I'm afraid if we don't do update it know, we'll
> > have to do it quite soon, can the rust world be rebuilt on a staging
> > branch soon after the core-updates merge?
>
> definitely, there already is a rust-team branch, and the rust team is in
> the starting block. Discussing gdb in this context would probably be
> a good idea!
I also noticed that gdb-11.1 failed to build on core-updates on
riscv64-linux. I can confirm that gdb-12 does build on riscv64-linux on
core-updates. I haven't tried yet to use gdb-12 in place of gdb-11 in
the rust tests, but I assume it would work. I'll test it out on x86_64
on core-updates to see if it works.
It sounds like as it currently stands neither aarch64 nor riscv64 have a
working rust on core-updates. I suppose, in order to decrease the number
of rebuilds, we could introduce gdb-11.2 and use that as the gdb input
in rust for those two architectures until I can either switch everyone
to 11.2 in the rust-team branch or switch everyone to gdb-12.
--
Efraim Flashner <efraim <at> flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[signature.asc (application/pgp-signature, inline)]
This bug report was last modified 2 years and 53 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.