From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: "Niels Søndergaard" <solengen@me.com>,
"Eli Zaretskii" <eliz@gnu.org>,
65836@debbugs.gnu.org
Subject: bug#65836: 30.0.50; compiling emacs 30.0.50 fails
Date: Tue, 24 Oct 2023 10:34:55 +0200 [thread overview]
Message-ID: <m2lebsto40.fsf@Pro.fritz.box> (raw)
In-Reply-To: <CADwFkmk-Bry2xrd+P+QGS6ACoKBPJBhL6f2d0URGSqj8BuANQw@mail.gmail.com> (Stefan Kangas's message of "Tue, 24 Oct 2023 01:22:34 -0700")
Stefan Kangas <stefankangas@gmail.com> writes:
> Niels Søndergaard <solengen@me.com> writes:
>
>> It is still not working, and I wrote sep 9:
>
> Thanks, it seems like this email didn't reach the list.
>
>> The build-script is at https://algon.dk/_doc/build.zsh
>> and the whole log file at https://algon.dk/_doc/Emacs-build-2023-09-09c.log
>
> Your build script is quite complex. Could you please reduce this down
> to a minimal set of steps needed to reproduce this?
>
> FWIW, I can build Emacs on two different macOS machines (12.7 and 14.0),
> so I suspect there is something wrong in your local environment.
Also, the build log shows that frame.c gets a patch applied.
prev parent reply other threads:[~2023-10-24 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 7:54 bug#65836: 30.0.50; compiling emacs 30.0.50 fails Niels Søndergaard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-09 8:11 ` Eli Zaretskii
2023-10-23 20:04 ` Stefan Kangas
2023-10-24 7:48 ` Niels Søndergaard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-24 8:05 ` Gerd Möllmann
2023-10-24 8:56 ` Niels Søndergaard via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-24 9:03 ` Gerd Möllmann
2023-10-24 8:22 ` Stefan Kangas
2023-10-24 8:34 ` Gerd Möllmann [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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2lebsto40.fsf@Pro.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=65836@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=solengen@me.com \
--cc=stefankangas@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).