try running `nmake -f xemacs.mak VERBOSECC=1' and send the results.
this will at least show what flags it's passing to the compiler.
ben
Guido Van Hoecke wrote:
Stephen,
My visual studio is located at
d:\ap\vs2k3.net and I've got
* d:\ap\vs2k3.net\Vc7\include\malloc.h
* d:\ap\vs2k3.net\Vc7\crt\src\malloc.h
and I can still compile my other (c# and cpp) projects without any
problems.
The include, library, path etc directories for visual studio are
registered in the registry.
Guido.
Stephen J. Turnbull wrote:
>>>>>> "Guido" == Guido Van Hoecke <Guido(a)vanhoecke.org>
writes:
>>>>>
>
>
> Guido> d:\src\XEmacs\xemacs-21-5-22-cucumber\src\config.h(835) :
> Guido> fatal error C1083: Cannot open include file: 'malloc.h': No
> Guido> such file or directory
> First guess is that something is unusual about your system. malloc.h
> is required by several standards, I don't see how you can build any
> sizable program if it's not found. You have a current CVS checkout,
> so I'd have to guess the change is due to some of the fiddling that
> Ben did clarify the Makefile for native Windows builds. But I can't
> guess how that could hurt; malloc.h should be on your standard include
> path that the compiler provides.
>
> There don't seem to be any options in the command line the would
> remove the standard include paths.
>
> It would help us if you could find malloc.h on your system and tell us
> where it is so we can make sure that the build is set up to find it.
>