emb978@LEAH.ALBANY.EDU (Eric M. Boehm) (01/12/90)
I am trying to compile bison on a VAX 8650, VMS 5.2. When I try to run bison, I run into problems because it is looking for BISON$VERBOSE. I see that this is defined in BISON.CLD but I have no idea what to do with this file! How do I tell bison about the information in BISON.CLD. -- Eric M. Boehm EMB978@leah.Albany.EDU EMB978@ALBNYVMS.BITNET
cooper@hpsrad.enet.dec.com (g.d.cooper in the shadowlands) (01/18/90)
I'm posting this response for two reasons 1) I can't respond via mail and 2) this is a general novice type problem for people running under VMS. In article <9001120502.AA05452@leah.Albany.EDU>, emb978@leah.albany.edu (Eric M. Boehm) writes... >I am trying to compile bison on a VAX 8650, VMS 5.2. When I try to run >bison, I run into problems because it is looking for BISON$VERBOSE. I >see that this is defined in BISON.CLD but I have no idea what to do with >this file! How do I tell bison about the information in BISON.CLD. CLD files are used by the command definition utility to define the interface between command line arguments and the CLI (command line interpreter). You use a .CLD file by issuing a "SET COMMAND filename.cld" command. This modifies the process' DCLTABLES. Please note that it only modifies for the current process level. If you spawn off you lose the definitions. There are ways to fix this but they are either messy or require that you have the appropriate privileges (BYPASS will do). Forced to work with VMS, shades ============================================================================ | He paid too high a price for living | Geoffrey D. Cooper | | too long with a single dream..... | cooper@hpsrad.enet.dec.com | |-------------------------------------| business (508) 467-3678 | | decwrl!hpsrad.enet.dec.com!cooper | home (617) 925-1099 | ============================================================================ Note: I'm a consultant. My opinions are *MY* opinions.