I had this same problem on our VAX. I finally used the http_server account
to compile (with mms) successfully with the following quotas:
Maxjobs: 0 Fillm: 179 Bytlm: 334946
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 164 JTquota: 4096
Prclm: 15 DIOlm: 164 WSdef: 2000
Prio: 4 ASTlm: 170 WSquo: 4000
Queprio: 0 TQElm: 100 WSextent: 16384
CPU: (none) Enqlm: 228 Pgflquo: 150000
I don't know what the minimums are, but these worked for me.
Hope this helps, I know it was pretty frustrating 'til I tried this.
-Bryan
Programmer/Webmaster
New Mexico Military Institute http://www.nmmi.cc.nm.us
101 W College Blvd, Roswell NM 88201-5173 (505) 624-8110
mailto:[EMAIL PROTECTED]
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 30, 2001 3:23 PM
To: [EMAIL PROTECTED]
Subject: Error while building Perl 5.6.0
I decided today to try building 5.6.0 on my VAX (VMS 6.2, DECC 5.7). I
pulled latest.tar.gz and applied the patches from www.crinoid.com. I then
ran CONFIGURE.COM. So far, so good. I then started the build (using MMK)
and it began compiling. It only got, however, as far as OP.C before it
stopped with a "%CLI-F-TEXT, Compiler abort - virtual memory limits
exceeded." I tried it on another VAX (also VMS 6.2 and DECC 5.7) and
encountered the same error at VMS.C. Anyone know the process quota minimums
to compile Perl?
- Paul
