unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Andreas Grünbacher" <andreas.gruenbacher@gmail.com>
Cc: 20681@debbugs.gnu.org, eggert@cs.ucla.edu, nandryshak@gmail.com,
	angelo.graziosi@alice.it
Subject: bug#20681: Build failure [MSYS2/MINGW64, OSX]
Date: Sat, 30 May 2015 15:10:29 +0300	[thread overview]
Message-ID: <83lhg6uuyy.fsf@gnu.org> (raw)
In-Reply-To: <CAHpGcMKc6qmycMQJ59KXawYtUZOwx4yuSXM-vFkYMd41zxYA1w@mail.gmail.com>

> Date: Sat, 30 May 2015 14:02:51 +0200
> From: Andreas Grünbacher <andreas.gruenbacher@gmail.com>
> Cc: Nick Andryshak <nandryshak@gmail.com>, 20681@debbugs.gnu.org, 
> 	Paul Eggert <eggert@cs.ucla.edu>, Angelo Graziosi <angelo.graziosi@alice.it>
> 
> Could you check if coreutils from
> https://github.com/andreas-gruenbacher/coreutils,
> master branch, builds on MinGW? (The upstream version of coreutils doesn't use
> the latest version of gnulib yet, but this version does.)

Coreutils doesn't build with MinGW for ages, so this is not a good
method of investigating the issue, IMO.

> If that fails, what config.h do you get there, and does it differ from
> the config you get with
> git://git.savannah.gnu.org/coreutils.git? Do the Savannah coreutils build?

Please tell what do you want to see in confg.h, specifically.  I can
force the Emacs development head to compile set-permissions.c, so
perhaps Emacs's config.h will do.





  reply	other threads:[~2015-05-30 12:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28 12:55 bug#20681: Build failure [MSYS2/MINGW64, OSX] Angelo Graziosi
2015-05-28 17:47 ` Eli Zaretskii
2015-05-29 12:27   ` Angelo Graziosi
2015-05-29 16:56     ` Paul Eggert
2015-05-29 19:06       ` bug#20681: [PATCH] acl-permissions: Fix build on Mac OS X and older AIX (Bug#20681) Andreas Gruenbacher
2015-05-29 19:09       ` bug#20681: Build failure [MSYS2/MINGW64, OSX] Andreas Grünbacher
2015-05-29 19:45         ` Paul Eggert
2015-05-29 19:56           ` Nick Andryshak
2015-05-29 19:57             ` Andreas Grünbacher
2015-05-30 10:22               ` Eli Zaretskii
2015-05-30 12:02                 ` Andreas Grünbacher
2015-05-30 12:10                   ` Eli Zaretskii [this message]
2015-05-30 13:06                     ` Andreas Grünbacher
2015-05-31 14:29                       ` Eli Zaretskii
2015-05-31 19:18                         ` Andreas Grünbacher
2015-06-01 15:05                           ` Eli Zaretskii
2015-06-01 16:18                             ` Andreas Grünbacher
2015-06-01 17:39                               ` Eli Zaretskii
2015-06-01 18:41                                 ` Andreas Grünbacher
2015-06-01 19:01                                   ` Eli Zaretskii
2015-05-29 21:49           ` Angelo Graziosi

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=83lhg6uuyy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=20681@debbugs.gnu.org \
    --cc=andreas.gruenbacher@gmail.com \
    --cc=angelo.graziosi@alice.it \
    --cc=eggert@cs.ucla.edu \
    --cc=nandryshak@gmail.com \
    /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).