From: Robert Pluim <rpluim@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
57563@debbugs.gnu.org, "Bob Kline" <bkline@rksystems.com>
Subject: bug#57563: 28.1; macOS - layout warning at startup
Date: Thu, 08 Sep 2022 15:55:43 +0200 [thread overview]
Message-ID: <87lequ7yxs.fsf@gmail.com> (raw)
In-Reply-To: <87k06e7zw0.fsf@yahoo.com> (Po Lu's message of "Thu, 08 Sep 2022 21:35:11 +0800")
>>>>> On Thu, 08 Sep 2022 21:35:11 +0800, Po Lu <luangruo@yahoo.com> said:
Po Lu> Bob Kline <bkline@rksystems.com> writes:
>> No version built with the tool we've been using displays the unwanted
>> warning (including emacs 28). On the other hand, "brew install
>> homebrew/cask-versions/emacs-nightly" gives me emacs-29.0.50 WITH the
>> warning. I did a little digging to try and find out which options were
>> used for building emacs, but didn't have any luck. I suppose I could
>> file a bug with the Homebrew folks. Anyone have any experience with
>> that? Is the Homebrew team as responsive as this one? 😉
Po Lu> Maybe it could be related to the version of Mac OS that the Emacs binary
Po Lu> was built on?
Po Lu> There are two knobs, MAC_OS_X_VERSION_MAX_ALLOWED and
Po Lu> MAC_OS_X_VERSION_MIN_REQUIRED, that change Emacs and operating system
Po Lu> behavior. But I can never remember what they mean. What if you build
Po Lu> Emacs with them defined to the same values that the Homebrew package was
Po Lu> built with?
emacssformacosx.com says they build on both macOS 10.10 and 10.14 and
then bundle those two version together. I canʼt find the actual
scripts used to produce the builds.
Po Lu> I don't think you can obtain their values from binaries, so you will
Po Lu> probably have to ask the person who built the Homebrew package.
Yes
Robert
--
next prev parent reply other threads:[~2022-09-08 13:55 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 14:39 bug#57563: 28.1; macOS - layout warning at startup Bob Kline
2022-09-05 1:36 ` Lars Ingebrigtsen
2022-09-05 12:13 ` Bob Kline
2022-09-05 19:01 ` Lars Ingebrigtsen
2022-09-06 1:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-06 13:45 ` Bob Kline
2022-09-07 1:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-07 5:04 ` Gerd Möllmann
2022-09-07 12:17 ` Bob Kline
2022-09-07 12:28 ` Gerd Möllmann
2022-09-07 12:47 ` Bob Kline
2022-09-07 12:56 ` Gerd Möllmann
2022-09-07 12:59 ` Bob Kline
2022-09-07 13:03 ` Robert Pluim
2022-09-07 13:10 ` Bob Kline
2022-09-07 13:19 ` Robert Pluim
2022-09-07 13:22 ` Bob Kline
2022-09-07 13:45 ` Gerd Möllmann
2022-09-07 13:47 ` Gerd Möllmann
2022-09-07 13:41 ` Gerd Möllmann
2022-09-07 13:48 ` Bob Kline
2022-09-07 13:58 ` Gerd Möllmann
2022-09-07 14:18 ` Bob Kline
2022-09-07 18:01 ` Bob Kline
2022-09-08 5:02 ` Gerd Möllmann
2022-09-08 8:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-08 13:04 ` Bob Kline
2022-09-08 13:19 ` Gerd Möllmann
2022-09-08 13:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-08 13:55 ` Robert Pluim [this message]
2022-09-08 14:02 ` Bob Kline
2022-09-08 16:12 ` Bob Kline
2022-09-08 20:00 ` Bob Kline
2022-09-09 5:02 ` Gerd Möllmann
2022-09-09 8:55 ` Robert Pluim
2022-09-11 11:13 ` Bob Kline
2022-09-12 5:58 ` Gerd Möllmann
2022-09-12 11:11 ` Bob Kline
2022-09-12 11:35 ` Gerd Möllmann
2022-09-15 13:33 ` Bob Kline
2022-09-16 5:56 ` Gerd Möllmann
2022-09-16 13:16 ` Bob Kline
2022-09-16 13:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-16 13:41 ` Bob Kline
2022-09-16 14:33 ` Bob Kline
2022-09-17 1:57 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lequ7yxs.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=57563@debbugs.gnu.org \
--cc=bkline@rksystems.com \
--cc=gerd.moellmann@gmail.com \
--cc=luangruo@yahoo.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.