On Tue, 15 Feb 2005, Craig Berry wrote:

> On Tuesday, February 15, 2005, at 03:21PM, John E. Malmberg wrote:
>
> >I am noticing on a previous build that a number of the tests are failing
> >when you build with the VMS DEBUG option, and the tests use PERLSHR
> >instead of DBGPERLSHR.  When the tests are run using DBGPERLSHR they
> >succeed.  This is telling me that when the VMS DEBUG option is selected,
> >PERLSHR is not being built correctly.
>
> When you configure and build for the VMS debugger, there is not supposed
> to be a PERLSHR.EXE, only DBGPERLSHR.EXE.  If you build in debug
> without configuring for it, you will see the symptoms you describe.
> Switching back and forth between a debug and non-debug build without
> reconfiguring is not supported.  If you are configuring for the
> debugger and still seeing this issue, please holler.

Hollering.

I did a MMK realclean between the builds, which gets rid if any
dangling executables.

Directory BUILD_ROOT:[000000]

DBGMINIPERL.EXE;1       7269  15-FEB-2005 16:20:51.35  (RWED,RWED,RE,)
DBGPERL.EXE;1             52  15-FEB-2005 16:21:56.35  (RWED,RWED,RE,)
DBGPERLSHR.EXE;1        7469  15-FEB-2005 16:21:54.61  (RWED,RWED,RE,)
MINIPERL.EXE;3          4111  15-FEB-2005 16:54:19.09  (RWED,RWED,RE,)
MINIPERL.EXE;2          4111  15-FEB-2005 16:54:17.57  (RWED,RWED,RE,)
MINIPERL.EXE;1          3873  15-FEB-2005 16:20:53.78  (RWED,RWED,RE,)
NDBGperl.exe;1             8  15-FEB-2005 16:21:56.72  (RWED,RWED,RE,)
PERL.EXE;1                 6  15-FEB-2005 16:54:46.44  (RWED,RWED,RE,)
PERLSHR.EXE;1           3441  15-FEB-2005 16:54:45.53  (RWED,RWED,RE,)

Ahhh....

Apparently the MMK/FROM_SOURCES TEST is creating the non debug version for
it's use, and that is causing the tests to fail.

So I need to modify that command in my master build file to also
have the /macro=__DEBUG__=1 for that MMK command.

> BTW, the simplest way to configure for the debugger is:
>
> $ @configure -"Dusevmsdebug" -"des"

Currently I am using:

$   @build_root:['root']configure.com -"Dusevmsdebug" -
    "-Dunlink_all_versions" "-Duselargefiles" "-Dusesymlinks" -
    "-Dusehardlinks" "-Dosname=GNV" "-de"

If the GNV build works, I am going to make it imply:
unlink_all_versions, uselargefiles, usesymlinks, and usehardlinks,
and possibly enabling all 64 bit options.

I plan to also put in vms.h the #ifdef for the GNV environment to set
the C feature logical to default to that all file specifications will
be in UNIX format and case sensitive, unless the user overides this.

-John
[EMAIL PROTECTED]
Personal Opinion Only

Reply via email to