7:56 p.m.
Ben,
My INCLUDE and LIB variables were setup using %VCINSTALLDIR% instead
of d:\ap\vs2k3.net and, although the VCINSTALLDIR variable was
defined, somehow it didn't get replaced anymore. Beats me.
I changed all references to the variable into the actual value of
the variable, and bingo, that did it.
I am compiling right now and will post the result when I am done.
Looks good so far.
Thanks for the help, sorry for the noise on the list: I really
should have found this myself. But I did not realise there was
something changed in my environment, and as I was trying a new
version of XEmacs, I immediately assumed XEmacs was the culprit.
Just shoot me and be done with it! :)
Anyway, thanks!
Guido
Ben Wing wrote:
OK. My options to cl are identical to yours so it's not that.
Guido, have you set the INCLUDE and LIB environment variables properly?
For running a command-line make, these need to be set in your
environment (Start->Settings->Control
Panel->System->Advanced->Environment Variables). If you type `set' at
the command prompt, it should show you your env. vars.
mine look like
INCLUDE=C:\Program Files\Microsoft Visual Studio .NET
2003\VC7\ATLMFC\INCLUDE;C:\Program Files\Microsoft Visual Studio .NET
2003\VC7\INCLUDE;C:\Program Files\Microsoft Visual Studio .NET
2003\VC7\PlatformSDK\include\prerelease;C:\Program Files\Microsoft
Visual Studio .NET 2003\VC7\PlatformSDK\include;C:\Program
Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\include
LIB=C:\Program Files\Microsoft Visual Studio .NET
2003\VC7\ATLMFC\LIB;C:\Program Files\Microsoft Visual Studio .NET
2003\VC7\LIB;C:\Program Files\Microsoft Visual Studio .NET
2003\VC7\PlatformSDK\lib\prerelease;C:\Program Files\Microsoft Visual
Studio .NET 2003\VC7\PlatformSDK\lib;C:\Program Files\Microsoft Visual
Studio .NET 2003\SDK\v1.1\lib
[if the line gets broken, sorry; each should be one long line]
There's a file called vsvars32.bat in `/Program Files/Microsoft Visual
Studio .NET 2003/Common7/Tools' (or somewhere similar) that shows you
how to set up these vars.
Guido Van Hoecke wrote:
>
>
> Ben Wing wrote:
>
>> 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.
>
>
>
> D:\src\XEmacs\xemacs-21-5-22-cucumber\nt>nmake -f xemacs.mak VERBOSECC=1
> nmake -f xemacs.mak VERBOSECC=1
>
> Microsoft (R) Program Maintenance Utility Version 7.10.3077
> Copyright (C) Microsoft Corporation. All rights reserved.
>
> vcversion.c
> Creating D:\src\XEmacs\xemacs-21-5-22-cucumber\lib-src\config.values
> --------------------------------------------------------------------
> OS version:
>
> Microsoft Windows XP [Version 5.1.2600]
> OS: Windows_NT
>
> XEmacs 21.5-b22 "cucumber" (+CVS-20051006) configured for
> `i586-pc-win32'.
>
> Building XEmacs using "nmake".
> Building XEmacs using make flags " ".
> Building XEmacs in source tree
> "D:\\src\\XEmacs\\xemacs-21-5-22-cucumber".
> For src, using compiler "cl -nologo -W3 -DSTRICT -O2 -G5 -Ob2 -MD
> -c -TP -ID:\src\XEmacs\xemacs-21-5-22-cucumber\nt\inc
> -ID:\src\XEmacs\xemacs-21-5-22-cucumber\src -I"d:\src\xpm-3.4k"
> -I"d:\src\xpm-3.4k\lib" -I"d:\src\libpng-1.2.8"
-I"d:\src\zlib-1.2.1"
> -I"d:\src\tiff-3.7.1\libtiff" -I"d:\src\jpeg-6b"
> -I"d:\src\compface-1.5.1" -I"d:\src\zlib-1.2.1" -DHAVE_MS_WINDOWS
> -DHAVE_MENUBARS -DHAVE_SCROLLBARS -DHAVE_TOOLBARS -DHAVE_WIDGETS
> -DHAVE_DIALOGS -DHAVE_XPM -DFOR_MSW -DHAVE_GIF -DHAVE_PNG -DHAVE_TIFF
> -DHAVE_JPEG -DHAVE_XFACE -DHAVE_ZLIB -DHAVE_NATIVE_SOUND -DMULE
> -DERROR_CHECK_ALL -DPDUMP -DSYSTEM_MALLOC -DWIN32_LEAN_AND_MEAN
> -DWIN32_NATIVE -Demacs -DHAVE_CONFIG_H
> -DPATH_VERSION=\"21.5-b22\"
> -DPATH_PROGNAME=\"xemacs\"
> -DEMACS_VERSION=\"21.5-b22\" -DEMACS_PROGNAME=\"xemacs\"
> -DSTACK_TRACE_EYE_CATCHER=xemacs_21_5_b22_i586_pc_win32
> -DPATH_PREFIX=\"..\" -DEMACS_MAJOR_VERSION=21
> -DEMACS_MINOR_VERSION=5 -DEMACS_BETA_VERSION=22
> -DXEMACS_CODENAME=\""cucumber"\"
> -DXEMACS_EXTRA_NAME=\"(+CVS-20051006)\"
> -DEMACS_CONFIGURATION=\"i586-pc-win32\"
>
-DPATH_PACKAGEPATH=\""~\\.xemacs;;d:\\ap\\XEmacs\\site-packages;d:\\ap\\XEmacs\\mule-packages;d:\\ap\\XEmacs\\xemacs-packages"\"".
>
> For lib-src, using compiler "cl -nologo -W3 -DSTRICT -O2 -G5 -Ob2
> -MD -ID:\src\XEmacs\xemacs-21-5-22-cucumber\lib-src
> -ID:\src\XEmacs\xemacs-21-5-22-cucumber\src -DHAVE_CONFIG_H
> -DWIN32_NATIVE".
> Compiling as C++.
> Installing XEmacs in "d:\\ap\\XEmacs\\XEmacs-21-5-native-mule-latest".
> Package path is
>
"~\\.xemacs;;d:\\ap\\XEmacs\\site-packages;d:\\ap\\XEmacs\\mule-packages;d:\\ap\\XEmacs\\xemacs-packages".
>
> Compiling in support for Microsoft Windows native GUI.
> Compiling in international (MULE) support.
> Compiling in support for XPM images.
> Compiling in support for GIF images.
> Compiling in support for PNG images.
> Compiling in support for TIFF images.
> Compiling in support for JPEG images.
> Compiling in support for X-Face message headers.
> Compiling in support for GZIP compression/decompression.
> Compiling in support for toolbars.
> Compiling in support for dialogs.
> Compiling in support for widgets.
> Compiling in support for native sounds.
> Using portable dumper.
> Using system malloc.
> Using DLL version of C runtime library.
> Compiling in extra internal error-checking.
> NOTE: ---------------------------------------------------------
> NOTE: Compiling in support for runtime error-checking.
> NOTE: XEmacs will run noticeably more slowly as a result.
> NOTE: Error-checking is on by default for XEmacs beta releases.
> NOTE: ---------------------------------------------------------
> Compiling with optimization.
> --------------------------------------------------------------------
> A subdirectory or file D:\src\XEmacs\xemacs-21-5-22-cucumber\nt\obj
> already exists.
> cl -nologo -W3 -DSTRICT -O2 -G5 -Ob2 -MD
> -ID:\src\XEmacs\xemacs-21-5-22-cucumber\lib-src
> -ID:\src\XEmacs\xemacs-21-5-22-cucumber\src -DHAVE_CONFIG_H
> -DWIN32_NATIVE
> -FeD:\src\XEmacs\xemacs-21-5-22-cucumber\lib-src/make-dump-id.exe
> -FdD:\src\XEmacs\xemacs-21-5-22-cucumber\lib-src/make-dump-id
> D:\src\XEmacs\xemacs-21-5-22-cucumber\lib-src\make-dump-id.c -link
> -incremental:no setargv.obj user32.lib wsock32.lib
> make-dump-id.c
> D:\src\XEmacs\xemacs-21-5-22-cucumber\src\config.h(835) : fatal error
> C1083: Cannot open include file: 'malloc.h': No such file or directory
> NMAKE: fatal error U1077: 'cl' : return code '0x2'
> Stop.
>
> D:\src\XEmacs\xemacs-21-5-22-cucumber\nt>
>
>>
>> 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.
>>>>
>>>
>>
>>
>>
>>
>