unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.g0@libero.it>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs build fails [MSYS2/MINGW64]
Date: Sun, 28 Apr 2019 20:30:37 +0300	[thread overview]
Message-ID: <83sgu2t4ua.fsf@gnu.org> (raw)
In-Reply-To: <1479130385.1253666.1556469684608@mail.libero.it> (message from Angelo Graziosi on Sun, 28 Apr 2019 18:41:24 +0200 (CEST))

> Date: Sun, 28 Apr 2019 18:41:24 +0200 (CEST)
> From: Angelo Graziosi <angelo.g0@libero.it>
> Cc: emacs-devel@gnu.org
> 
> > Thanks.  But please in the future report bugs to the bug tracker using
> > "M-x report-emacs-bug RET".
> 
> I don't see how.. I am non inside Emacs when building a new Emacs... I don't think MinTTY understands that...

It doesn't have to be from the same Emacs which crashes, it can be a
different version, if the problematic version cannot be built.



  reply	other threads:[~2019-04-28 17:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-28 15:37 Emacs build fails [MSYS2/MINGW64] Angelo Graziosi
2019-04-28 16:10 ` Paul Eggert
2019-04-28 16:43   ` Angelo Graziosi
2019-04-29 11:53   ` Angelo Graziosi
2019-04-29 12:49     ` martin rudalics
2019-04-29 14:53       ` Eli Zaretskii
2019-04-29 19:38         ` Paul Eggert
2019-04-30 15:45           ` Eli Zaretskii
2019-04-30 16:49             ` Paul Eggert
2019-04-30 16:53               ` Eli Zaretskii
2019-05-01  8:28           ` martin rudalics
2019-04-28 16:21 ` Eli Zaretskii
2019-04-28 16:41   ` Angelo Graziosi
2019-04-28 17:30     ` Eli Zaretskii [this message]
2019-04-28 21:22       ` Angelo Graziosi
2019-04-28 21:24       ` Angelo Graziosi
2019-04-29  2:29         ` Eli Zaretskii
2019-04-29 14:54     ` Eli Zaretskii
2019-04-28 17:46 ` Stephen Leake
2019-04-29 14:56   ` 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

  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=83sgu2t4ua.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=angelo.g0@libero.it \
    --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 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).