From: Stefan Kangas <stefan@marxist.se>
To: Jean-Christophe Helary <lists@traduction-libre.org>
Cc: Alan Third <alan@idiocy.org>, Emacs Devel <emacs-devel@gnu.org>
Subject: Re: ./configure --with-native-compilation on macos (11.5.2 Big Sur)
Date: Mon, 6 Sep 2021 09:52:02 +0200 [thread overview]
Message-ID: <CADwFkmk59Z3RrpCaMSbnfkU85OH5ACVB3jU0roZ7N1AZsowXSQ@mail.gmail.com> (raw)
In-Reply-To: <78967E72-1A4A-40BC-A822-B4F2A7FA9350@traduction-libre.org>
Jean-Christophe Helary <lists@traduction-libre.org> writes:
> It looks like all the warning are actually quite interesting as far as potential fixes in the various modes are concerned.
>
> Is it encouraged to report the errors or eventually propose fixes ?
Yes, it is encouraged. You should probably double check that they
haven't already been reported, though.
If these packages are on GNU ELPA, you will generally want to report
them with M-x report-emacs-bug or by mailing bug-gnu-emacs@gnu.org.
Otherwise, you will need to report and propose fixes to the
maintainers of that package, who will have their own channels.
next prev parent reply other threads:[~2021-09-06 7:52 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 6:10 ./configure --with-native-compilation on macos (11.5.2 Big Sur) Jean-Christophe Helary
2021-08-16 17:18 ` Alan Third
2021-08-17 0:59 ` Jean-Christophe Helary
2021-08-17 1:02 ` Jean-Christophe Helary
2021-08-17 19:45 ` Alan Third
2021-08-20 6:29 ` Jean-Christophe Helary
2021-08-21 4:43 ` Jean-Christophe Helary
2021-08-21 9:47 ` Alan Third
2021-09-05 13:07 ` Alan Third
2021-09-05 13:22 ` Jean-Christophe Helary
2021-09-06 3:24 ` Alan Third
2021-09-06 3:46 ` Jean-Christophe Helary
2021-09-06 6:27 ` Jean-Christophe Helary
2021-09-06 6:43 ` Jean-Christophe Helary
2021-09-06 7:10 ` Jean-Christophe Helary
2021-09-06 7:34 ` Stefan Kangas
2021-09-06 7:38 ` Jean-Christophe Helary
2021-09-06 7:52 ` Stefan Kangas [this message]
2021-09-06 10:33 ` Eli Zaretskii
2021-09-06 12:12 ` Jean-Christophe Helary
2021-09-06 12:34 ` Eli Zaretskii
2021-09-06 9:45 ` Jean-Christophe Helary
2021-09-06 20:01 ` Alan Third
2021-09-06 23:50 ` Jean-Christophe Helary
2021-09-13 22:55 ` Jean-Christophe Helary
2021-09-08 7:34 ` Lars Ingebrigtsen
2021-09-08 15:31 ` Alan Third
2021-09-08 20:59 ` Alan Third
2021-09-08 21:15 ` Alan Third
2021-09-08 23:44 ` Jean-Christophe Helary
2021-09-09 21:07 ` Alan Third
2021-09-10 0:35 ` Jean-Christophe Helary
2021-09-10 20:53 ` Alan Third
2021-09-11 5:54 ` Eli Zaretskii
2021-09-11 0:30 ` Jean-Christophe Helary
2021-09-11 16:17 ` Alan Third
2021-09-12 8:47 ` Jean-Christophe Helary
2021-09-12 11:59 ` Alan Third
2021-09-13 12:06 ` Jean-Christophe Helary
2021-09-13 18:19 ` Alan Third
2021-09-13 18:42 ` Alan Third
2021-09-13 22:04 ` Jean-Christophe Helary
2021-09-13 22:08 ` Alan Third
2021-09-13 22:24 ` Jean-Christophe Helary
2021-09-13 22:56 ` Jean-Christophe Helary
2021-09-14 15:22 ` Alan Third
2021-09-14 17:10 ` Jean-Christophe Helary
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=CADwFkmk59Z3RrpCaMSbnfkU85OH5ACVB3jU0roZ7N1AZsowXSQ@mail.gmail.com \
--to=stefan@marxist.se \
--cc=alan@idiocy.org \
--cc=emacs-devel@gnu.org \
--cc=lists@traduction-libre.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 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).