Mksymlists: dont produce Borland C export symbols if BCC support dropped

Borland C was dropped in Perl 5.16. Underscore prefixed symbols were added
for interworking between BCC DLLs and VC DLLs in P5P ML post
"[PATCH] binary coexistence on win32" by Gurusamy Sarathy. Remove
underscore prefixed symbols if BCC support is impossible on a particular
perl version. This removed a RO litteral string, plus some void * sized
slices in the export table, from every DLL image making them smaller.
Revert "Simulate Module::Install $(PERL) changing."

This reverts commit 1e0d49b8c19fd0ca142b41b8a445d30b93e46679.
(On e.g. Perl 5.10.1 adding -Mstrict to xsubpp causes problems)
Add compat-test for Module::Install behaviour to t/basic.t
Merge pull request #161 from mohawk2/removestricttest

Remove -Mstrict from t/xs.t
Merge pull request #158 from bulk88/master

Mksymlists: dont produce Borland C export symbols if BCC support dropped
Release engineering for v7.01_04
Revert "Move MCR from PERL to PERLRUN on VMS."

This reverts commit 205668e34767e990ed75e204add975b2f217e42b.

This approach isn't going to work because any random module can
specify $(PERL) in the MY namespace code expecting it to work as
a command verb rather than just a path.  For example, Encode does
that in its postamble.

So whenever we parse $(PERL) we'll just have to parse it differently
on VMS.
Handle switches in $(PERL) for VMS.

b4de841e328911 has us parsing options off $(PERL) and then adding
them back.  This has to work a bit differently on VMS because there
must be a command verb rather than just a path to the Perl
executable.

The common convention on VMS is to make "MCR" the command verb,
which basically means run this program and allow it to have
parameters without defining a foreign symbol or adding it to the
command tables.

So "MCR" is removed and then added back, but in fact we prepend it
even if it wasn't there before (for VMS only) because we always need
it and we may not have it in some cases.
Don't quote make in Test::Utils on VMS.

A command verb can't be parsed by the CLI if it has quotes around
it, so don't do that.
Release engineering for v7.01_05
Revert "Resolve issue with test_harness and nmake"

This reverts commit d2370755aef6209efc394332a70e81ac3a648768.

Whilst this fixed the problems with nmake it broke a whole bunch
of other things.

Interestingly changing t/*.t to t\*.t also resolved the problem
with nmake.

Also removing the quotes from around the FULLPERL did too.
There is no way to check whether make is available

... and have it work sanely on Windows

Resign ourselves to just skipping this test when crosscompiling
Resolve the "nmake being broken" issue

There is a bug in nmake that appears if these conditions are met:
1) A command is enclosed in quotes;
2) The first parameter to that command contains a /;

nmake adds a space prior to the first / in the first parameter, if the command is in quotes.

't/*.t' was being passed as 't /*.t'

The solution is to translate '/' to '\' only when the make utility is nmake.
Release engineering for v7.01_06
Change regex to match Manify which is always present, Skip not so.
Release engineering for v7.01_07
Revert "Change regex to match Manify which is always present, Skip not so."

This reverts commit 36db35e5171ac58196c768566a0231e0764c3d5c.

Travis says no, but my setup said yes. Fuck it, put it back.
Added PERL_INSTALL_QUIET to the list of env vars to scrub
Release engineering for v7.01_08
Mark a test in pm_to_blib as TODO