unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: configure.ac needs a change for MinGW
Date: Fri, 15 Jul 2016 22:10:15 +0300	[thread overview]
Message-ID: <831t2u7m5k.fsf@gnu.org> (raw)

win32-uname.[ch] were renamed in Guile 2.0.12, but configure.ac still
references them:

  case $host in
    *-*-mingw*)
      AC_CHECK_HEADER(winsock2.h, [AC_DEFINE([HAVE_WINSOCK2_H], 1,
	[Define if you have the <winsock2.h> header file.])])
      AC_CHECK_LIB(ws2_32, main)
      AC_LIBOBJ([win32-uname])  <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

This causes a fatal error during the build with MinGW.



             reply	other threads:[~2016-07-15 19:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15 19:10 Eli Zaretskii [this message]
2016-07-16  8:37 ` configure.ac needs a change for MinGW Andy Wingo

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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=831t2u7m5k.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.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.
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).