From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Niels =?UTF-8?Q?S=C3=B8ndergaard?= <nisoni@algon.dk>
Newsgroups: gmane.emacs.bugs
Subject: bug#48804: 27.2; compilation emacs on macOS
Date: Fri, 4 Jun 2021 15:03:30 +0200
Message-ID: <F7721D5F-968B-40FC-BEEC-90D8720ECF61@algon.dk>
References: <C3993810-F3AE-474E-9DFD-593FB8837901@algon.dk>
 <2AF45A3E-8412-437F-A903-F314C934E618@univie.ac.at>
 <YLlK9Gb+nDvFsJkT@idiocy.org> <8335tyw4mk.fsf@gnu.org>
 <DD6FE42F-2516-40A2-9189-4B9696B705A0@univie.ac.at>
 <BEF6760F-C190-454A-9728-E28E642A6F3E@algon.dk> <834kedn7hx.fsf@gnu.org>
 <3AF5227F-7CBC-4F9A-BB72-E4E92F3BFDBF@idiocy.org> <8335txn73m.fsf@gnu.org>
 <YLojvTT+eZh7FMvn@breton.holly.idiocy.org>
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_E74DB90B-B01E-49CB-AAD3-5EFBAFAD9C80"
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="7888"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: Niels =?UTF-8?Q?S=C3=B8ndergaard?= <nisoni@algon.dk>,
 Konrad Podczeck <konrad.podczeck@univie.ac.at>, 48804@debbugs.gnu.org
To: Alan Third <alan@idiocy.org>
Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jun 04 15:04:27 2021
Return-path: <bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org>
Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org
Original-Received: from lists.gnu.org ([209.51.188.17])
	by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org>)
	id 1lp9Ux-0001qV-Dw
	for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 04 Jun 2021 15:04:27 +0200
Original-Received: from localhost ([::1]:42646 helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org>)
	id 1lp9Uw-0005Uk-FO
	for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 04 Jun 2021 09:04:26 -0400
Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56552)
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
 id 1lp9UZ-0005Tp-5h
 for bug-gnu-emacs@gnu.org; Fri, 04 Jun 2021 09:04:04 -0400
Original-Received: from debbugs.gnu.org ([209.51.188.43]:34252)
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
 (Exim 4.90_1) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
 id 1lp9UY-0002Ub-L2
 for bug-gnu-emacs@gnu.org; Fri, 04 Jun 2021 09:04:02 -0400
Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1lp9UY-0001CB-HC
 for bug-gnu-emacs@gnu.org; Fri, 04 Jun 2021 09:04:02 -0400
X-Loop: help-debbugs@gnu.org
Resent-From: Niels =?UTF-8?Q?S=C3=B8ndergaard?= <nisoni@algon.dk>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@gnu.org
Resent-Date: Fri, 04 Jun 2021 13:04:02 +0000
Resent-Message-ID: <handler.48804.B48804.16228118404586@debbugs.gnu.org>
Resent-Sender: help-debbugs@gnu.org
X-GNU-PR-Message: followup 48804
X-GNU-PR-Package: emacs
Original-Received: via spool by 48804-submit@debbugs.gnu.org id=B48804.16228118404586
 (code B ref 48804); Fri, 04 Jun 2021 13:04:02 +0000
Original-Received: (at 48804) by debbugs.gnu.org; 4 Jun 2021 13:04:00 +0000
Original-Received: from localhost ([127.0.0.1]:45798 helo=debbugs.gnu.org)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <debbugs-submit-bounces@debbugs.gnu.org>)
 id 1lp9US-0001Bq-GF
 for submit@debbugs.gnu.org; Fri, 04 Jun 2021 09:04:00 -0400
Original-Received: from algon.dk ([212.99.233.66]:55696)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <nisoni@algon.dk>) id 1lp9UN-0001Ba-9n
 for 48804@debbugs.gnu.org; Fri, 04 Jun 2021 09:03:55 -0400
