unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
To: Corwin Brust <corwin@bru.st>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: limit native compilation - how
Date: Tue, 18 Jan 2022 20:04:09 +0100	[thread overview]
Message-ID: <861r1450ie.fsf@duenenhof-wilhelm.de> (raw)
In-Reply-To: <CAJf-WoSMZ7p=e0JNDzR5QQnm=pw=kNy9t10LS17+cZesp99tfA@mail.gmail.com> (Corwin Brust's message of "Mon, 17 Jan 2022 15:54:55 -0600")

Corwin Brust <corwin@bru.st> writes:

> Home, safe and sound!
Nice to read. :-)

> Here's the "usual" recipe I've been using.  Sometimes (when I screw up
> my build tree) I use "make maintainer-clean" instead of "make clean".
>
> git pull && make clean && ./autogen.sh && ./configure
> --with-native-compilation && make -j 20 NATIVE_FULL_AOT=1

Thanks, that's really helpful for me, but I wanted to inspect your
recipes for doing distros! :-)

> Given a working install of GNU PGP for Windows (which I already had)
> it was quite easy:

There's gpg on MSYS2, my key ID is
8027EC54B495EC88959B97B7B63FB3E2D6A2F7B8, we could sign our respective
keys, if that's helpful..

> Ensure your gpg is working at that you have your keys setup:
>   # gpg --list-keys
> And, given that works correctly, in ~/emacs-upload use something like:
>   # for f in *.zip ; do gpg -b $f ; done
> From there I believe we just need to create the directive files.
> Regarding which, see:
>
>   https://www.gnu.org/prep/maintain/html_node/FTP-Upload-Directive-File.html#FTP-Upload-Directive-File

Oh, what's a directive file?  I'll need to check the documentation..

> OK.  I will create a new thread with Eli to discuss.  I will put you
> in copy (as I assume you are not far behind :)

Great, please do so.

       Dieter

-- 
Best wishes
H. Dieter Wilhelm
Zwingenberg, Germany



  parent reply	other threads:[~2022-01-18 19:04 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-15 15:42 limit native compilation - how Colin Baxter 😺
2022-01-15 15:58 ` Eli Zaretskii
2022-01-15 16:01   ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-15 16:38     ` Eli Zaretskii
2022-01-15 16:51       ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-15 17:55         ` Eli Zaretskii
2022-01-15 18:58           ` Colin Baxter 😺
2022-01-15 19:12             ` Eli Zaretskii
2022-01-15 19:21             ` H. Dieter Wilhelm
2022-01-15 20:31               ` Colin Baxter 😺
2022-01-15 22:15                 ` H. Dieter Wilhelm
2022-01-16  7:13                   ` Eli Zaretskii
2022-01-16  7:15                 ` Eli Zaretskii
2022-01-16  7:41                   ` Colin Baxter 😺
2022-01-16  9:26                     ` Eli Zaretskii
2022-01-17 19:37                     ` H. Dieter Wilhelm
2022-01-17 20:39                       ` Colin Baxter 😺
2022-01-16  8:39               ` Eli Zaretskii
2022-01-16 11:30                 ` H. Dieter Wilhelm
2022-01-16 11:42                   ` Eli Zaretskii
2022-01-16 12:01                     ` H. Dieter Wilhelm
2022-01-16 12:11                       ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 12:17                       ` Eli Zaretskii
2022-01-16 13:24                         ` H. Dieter Wilhelm
2022-01-16 13:36                           ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 13:52                             ` H. Dieter Wilhelm
2022-01-16 13:59                               ` Eli Zaretskii
2022-01-16 18:37                                 ` H. Dieter Wilhelm
2022-01-16 18:46                                   ` Eli Zaretskii
2022-01-17 13:38                                     ` H. Dieter Wilhelm
2022-01-17 13:49                                       ` Eli Zaretskii
2022-01-17 16:11                                         ` H. Dieter Wilhelm
2022-01-17 16:30                                           ` Corwin Brust
2022-01-17 19:03                                             ` H. Dieter Wilhelm
2022-01-17 19:23                                               ` Corwin Brust
2022-01-17 21:54                                               ` Corwin Brust
2022-01-18 14:34                                                 ` Eli Zaretskii
2022-01-18 19:04                                                 ` H. Dieter Wilhelm [this message]
2022-01-17 16:55                                           ` Eli Zaretskii
2022-01-18  2:57                                           ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-01-18  3:22                                             ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 21:49                                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 21:53                                   ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 22:10                                   ` Michael Heerdegen
2022-01-16 13:48                           ` Eli Zaretskii
2022-01-16 17:08                           ` Andy Moreton
2022-01-16 18:09                             ` H. Dieter Wilhelm
2022-01-15 17:55   ` Colin Baxter 😺
2022-01-15 16:01 ` Emanuel Berg via Users list for the GNU Emacs text editor

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=861r1450ie.fsf@duenenhof-wilhelm.de \
    --to=dieter@duenenhof-wilhelm.de \
    --cc=corwin@bru.st \
    --cc=help-gnu-emacs@gnu.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.
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).