all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 37483@debbugs.gnu.org
Subject: bug#37483: [PATCH] macOS build error (aligned_alloc)
Date: Mon, 23 Sep 2019 19:37:09 +0100	[thread overview]
Message-ID: <20190923183709.GB53480@breton.holly.idiocy.org> (raw)
In-Reply-To: <CD28871F-204E-4A3A-B1E7-8F11EFF2B6BF@acm.org>

On Mon, Sep 23, 2019 at 11:14:55AM +0200, Mattias Engdegård wrote:
> 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.

The command line tools are closely related to XCode, they’re not old
or obsolete.

-- 
Alan Third





  reply	other threads:[~2019-09-23 18:37 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
2019-09-23 18:37     ` Alan Third [this message]
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=20190923183709.GB53480@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=37483@debbugs.gnu.org \
    --cc=mattiase@acm.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.
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.