Re: Fw: CONS on OpenVMS

[Steven Knight]

Donald--

> I did play with the contruct. file in an attempt to setup a simple hello
> world for the VMS environment.  My work resulted in a greater understanding
> of the flexibility of CONS.  However, I ended with a deep recursion on
> subroutine "futil::mkdir" at cons. line 2927.

What was the configuration that caused this recursion?

> I'm attempting to perform the following commands in CONS:
>
> 1) I want to compile the hello.c code into hello.obj
> $ CC /STAND=VAXC HELLO.C

Is the .OBJ extension a VMS standard, or just your preference for
your particular build configuration?

> I included the "Objects" method, otherwise CONS didn't know how to construct
> the .OBJ file.

You can use the SUFOBJ construction variable to set the object
suffix to '.OBJ'.  That should eliminate having to use the Objects
method explicitly.

Actually, Cons uses the Perl %Config values for the default file
extensions.  Hence my question above; if .OBJ is the VMS standard
suffix for object files, and the Perl port to OpenVMS used that
file suffix, then it *should* have been stored in Perl's %Config
hash and Cons would have used the .OBJ extension by default.

You can see what Cons is picking up from Perl as its default object
file extension by executing:

        perl -e "use Config; print $Config{_o}"

(or the equivalent, if that idiom doesn't work on OpenVMS for some
reason).  Actually, I'd be interested to know what the VMS version
of Perl has in the entir %Config hash...

BTW, what version of Perl is this (perl -v)?

Thanks for getting Cons to work on VMS.  More portability is good...

        --SK