unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Deniz Dogan <deniz.a.m.dogan@gmail.com>
To: emacs-help <help-gnu-emacs@gnu.org>
Subject: Building Emacs with GnuTLS on Windows
Date: Wed, 27 Apr 2011 23:55:51 +0200	[thread overview]
Message-ID: <BANLkTim4zSyQATRjDB1RsWL13ZzKdM=xNg@mail.gmail.com> (raw)

I'm trying to figure out how to build Emacs on Windows with the latest trunk.

c:\repos\emacs-trunk\nt>configure.bat --without-png --without-jpeg
--without-gif --without-tiff --without-xpm --prefix=C:\emacs
--cflags="-IC:/gnutls/include" --lib=C:/gnutls/lib --lib=C:/gnutls/bin
 extrauserlibs:
 extrauserlibs: C:/gnutls/lib
Checking for 'cp'...
Checking for 'rm'...
Checking whether 'gcc' is available...
Checking whether gcc requires '-mno-cygwin'...
Checking whether W32 API headers are too old...

c:\repos\emacs-trunk\nt>gcc -IC:/gnutls/include -c junk.c
Using 'gcc'
Checking for libgnutls...
...GNUTLS header available, building with GNUTLS support.
Generating makefiles
        1 file(s) copied.
config.settings
gmake.defs
..\nt\makefile.w32-in
        1 file(s) copied.
config.settings
gmake.defs
..\admin\unidata\makefile.w32-in
        1 file(s) copied.
config.settings
gmake.defs
..\lib-src\makefile.w32-in
        1 file(s) copied.
config.settings
gmake.defs
..\lib\makefile.w32-in
        1 file(s) copied.
config.settings
gmake.defs
..\src\makefile.w32-in
        1 file(s) copied.
config.settings
gmake.defs
..\doc\emacs\makefile.w32-in
        1 file(s) copied.
config.settings
gmake.defs
..\doc\misc\makefile.w32-in
        1 file(s) copied.
config.settings
gmake.defs
..\doc\lispref\makefile.w32-in
        1 file(s) copied.
config.settings
gmake.defs
..\doc\lispintro\makefile.w32-in
        1 file(s) copied.
config.settings
gmake.defs
..\lisp\makefile.w32-in
        1 file(s) copied.
config.settings
gmake.defs
..\leim\makefile.w32-in
        1 file(s) copied.

Emacs successfully configured.
Run `make' to build, then run `make install' to install.
c:\repos\emacs-trunk\nt>make
makefile:161: *** separator saknas.  Stannar.

The last part means "separator missing. Stopping." This is the latest
commit in the log:

revno: 104031
committer: Eli Zaretskii <eliz@gnu.org>
branch nick: trunk
timestamp: Thu 2011-04-28 00:14:34 +0300
message:
  Support inttypes.h and strtoumax in non-MinGW builds on Windows.

   nt/inc/inttypes.h: New file.
   nt/config.nt (HAVE_DECL_STRTOULL, HAVE_DECL_STRTOUMAX)
   (HAVE_STRTOULL, HAVE_STRTOUMAX): New macros.

I'm reluctant to post this to emacs-devel as I'm not sure it's my
fault, but I get the feeling that the recent changes to the quoting
and GnuTLS for Windows introduced this problem.

-- 
Deniz Dogan



             reply	other threads:[~2011-04-27 21:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 21:55 Deniz Dogan [this message]
2011-04-28  2:56 ` Building Emacs with GnuTLS on Windows Eli Zaretskii
2011-04-28  7:09   ` Deniz Dogan
2011-04-28  7:13     ` Deniz Dogan
2011-04-28 11:23     ` Eli Zaretskii
2011-04-28 18:40       ` Deniz Dogan
2011-04-28 20:22         ` Eli Zaretskii
2011-04-28 20:35           ` Eli Zaretskii
2011-04-29  8:10             ` Deniz Dogan
2011-04-29  9:09               ` 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='BANLkTim4zSyQATRjDB1RsWL13ZzKdM=xNg@mail.gmail.com' \
    --to=deniz.a.m.dogan@gmail.com \
    --cc=help-gnu-emacs@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.
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).