>-----Original Message-----
>From: Craig A. Berry [mailto:[EMAIL PROTECTED]]
>Sigh. This is where I usually blow away the build tree, recreate it from
>the archive and try again from scratch.
At 03:49 PM 6/26/2001 -0700, "Maxim, Michael" wrote:
>Actually, I've been doing that each time, just to make sure. :(
Good. You're deleting the directories as well as the files in them?
>Still can't get past the link error, tho the build of perl seems
>to complete a-ok (i.e. perl runs afterwards). Tried doing a manual
>configure/install using GCC, really didn't like that either.
>
>I'm stumped.
Me too. Are you quite sure there are no other errors before the link errors?
Try this. Get to the [.ext.re] directory under your source directory and type
CC/DECC /Include=[]/Standard=Relaxed_ANSI/Prefix=All/noobj/List/show=all/NOANSI_ALIAS -
/Define=(PERL_EXT_RE_BUILD,PERL_EXT_RE_DEBUG,"VERSION=""0.02""","XS_VERSION=""0.02""")
-
/Include=([--]) RE_COMP.c
Send me the resulting re_comp.lis off-list. You may also want to see if the
logical DECC$SYSTEM_INCLUDE or DECC$USER_INCLUDE are defined and if by some
chance the place(s) they point to contain regcomp.h and regnodes.h.
If that doesn't get us anywhere, these are all superstitious things that
should have nothing to do with your problem, but what the heck:
check your disk quota if it's enabled
$ show quota
see if your admin folks will install a later C compiler (current is 6.4) --
there's a remote chance the compiler is having difficulty locating include
directories.
you may not have privs to do this, but you can check for disk corruption with
$ analyze/disk devname:
sacrifice a chicken and sprinkle the blood all over the VAX.
