state of MSVC patches for HEAD

[Ralf Wildenhues]

Hi Peter, others,

I've decided to start yet another new thread about this neverending
issue.  I've given your patches (and also my pending ones) another test
round, and something seems to be going very wrong.  Since more than just
one thing changed between the last time I tested (and only a couple of
failures occurred there), I may have just done some things wrong, but I
can't see them at the moment.

a) I forgot to patch the old testsuite tests, sorry.  So seeing failures
which account for the missing EXTERN should be OK.  But I don't think
the ones below are those.

b) The first attachment shows a failure of demo-make after demo-static.
This might be a local setup problem or not, I'm not sure.  The same
failure occurs in half the testsuite failing.  For reference, I have
attached as second one my settings of LIB and INCLUDE, which may be
wrong, I don't know.  Some of the libraries exist in both MSVC and the
developer toolkit, and frankly, I don't know what the required order is.
(also watch out for the stupid native language path if you want to try
this for yourself).

c) The third attachment shows a pdemo-make after pdemo-conf failure.
Is this due to the missing EXTERN patch?

d) The fourth attachment shows tagdemo-make after tagdemo-static failing
because of missing libci.  I searched the net, and found the hint that
MS renamed the library to libcp, but forgot to rename all references to
it.  What would I need to do except a "cp libci.lib libcp.lib" in the
corresponding direcory/ies to make this work again?

e) Of the new testsuite, test 12 and 13 seem to pass but silently fail
for me on my slightly out-of-date MinGW/msys installation (next
attachment), it seems because Automake-1.7 is used.  I see MinGW has
1.8.2 for download now; which one did you test with, and do you see this
failure?  This is important, we have to adjust minimum allowed Automake
versions for client packages here 

f) The standalone failure is really weird.  I'd guess it's a merge error
of mine when putting together your outstanding patches..

Finally, I've attached the compressed output of "cvs diff" to show my
merge of your patches plus a couple of pending ones of mine.  And: I've
actually bootstrapped with 1.9.5 and 2.59, so issues related to that
could've shown up as well.

Regarding "test one issue at a time": yes, I should do that.  No, my bug
reports cannot be qualified as decent.  If you want decent ones, you'll
get them, but only much much later.

Any pointers are greatly appreciated!  :)

By the way, can I expect another update on the "link -dump" issue from
you regarding the recent comments from people?

Cheers,
Ralf

demo-make-failure
Description: Text document

init-cl.sh
Description: Bourne shell script

pdemo-make-failure
Description: Text document

tagdemo-make-failure
Description: Text document

am-sub-failure
Description: Text document

standalone-failure
Description: Text document

current-msvc-test.diff.gz
Description: Binary data