Original-Received: from localhost (localhost [127.0.0.1])
 by algon.dk (Postfix) with ESMTP id ADB2A20062;
 Fri,  4 Jun 2021 15:03:45 +0200 (CEST)
X-Virus-Scanned: amavisd-new at algon.dk
Original-Received: from algon.dk ([127.0.0.1])
 by localhost (odin.algon.dk [127.0.0.1]) (amavisd-new, port 10024)
 with LMTP id AYU3EaWcx3mO; Fri,  4 Jun 2021 15:03:44 +0200 (CEST)
Original-Received: from smtpclient.apple (unknown [85.83.136.51])
 by algon.dk (Postfix) with ESMTPA id 879202004F;
 Fri,  4 Jun 2021 15:03:44 +0200 (CEST)
In-Reply-To: <YLojvTT+eZh7FMvn@breton.holly.idiocy.org>
X-Mailbutler-Message-Id: EC08473E-5291-4823-B2B9-57164D1ABAA5
X-Mailer: Apple Mail (2.3654.100.0.2.22)
X-BeenThere: debbugs-submit@debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
X-BeenThere: bug-gnu-emacs@gnu.org
List-Id: "Bug reports for GNU Emacs,
 the Swiss army knife of text editors" <bug-gnu-emacs.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-gnu-emacs>,
 <mailto:bug-gnu-emacs-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-gnu-emacs>
List-Post: <mailto:bug-gnu-emacs@gnu.org>
List-Help: <mailto:bug-gnu-emacs-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-gnu-emacs>,
 <mailto:bug-gnu-emacs-request@gnu.org?subject=subscribe>
Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org
Original-Sender: "bug-gnu-emacs"
 <bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org>
Xref: news.gmane.io gmane.emacs.bugs:208012
Archived-At: <http://permalink.gmane.org/gmane.emacs.bugs/208012>


--Apple-Mail=_E74DB90B-B01E-49CB-AAD3-5EFBAFAD9C80
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

You can=E2=80=99t sat try a newer M! iMac, they were first released i =
april/may this year=E2=80=A6...
The big different is, that it is Apple Silicon and using ARM ( i blive =
it=E2=80=99s proparivary, but very near ARM V9)
mvh
Niels

> Den 4. jun. 2021 kl. 14.59 skrev Alan Third <alan@idiocy.org>:
>=20
> On Fri, Jun 04, 2021 at 03:32:13PM +0300, Eli Zaretskii wrote:
>>> I believe that libgccjit only just added support for M1 processors
>>> in the last week or two, and for whatever reason the Intel
>>> emulation on the Macs doesn't work with the older libgccjit
>>> either.
>>=20
>> Should we mention this in NEWS, where we announce native-compilation
>> support? Knowing the prerequisites is important to avoid false
>> expectations and frustration.
>=20
> Probably, unfortunately I can't work out what the actual prerequisites
> are. I don't have an M1 Mac so I can't even work it out myself.
>=20
> Perhaps someone else can help us, unless just saying "try a newer
> version on M1 Macs" is acceptable?
> --=20
> Alan Third


