all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arthur Miller <arthur.miller@live.com>
To: Angelo Graziosi <angelo.g0@libero.it>
Cc: emacs-devel@gnu.org,  eliz@gnu.org
Subject: Re: Missing snprintf in ucrt mingw + vc-refresh in find-file hook?
Date: Tue, 13 Feb 2024 23:26:18 +0100	[thread overview]
Message-ID: <DU2PR02MB10109594A9870770FA4CBC2BE964F2@DU2PR02MB10109.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <8cb8fc4f-970c-4505-8b36-7b2dbaaa6b85@libero.it> (Angelo Graziosi's message of "Tue, 13 Feb 2024 23:21:31 +0100")

Angelo Graziosi <angelo.g0@libero.it> writes:

> Il 13/02/2024 23:09, Arthur Miller ha scritto:
>> I was lazy; I just tried git apply ucrt.patch, and it refused; nad I was like
>> 3
>> if-defs; I can just put it in, 30 seconds :). I just build with gcc, so I wasn't
>> interestedin clang patch.
>
> I don't remember well now.. but without the clang patch the build finishes with
> a "...not functional Emacs" message.. maybe the clang patch is not only for
> CLANG... MSYS2 people should explain this..

Ah, there is the answer :). Yes it does; it ended so for me, but everything
seems to work fine.

>> By the way, is there any reason to build with clang instead of gcc? Faster,
>> smaller, better? I never tried to be honest.
>
> they build for different "architecture/systems": ucrt64, clang64, mingw64,
> clangarm64.. They are starting to drop some 32-bit packages. Ask them for other
> details...

Yes, I know they do; I thought you were also. Just wonder if there is any
difference; I am too lazy to build and try myself. Yeah, you are right I should
ask them, but I think I am not that curious :).

> Ciao,
>   Angelo.

Thanks; ciaos.



  reply	other threads:[~2024-02-13 22:26 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12 17:37 Missing snprintf in ucrt mingw + vc-refresh in find-file hook? Angelo Graziosi
2024-02-13 10:49 ` Arthur Miller
2024-02-13 19:00 ` Arthur Miller
2024-02-13 20:01   ` Eli Zaretskii
2024-02-13 22:05     ` Arthur Miller
2024-02-14 14:45       ` Eli Zaretskii
2024-02-14 18:43         ` Arthur Miller
2024-02-13 21:26   ` Angelo Graziosi
2024-02-13 22:09     ` Arthur Miller
2024-02-13 22:21       ` Angelo Graziosi
2024-02-13 22:26         ` Arthur Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-12 10:06 Arthur Miller
2024-02-12 13:44 ` Dmitry Gutov
2024-02-12 13:56   ` Arthur Miller
2024-02-12 14:58     ` Dmitry Gutov
2024-02-12 16:49       ` Eli Zaretskii
2024-02-12 18:05         ` Dmitry Gutov
2024-02-12 19:15           ` Eli Zaretskii
2024-02-12 19:25             ` Dmitry Gutov
2024-02-12 19:34               ` Eli Zaretskii
2024-02-13  9:47       ` Arthur Miller
2024-02-13 13:36         ` Eli Zaretskii
2024-02-13 14:30           ` Arthur Miller
2024-02-13 21:26           ` Dmitry Gutov
2024-02-13 23:10             ` Arthur Miller
2024-02-14  3:42               ` Dmitry Gutov
2024-02-14 21:04                 ` Arthur Miller
2024-02-14 22:37                   ` Dmitry Gutov
2024-02-15 11:16                     ` Arthur Miller
2024-02-14 14:30             ` Eli Zaretskii
2024-02-14 16:36               ` Dmitry Gutov
2024-02-14 16:51                 ` Eli Zaretskii
2024-02-14 17:01                   ` Dmitry Gutov
2024-02-14 17:29                     ` Eli Zaretskii
2024-02-14 21:05                       ` Dmitry Gutov
2024-02-12 14:36 ` Eli Zaretskii
2024-02-13 10:44   ` Arthur Miller
2024-02-13 13:13     ` Eli Zaretskii

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=DU2PR02MB10109594A9870770FA4CBC2BE964F2@DU2PR02MB10109.eurprd02.prod.outlook.com \
    --to=arthur.miller@live.com \
    --cc=angelo.g0@libero.it \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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.
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.