I fixed the VS2005 build issues I could in r17306, but there are a
couple left...
> > The 2nd issue is zlib123 -- the new ML doesn't like the assembly
> > version (tweaking build_zlib.bat or the generator to not use the
> > assembly version works fine):
> > inffas32.asm(594) : error A2070: invalid instruction operands
> > inffas32.asm(596) : error A2070: invalid instruction operands
> > inffas32.asm(610) : error A2070: invalid instruction operands
> > inffas32.asm(667) : error A2070: invalid instruction operands
> >
These were due to assumed operand sizes which the new assembler won't
assume anymore -- hopefully the next release of zlib will be fixed
(they are aware of the issue). Some info is available at:
http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=6306f7dc-2cc2-4591-bd60-5d802178fdfa
> >
> > The 4th issue is that one of the stats tests is failing -- it seems to
> > be due to a change in how wildcards on the commandline are handled,
> > but I haven't looked at it very closely yet. It does not seem to be
> > an actual problem with any code, just the test, at first glance.
This issue, IMO, is a total bug in VS2005 but MS is saying it is 'by
design'. They have broken wildcard quoting in setargv.obj:
http://lab.msdn.microsoft.com/ProductFeedback/viewfeedback.aspx?feedbackid=1c569ad8-7329-4d95-8588-ad6ed08fe988
If they refuse to fix it, I guess we'll have to expand wildcards
ourselves on Windows? Any better ideas?
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 16 21:11:51 2005