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: Mon, 29 Apr 2019 05:29:03 +0300 [thread overview]
Message-ID: <83o94ptuhc.fsf@gnu.org> (raw)
In-Reply-To: <1965363156.1241128.1556486696014@mail.libero.it> (message from Angelo Graziosi on Sun, 28 Apr 2019 23:24:55 +0200 (CEST))
> Date: Sun, 28 Apr 2019 23:24:55 +0200 (CEST)
> From: Angelo Graziosi <angelo.g0@libero.it>
> Cc: emacs-devel@gnu.org
>
> > 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.
>
> but the working copy here (built on March 30) has a different configuration.. I wonted to reproduce the issu in the simplest manner: ./configure && make..
That's okay: it's the best you can do when the problematic
configuration doesn't build.
The main reason for my request is to have the bugs recorded and
discussed on the bug forum, where they belong.
next prev parent reply other threads:[~2019-04-29 2:29 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
2019-04-28 21:22 ` Angelo Graziosi
2019-04-28 21:24 ` Angelo Graziosi
2019-04-29 2:29 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o94ptuhc.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 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.