From: "Mattias Engdegård" <mattiase@acm.org>
To: mituharu@math.s.chiba-u.ac.jp
Cc: 37483@debbugs.gnu.org
Subject: bug#37483: [PATCH] macOS build error (aligned_alloc)
Date: Mon, 23 Sep 2019 11:14:55 +0200 [thread overview]
Message-ID: <CD28871F-204E-4A3A-B1E7-8F11EFF2B6BF@acm.org> (raw)
In-Reply-To: <dcf310ba0ab32a65a6e5289c119f9978.squirrel@weber.math.s.chiba-u.ac.jp>
22 sep. 2019 kl. 22.14 skrev mituharu@math.s.chiba-u.ac.jp:
>
> You would need to install the Command Line Developer Tools with
> "xcode-select --install". In general this is necessary when the
> macOS version is older than the newest one Xcode supports. In
> the case of Xcode 11, it is macOS 10.15.
>
> Actually you don't need Xcode for building Emacs, but the Command
> Line Developer Tools would be sufficient.
Thank you, this is useful to know.
Even so, doesn't it make sense to make the configure script work with tools that support newer OS versions? After all, we are not talking about cross-tools or tools that can only generate code for newer versions. If I want to use the most recent toolchain for my OS, these (Xcode 11) tools are the ones to use.
I first tried some other workarounds: configuring with -Werror=unguarded-availability-new in CFLAGS will prevent HAVE_DECL_ALIGNED_ALLOC from being defined, but HAVE_ALIGNED_ALLOC is not affected because its config check doesn't include the standard header (by design).
next prev parent reply other threads:[~2019-09-23 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 17:25 bug#37483: [PATCH] macOS build error (aligned_alloc) Mattias Engdegård
2019-09-22 20:14 ` mituharu
2019-09-23 9:14 ` Mattias Engdegård [this message]
2019-09-23 18:37 ` Alan Third
2019-09-23 19:53 ` Mattias Engdegård
2019-09-23 20:02 ` Paul Eggert
2019-09-24 11:08 ` Mattias Engdegård
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=CD28871F-204E-4A3A-B1E7-8F11EFF2B6BF@acm.org \
--to=mattiase@acm.org \
--cc=37483@debbugs.gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
/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.