all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Gomes, Pedro (NSN - PT/Amadora)" <pedro.gomes@nsn.com>
Cc: 7363@debbugs.gnu.org
Subject: bug#7363: Problems compiling newest Emacs 23.2.90 pretest with MSVC 10 Express
Date: Wed, 10 Nov 2010 07:47:30 -0500	[thread overview]
Message-ID: <E1PGA5K-0003P5-IG@fencepost.gnu.org> (raw)
In-Reply-To: <9469E027990D5C418DC69525CC9780840190D99D@DEMUEXC035.nsn-intra.net> (pedro.gomes@nsn.com)

> Date: Wed, 10 Nov 2010 12:58:12 +0100
> From: "Gomes, Pedro (NSN - PT/Amadora)" <pedro.gomes@nsn.com>
> Cc: 
> 
> I'm having a lot of problems compiling Emacs 23.2.90 with MSVC 10
> Express. Are there already any already recepies/patches/hacks for it

MSVC 10 (actually MSVC 8.0 and later) is not supported, sorry.  See
nt/INSTALL.  MS modified their run-time libraries too extensively, in
particular in the area of memory management, and that screws up the
dumped Emacs too much.  With a MinGW port of GCC freely available and
fully supported, the motivation of Emacs maintainers to cater to MSVC
is below zero, so no one cared enough to overcome these problems.

> shall I dig deeper and provide some patches ?

I would suggest instead to install MinGW and use that.  Of course, if
you do decide to fix the MSVC build and provide patches to do that, we
will consider them for inclusion.  Thanks in advance.





  reply	other threads:[~2010-11-10 12:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 11:58 bug#7363: Problems compiling newest Emacs 23.2.90 pretest with MSVC 10 Express Gomes, Pedro (NSN - PT/Amadora)
2010-11-10 12:47 ` Eli Zaretskii [this message]
     [not found]   ` <9469E027990D5C418DC69525CC9780840190DA36@DEMUEXC035.nsn-intra.net>
2010-11-10 13:07     ` bug#7363: Problems compiling newest Emacs 23.2.90 pretest with MSVC10 Express 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=E1PGA5K-0003P5-IG@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=7363@debbugs.gnu.org \
    --cc=pedro.gomes@nsn.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 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.