Re: Fw: CONS on OpenVMS

[Rajesh Vaidheeswarran]

I have a couple of comments.

> Program $env 'hello.exe', 'hello.obj';
> Objects $env 'hello.c';

I would do that as

Program $env 'hello.exe', $env->Objects('hello.c');

The other thing is that, when you say you are getting a recursion.. it would
help you if you run cons with dependency debugging on (-d)

rv

In a previous message, "Don's Email" writes:

> 
> Thanks for the input from Rajesh and Anthony.
> 
> 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.
> 
> I was unable to repeat the $ENV error I got initially and my perl
> environment does support the assignment to $ENV.  DCL on OpenVMS system uses
> symbols and logicals.  The perl $ENV structure is saved as a system logical.
> 
> I also do have all the required modules installed with perl (ie MD5).  So my
> perl configuration should be compatible with CONS.
> 
> 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
> 2) I then link the resultant hello.obj (not .o as on Unix) to produce
> hello.exe
> $ LINK HELLO.OBJ
> 
> My construct file looks like:
> 
> *** cut here
> $env = new cons(
>            CC => 'CC',
>            CCOM => '%CC /STAND=VAXC /OBJ=.OBJ',
>            LINK => 'LINK',
>            LINKCOM => '%LINK'
>            );
> Program $env 'hello.exe', 'hello.obj';
> Objects $env 'hello.c';
> *** cut here
> 
> I included the "Objects" method, otherwise CONS didn't know how to construct
> the .OBJ file.
> 
> Thanks for any continued assistance on the OpenVMS platform,
> 
> Donald G Plugge
> 
> ----- Original Message -----
> From: "Rajesh Vaidheeswarran" <address@hidden>
> To: "Don's Email" <address@hidden>
> Cc: <address@hidden>
> Sent: Tuesday, May 08, 2001 12:14 PM
> Subject: Re: CONS on OpenVMS
> 
> 
> >
> > I'm not sure anyone has used it outside of Unix/NT as far as I know.
> >
> > That said.. we can do (and in fact, do support) separate compile and
> > link stages..
> >
> > You can pretty much override any cons default (for CC AR LINK, etc..)
> > with stuff that suits your environment.
> >
> > If you tell us what the usable set of defaults is for VMS, we'd be glad
> > to incorporate it. (check cons.pl for @param::defaults - from 2.3.0
> onwards
> > it would be @param::unix and @param::msvc. We could certainly have a
> > @param::vms)
> >
> > However, I don't understand the issue with the $ENV. If you can set
> > the ENV hash from inside  a vanilla perl script, then you should be able
> to
> > do it through cons scripts too. If you can't do it through regular perl,
> > I'd be interested in finding out how perl scripts work on that platform
> > in the first place..
> >
> > One more thing to consider.. we use a few packages like File::Spec and
> > MD5 (or Digest::MD5)..  Make sure they are available for your platform..
> >
> > rv
> >
> > In a previous message, "Don's Email" writes:
> >
> > > Ever since reading the Spring 1998 Perl Journal article about CONS by =
> > > Bob Sidebotham, I've had it in the back of my mind to test the package =
> > > in my OpenVMS environment.  OpenVMS has a make equivalent called MMS, =
> > > however in most cases you can't simply download a Unix make file and use
> =
> > > MMS.  Therefore, I'm not particularly attached to make in the first =
> > > place.
> > >
> > > OpenVMS compiling and linking works differently than its Unix counter =
> > > parts.  Several key issues cause me to wonder if CONS will work in my =
> > > environment.
> > >
> > > 1) The compiler and linker are called separately in OpenVMS.
> > >     Unix: =20
> > > gcc -c hello.c -o hello.o
> > >     OpenVMS:
> > > cc hello.c
> > > link hello.obj
> > >
> > > 2) The object and executable files have different extensions
> > > hello.obj and hello.exe
> > >
> > > 3) Library commands are different
> > > Unix:
> > > ar r libworld.a world.o
> > > OpenVMS:
> > > library/replace/object libworld.olb world.obj
> > >
> > > 4) Perl is called using the "Perl" command
> > > Unix:
> > > cons.pl hello
> > > OpenVMS:
> > > perl cons.pl hello
> > >
> > > In addition, I've receive an error assigning to the $ENV variable on =
> > > this platform and the file naming conventions differ.  The $ in  DCL =
> > > files can cause problems.
> > >
> > > Basically, I'm wonder if anyone has successfully used the CONS package =
> > > on OpenVMS.  Or if anyone has an opinion on how surmountable these =
> > > issues will be in the OpenVMS environment.
> > >
> > > Sincerely,
> > > Donald G Plugge
> >
> > _______________________________________________
> > address@hidden
> > http://mail.gnu.org/mailman/listinfo/cons-discuss
> > Cons URL: http://www.dsmit.com/cons/
> >
> >
> 
> 
> _______________________________________________
> address@hidden
> http://mail.gnu.org/mailman/listinfo/cons-discuss
> Cons URL: http://www.dsmit.com/cons/