From: Sergey Fedorov <vital.had@gmail.com>
To: Rob Browning <rlb@defaultvalue.org>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
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: Fri, 4 Oct 2024 21:50:28 +0700 [thread overview]
Message-ID: <CALYdzymLjUgTK6C5yswSJ_drmtL+0RxOU_XG6kj2RtTfgX8tuQ@mail.gmail.com> (raw)
In-Reply-To: <87ttdsvgi0.fsf@trouble.defaultvalue.org>
[-- Attachment #1: Type: text/plain, Size: 1429 bytes --]
Not directly related to the bug being discussed, but since we already deal
with powerpc here:
What is the reason for pre-built ppc binaries being broken on Darwin? I
understand that Darwin ppc ABI differs from ELF, but on x86 they somehow
work both on Linux and Darwin, AFAIU. On ppc that is not the case, which is
particularly painful for users, given that most of the relevant hardware is
not the fastest (especially G4) and MacPorts has no buildbots for powerpc
(MacPorts not being the point here: nobody has buildbots).
Full bootstrap of guile takes 10+ hrs to build even on G5 Quad, I recall on
2.3 DC it was close to 20 if not 24. On a single G4 it will probably take
several days.
If this could be addressed by someone from upstream, so that we can have an
option to build it without a full bootstrap, it would be really helpful.
On Fri, Oct 4, 2024 at 7:49 AM Rob Browning <rlb@defaultvalue.org> wrote:
> John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> writes:
>
> > Is there a chance this particular Debian patch that fixes the segfault on
> > 32-bit big-endian targets could be upstreamed?
>
> It's at been filed upsteam, at least https://debbugs.gnu.org/45214
>
> --
> 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
>
[-- Attachment #2: Type: text/html, Size: 2124 bytes --]
next prev parent reply other threads:[~2024-10-04 14:50 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
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 [this message]
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=CALYdzymLjUgTK6C5yswSJ_drmtL+0RxOU_XG6kj2RtTfgX8tuQ@mail.gmail.com \
--to=vital.had@gmail.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=gsteemso@gmail.com \
--cc=guile-devel@gnu.org \
--cc=rlb@defaultvalue.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.
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).