unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Andreas Enge <andreas@enge.fr>
Cc: Pierre Langlois <pierre.langlois@gmx.com>, 63008@debbugs.gnu.org
Subject: [bug#63008] gdb on aarch64
Date: Tue, 25 Apr 2023 13:46:47 +0300	[thread overview]
Message-ID: <ZEevl8ZYEwtsu7WF@3900XT> (raw)
In-Reply-To: <ZEbis0sO4wBxrCOs@jurong>

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

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@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

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

  reply	other threads:[~2023-04-25 10:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21 22:11 [bug#63008] [PATCH core-updates] gnu: gdb@11: Update to 11.2 Pierre Langlois
2023-04-22 20:15 ` [bug#63008] gdb on aarch64 Andreas Enge
2023-04-24 19:04   ` Pierre Langlois
2023-04-24 19:20     ` Pierre Langlois
2023-04-24 20:12     ` Andreas Enge
2023-04-25 10:46       ` Efraim Flashner [this message]
2023-04-25 13:05         ` Andreas Enge
2023-04-26  7:04           ` Andreas Enge
2023-04-25 12:01       ` Efraim Flashner
2023-05-20 20:00         ` bug#63008: " Efraim Flashner

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZEevl8ZYEwtsu7WF@3900XT \
    --to=efraim@flashner.co.il \
    --cc=63008@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    --cc=pierre.langlois@gmx.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).