From: martin rudalics <rudalics@gmx.at>
To: Andy Moreton <andrewjmoreton@gmail.com>, emacs-devel@gnu.org
Subject: Re: Current trunk aborts with MinGW
Date: Tue, 30 Sep 2014 17:57:30 +0200 [thread overview]
Message-ID: <542AD2EA.8050708@gmx.at> (raw)
In-Reply-To: <vz1zjdhmbqz.fsf@gmail.com>
>> I have no idea what a mingw toolchain version is.
>
> There are several toolchains:
>
> a) The Mingw project (www.mingw.org):
> - 32bit gcc (i686-pc-mingw32)
>
> b) The Mingw64 project (mingw-w64.sourceforge.net):
> - 32bit gcc (i686-w64-mingw32)
> - 64bit gcc (x86_64-w64-mingw32)
Aha ... that thing printed by `emacs-version' or `system-configuration'.
It's "i686-pc-mingw32" here. Couldn't you try to write a function that
provides more meaningful information here? I always consider w32 bug
reports inferior to the ones for GNU/Linux which IMHO are not entirely
optimal either. Basically, it would be fine to have one function that
gets me, in a nicely formatted way,
- the operating system,
- the revision number,
- the build options,
- the build environment,
- the date of the build
that is, most of the things you asked for.
martin
next prev parent reply other threads:[~2014-09-30 15:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 8:25 Current trunk aborts with MinGW martin rudalics
2014-09-30 13:01 ` Andy Moreton
2014-09-30 13:51 ` martin rudalics
2014-09-30 14:19 ` Andy Moreton
2014-09-30 15:57 ` martin rudalics [this message]
2014-09-30 14:44 ` Eli Zaretskii
2014-09-30 15:58 ` martin rudalics
2014-09-30 16:07 ` Eli Zaretskii
2014-09-30 16:24 ` martin rudalics
2014-09-30 14:02 ` Eli Zaretskii
2014-09-30 13:59 ` Eli Zaretskii
2014-09-30 14:11 ` martin rudalics
2014-09-30 14:36 ` Eli Zaretskii
2014-09-30 14:33 ` Stefan Monnier
2014-09-30 14:42 ` Eli Zaretskii
2014-09-30 15:57 ` martin rudalics
2014-09-30 17:41 ` 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=542AD2EA.8050708@gmx.at \
--to=rudalics@gmx.at \
--cc=andrewjmoreton@gmail.com \
--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).