Compiling 21.5 with Visual Studio 2010 (was Re: Generated Headers - Quite the Can of Worms)

[email protected] (Henry S. Thompson)
Newsgroups gmane.emacs.xemacs.beta
Message-ID <[email protected]>
Vin Shelton writes:

> On Thu, Apr 2, 2015 at 11:22 AM, Henry S. Thompson <[email protected]> wrote:
>> The failures I'm now seeing are all somewhere in dumper.c, at various
>> places under pdump_load_finish depending on the values of USE_KKCC and
>> NEW_GC.  I haven't found a setting that works. . .

> First, I would try to build a 32-bit executable without any of your changes.

Doing that, as near as possible.

> I assume you're using the portable dumper.

Yes.

> Suggestion: turn off both KKCC and NEW_GC.

Done.

Still seeing the same failures: temacs.exe runs fine, but the dumped
xemacs.exe can't get started.

Here's how temacs.exe is being linked:

  link -nologo -debug -opt:noref -incremental:no -base:0x1000000
  -stack:0x800000 -entry:mainCRTStartup -subsystem:windows
  -heap:0x00100000 -nodefaultlib setargv.obj
  -pdb:C:\C32\usr\local\src\xemacs-21.5-native\src\temacs.pdb
  -map:C:\C32\usr\local\src\xemacs-21.5-native\src\temacs.map
  -out:C:\C32\usr\local\src\xemacs-21.5-native\src\temacs.exe ...

Any chance those base/stack/heap values are out-of-date?

Any possibility the problem lies somewhere in the vicinity of the
problem reported in the parallel thread for the OS X Yosemite build [1]?  
I.e. is there any equivalent for VC to the -Wl,-no_pie flag Aidan
mentions in that thread?

ht

[1] http://permalink.gmane.org/gmane.emacs.xemacs.beta/39151
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: [email protected]
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.