-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Derek,
I'm slow to understand the goal. I'm coming to the conclusion
what you're trying is eliminate the difference between:
*** config.h.in, generated by mkconfig:
as opposed to:
*** config.h.in, generated by mkconfig.pl:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Conrad T. Pino wrote:
| Previously I wasn't aware of the existence of the intermediates on
| UNIX and of course they don't exist on Windows. The commands I ran
| on both Windows and UNIX are:
|
| cd ccvs perl windows-NT/fix-msvc-mak.pl cd windows-NT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Derek,
From: Derek Price [mailto:[EMAIL PROTECTED]
I've attached the diff. Conrad or somebody, would you mind verifying
that after applying this patch (on WOE32, only the two named files will
be relevant)...
Please define the phrase two
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Conrad T. Pino wrote:
|
| Hi Derek,
|
| From: Derek Price [mailto:[EMAIL PROTECTED]
|
| I've attached the diff. Conrad or somebody, would you mind
| verifying that after applying this patch (on WOE32, only the two
| named files will be relevant)...
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Derek,
From: Derek Price [mailto:[EMAIL PROTECTED]
The two files are listed in the subject line. :)
Oops, I need another cup of coffee!! :)
First off, the problem cited in your output is not caused by the patch
I just sent, but I'll
