Re: [Cvs-dev] GNULIB update patch

[Derek R. Price]

Mark D. Baushke wrote:
>>> What happens if MSVC is installed to a
>>> different directory (through user choice or a change of defaults in
>>> different versions of the program)?  Does MSVC6 support the
>>> #include_next directive?
> 
> I doubt it. To be perfectly honest, I suspect that there is some other
> problem with the HAVE_STDINT_H macro that Jim has not found yet.

Also, I'm forwarding this question from Dennis Jones, who has been
running the nightly CVS builds under Windows.  He wants to know if we
are now requiring MSVC++ 6.0 (as opposed to 5.0).  I believe Conrad was
rebuilding things with 5.0, but if the people doing the work have 6.0,
then I have no problem moving up.  Note that MS support for even MSVC
6.0 ended September of last year
(http://support.microsoft.com/lifecycle/search/?sort=PN&alpha=visual+c%2B%2B),
so it may be reasonable to discontinue support even for 6.0 ourselves.
Especially as it appears that MS now makes a version of MSVC++ 2005
(called MS Visual Studio 2005 Express Edition) available for free
download.  Of course, I have no idea what is necessary to compile CVS
under 2005 Express, if it is even possible.


----- Forwarded Message -----
From: <address@hidden>
To: <address@hidden>; <address@hidden>
Sent: Thursday, June 15, 2006 12:02 AM
Subject: Build CVS (TRUNK) failed.

> > .\windows-NT\canonicalize.c(27) : fatal error C1083: Cannot open include
file: 'shlwapi.h': Permission denied
> > NMAKE : fatal error U1077: 'cl.exe' : return code '0x2'
> > Stop.

Does this mean it is time for me to update the nightly build from VC++ 5.0
to VC++ 6.0?

- Dennis
----- End Forwarded Message -----



Regards,

Derek
-- 
Derek R. Price
CVS Solutions Architect
Get CVS support at Ximbiot <http://ximbiot.com>!
v: +1 248.835.1260
f: +1 248.835.1263
<mailto:address@hidden>