unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: 58444@debbugs.gnu.org
Cc: "Mathieu Othacehe" <othacehe@gnu.org>,
	"Ludovic Courtès" <ludo@gnu.org>,
	control@debbugs.gnu.org,
	"Denis 'GNUtoo' Carikli" <GNUtoo@cyberdimension.org>
Subject: bug#58444: Make gtk use librsvg on aarch64 again.
Date: Wed, 12 Oct 2022 21:38:27 +0200	[thread overview]
Message-ID: <877d14x26k.fsf@pelzflorian.de> (raw)
In-Reply-To: <87tu4a1cfz.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Tue, 11 Oct 2022 19:45:36 +0200")

close 58444
thanks

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:
> "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:
>> I wrote a patch but probably it would rebuild the world.
> It does rebuild the world.  I will try with (or (target-aarch64?)
>                                                 (target-x86-64?)).

My other attempt also caused rebuilds.  Also it's not that important if
gtk+-2 uses an old librsvg.  I had thought GNUtoo's i686 fix (and thank
you for it) introduced a regression for aarch64, but had not noticed how
his use of (target-x86-64?) was a common pattern for e.g. emacs as well.
Perhaps it is better to remove the (target-x86-64?) checks as soon as
mrustc supports i686.

Sorry for the noise.  Closing.

Regards,
Florian




      reply	other threads:[~2022-10-12 19:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19 11:41 bug#57933: Gtk is unsupported on i686-linux Mathieu Othacehe
2022-10-09 20:36 ` Ludovic Courtès
2022-10-10 15:40   ` Ludovic Courtès
2022-10-11 15:56 ` bug#58444: Make gtk use librsvg on aarch64 again pelzflorian (Florian Pelz)
2022-10-11 17:45   ` pelzflorian (Florian Pelz)
2022-10-12 19:38     ` pelzflorian (Florian Pelz) [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

  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=877d14x26k.fsf@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=58444@debbugs.gnu.org \
    --cc=GNUtoo@cyberdimension.org \
    --cc=control@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=othacehe@gnu.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.
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).