--Apple-Mail=_E74DB90B-B01E-49CB-AAD3-5EFBAFAD9C80
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">You =
can=E2=80=99t sat try a newer M! iMac, they were first released i =
april/may this year=E2=80=A6...<br class=3D""><div>The big different is, =
that it is Apple Silicon and using ARM ( i blive it=E2=80=99s =
proparivary, but very near ARM =
V9)</div><div>mvh</div><div>Niels</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">Den 4. jun. 2021 kl. 14.59 =
skrev Alan Third &lt;<a href=3D"mailto:alan@idiocy.org" =
class=3D"">alan@idiocy.org</a>&gt;:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">On =
Fri, Jun 04, 2021 at 03:32:13PM +0300, Eli Zaretskii wrote:<br =
class=3D""><blockquote type=3D"cite" class=3D""><blockquote type=3D"cite" =
class=3D"">I believe that libgccjit only just added support for M1 =
processors<br class=3D"">in the last week or two, and for whatever =
reason the Intel<br class=3D"">emulation on the Macs doesn't work with =
the older libgccjit<br class=3D"">either.<br class=3D""></blockquote><br =
class=3D"">Should we mention this in NEWS, where we announce =
native-compilation<br class=3D"">support? Knowing the prerequisites is =
important to avoid false<br class=3D"">expectations and frustration.<br =
class=3D""></blockquote><br class=3D"">Probably, unfortunately I can't =
work out what the actual prerequisites<br class=3D"">are. I don't have =
an M1 Mac so I can't even work it out myself.<br class=3D""><br =
class=3D"">Perhaps someone else can help us, unless just saying "try a =
newer<br class=3D"">version on M1 Macs" is acceptable?<br class=3D"">-- =
<br class=3D"">Alan Third<br class=3D""></div></div></blockquote></div><br=
 class=3D""><img =
src=3D"https://mailbutler.org/p/2762cbfd-4f65-4598-ba7e-895584a9eece/60235=
c45-7726-4de7-b37a-69ed57673256/t.gif" align=3D"left" width=3D"0" =
height=3D"0" style=3D"width:0;height:0;border:0;" title=3D"" alt=3D"" =
id=3D"MailbutlerTrackingPixel" class=3D"lp-rich-link"><!--How does =
Mailbutler=E2=80=99s Email Tracking Work?
We, Mailbutler GmbH, Akazienstra=C3=9Fe 3a, 10823 Berlin/Germany offer =
Mailbutler, a software extension (plugin) for the Apple Mail program, =
which, inter alia, enables mail senders to see when, where, how often =
and on which device the recipient has opened (read) an email. If the =
sender activates the email tracking for a specific email, Mailbutler =
includes a hidden image (also referred to as web-bug or 1-pixel image) =
with a unique mail-ID into the outgoing mail. Once the recipient views =
the email, the recipient=E2=80=99s mail client or web service sends a =
request to our server in order to load the hidden image. Our servers =
collect and store the mail-ID, email client information, device =
information and the date and time of such request. We pass on the =
date/time, email client information, device information and mail-ID to =
the Mailbutler software of the sender where it is linked to the specific =
email and enables the Mailbutler software to display the read date/time, =
email client information, device information and location based on the =
IP address.

What data is collected?
Through Mailbutler=E2=80=99s email tracking the sender obtains the =
information when the recipient has first opened the email. We, =
Mailbutler, only store the mail-ID together with the corresponding read =
date/time and device information. We do not collect further data. We are =
unable to link this information to an individual email address of the =
sender or recipient, since the mail-ID is linked to a specific email =
only locally at the device of the Mailbutler installation at the sender.

Who is responsible?
We do not collect information that can be attributed to an individual =
and therefore do not collect, process or use personal data. However, the =
sender of an email using Mailbutler=E2=80=99s email tracking =
functionality may collect, process and use personal data. It is the =
sender=E2=80=99s responsibility to ensure that the use of the email =
tracking functionality is in compliance with any laws applicable to the =
sender, in particular data protection laws. This may require the sender =
to inform the recipient about the tracking, to offer an opt-out or to =
obtain prior consent.

How can the Recipient avoid Email Tracking?
Recipients can configure their email client (e.g. Outlook) or web =
service (e.g. googlemail) so that by default images contained in emails =
are not loaded. Please see the configurations menu and manual of your =
email client or web service for details. Alternatively, you can contact =
the sender and object to any future email tracking. Please note that we, =
Mailbutler, can not deactivate email tracking for specific e-mail =
address since we have no access to information about the sender or =
recipient of tracked emails.
--></body></html>=

--Apple-Mail=_E74DB90B-B01E-49CB-AAD3-5EFBAFAD9C80--