unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Sergio Had <vital.had@gmail.com>
Cc: Gordon Steemson <gsteemso@gmail.com>, guile-devel@gnu.org
Subject: Re: Guile 3.0.10 fails to build for powerpc-darwin (3.0.9 built earlier)
Date: Mon, 30 Sep 2024 14:39:56 -0500	[thread overview]
Message-ID: <8734lhgcc3.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <c13255835a6feca2dab76da8f151135273a4f1c2.camel@physik.fu-berlin.de>

John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> writes:

> Yes, correct. Could be an idea to test on armhf to see if it's an endianness
> issue. And maybe also on s390x.

Current main 1c96e4ab6dde18c69f1493a8e1560e80a347cd21 was fine on s390x
(big 64) and armhf (little 32).

...then I remembered we might have relevant debian/patches.  If you
didn't, could you try again with https://salsa.debian.org/rlb/deb-guile/-/blob/deb/guile-3.0/d/sid/master/debian/patches/0007-Fix-32-bit-big-endian-builds-via-Oresolve-primitives.patch?ref_type=heads

Offhand, the failure doesn't look quite the same, but think it's worth
checking.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4



  reply	other threads:[~2024-09-30 19:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-01  5:44 Guile 3.0.10 fails to build for powerpc-darwin (3.0.9 built earlier) Gordon Steemson
2024-09-01  7:09 ` Gordon Steemson
2024-09-01  8:43   ` Sergey Fedorov
2024-09-13 15:59   ` Sergey Fedorov
2024-09-22  5:24     ` Sergey Fedorov
2024-09-22  8:33       ` John Paul Adrian Glaubitz
2024-09-22 15:53         ` Gordon Steemson
2024-09-22 15:57         ` Sergio Had
2024-09-29 17:46           ` Rob Browning
2024-09-29 18:43             ` John Paul Adrian Glaubitz
2024-09-29 19:19               ` John Paul Adrian Glaubitz
2024-09-29 19:34                 ` Sergey Fedorov
2024-09-29 20:00                 ` Rob Browning
2024-09-29 20:21                   ` John Paul Adrian Glaubitz
2024-09-30  1:24                     ` Rob Browning
2024-09-30  6:27                       ` John Paul Adrian Glaubitz
2024-09-30 19:39                         ` Rob Browning [this message]
2024-10-03  7:14                           ` Rob Browning
2024-10-03  7:40                             ` John Paul Adrian Glaubitz
2024-10-04  0:49                               ` Rob Browning
2024-10-04 14:50                                 ` Sergey Fedorov
2024-10-03  7:48                             ` Sergey Fedorov
2024-10-04  0:46                             ` Rob Browning
2024-09-01  8:51 ` Sergey Fedorov
     [not found] <mailman.12480.1725054330.21467.guile-devel@gnu.org>
2024-08-31  3:47 ` Gordon Steemson
  -- strict thread matches above, loose matches on Subject: below --
2024-08-30 21:20 Sergey Fedorov
2024-08-31  2:27 ` Rob Browning

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://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=8734lhgcc3.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=gsteemso@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=vital.had@gmail.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.
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).