From: Sergey Fedorov <vital.had@gmail.com>
To: Gordon Steemson <gsteemso@gmail.com>
Cc: guile-devel@gnu.org, Rob Browning <rlb@defaultvalue.org>
Subject: Re: Guile 3.0.10 fails to build for powerpc-darwin (3.0.9 built earlier)
Date: Sun, 1 Sep 2024 16:43:49 +0800 [thread overview]
Message-ID: <CALYdzykPAbuqx2xr0zSHgkQPzzmyjpUoedJWhMwR6UAn8Xm-KQ@mail.gmail.com> (raw)
In-Reply-To: <75D8FC68-B975-4808-9552-9F8CE163D169@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1491 bytes --]
On Sun, Sep 1, 2024 at 3:09 PM Gordon Steemson <gsteemso@gmail.com> wrote:
> So, it won't build on 32-bit Mac OS... but not for any sane reason;
> rather, it won't build because it's failing to pick up the appropriate
> gnulib shims to make the 'environ' function visible. I mean, HOW? It
> works just fine on 64-bit! Is this something that the ./configure script
> does differently between the two?
>
Just in case, is it correctly defined?
It should be this for Apple:
```
#include <crt_externs.h>
#define environ (*_NSGetEnviron())
```
I.e. different from Linux one.
>
> > On Aug 31, 2024, at 10:45 PM, Gordon Steemson <gsteemso@gmail.com>
> wrote:
> >
> > Hello all,
> >
> >> Date: Fri, 30 Aug 2024 21:27:16 -0500
> >> From: Rob Browning <rlb@defaultvalue.org>
> >>
> >> 3.0.10 does appear to be broken on 32-bit architectures:
> >> https://buildd.debian.org/guile-3.0
> >>
> >> So if that's what you have, you may need to stick with 3.0.9 for now. I
> >> plan to downgrade debian/unstable to 3.0.9 this weekend.
> >
> > I did get it to build for 32-bit as part of a multi-architecture ("fat
> binary") build, using the old Apple GCC. I don't seem to have needed to do
> anything special to make it work, though I obviously do need to test
> whether it will build 32-bit only. I will report back if any relevant
> observations come up – as noted, it’s a 13-hour build, so this won’t be
> immediate.
> >
> > Gordon S.
>
[-- Attachment #2: Type: text/html, Size: 2458 bytes --]
next prev parent reply other threads:[~2024-09-01 8:43 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 [this message]
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
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=CALYdzykPAbuqx2xr0zSHgkQPzzmyjpUoedJWhMwR6UAn8Xm-KQ@mail.gmail.com \
--to=vital.had@gmail.com \
--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).