Hi again all-
Checked this:
$ search *.h pl_regkind, pl_simple, pl_varies
******************************
TEMP_DATA:[3WEEK_TEMP.SOURCE]REGCOMP.H;1
EXTCONST U8 PL_varies[];
EXTCONST U8 PL_varies[] = {
EXTCONST U8 PL_simple[];
EXTCONST U8 PL_simple[] = {
******************************
TEMP_DATA:[3WEEK_TEMP.SOURCE]REGNODES.H;1
EXTCONST U8 PL_regkind[];
EXTCONST U8 PL_regkind[] = {
$ cc/ver
DEC C V5.6-003 on OpenVMS VAX V7.1
Same as what Peter found basically. I also logged in /nocomm and ran mms
clean
then mms again, still bombs with the same link error. Any other ideas?
Regards,
m2.
-----Original Message-----
From: Peter Prymmer [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 25, 2001 5:51 PM
To: Craig A. Berry
Cc: Maxim, Michael; [EMAIL PROTECTED]
Subject: RE: Kit to build perl + entensions
On Mon, 25 Jun 2001, Craig A. Berry wrote:
> At 2:56 PM -0700 6/25/01, Maxim, Michael wrote:
> > same link error. :/ Any ideas?
> >
> >Link /NoTrace/NoMap /Shareable=[--.LIB.AUTO.RE]PL_RE.EXE
> >re.opt/Option,[--]perlshr_attr.opt/Option
> >%LINK-W-NUDFSYMS, 3 undefined symbols:
> >%LINK-I-UDFSYM, PL_REGKIND
> >%LINK-I-UDFSYM, PL_SIMPLE
> >%LINK-I-UDFSYM, PL_VARIES
>
> These are all constants and should be defined in include files in
> your main source directory like so:
>
> $ search *.h pl_regkind, pl_simple, pl_varies
>
> ******************************
> D0:[CRAIG.KITS.PERLBUILD.SOURCE]REGCOMP.H;1
>
> EXTCONST U8 PL_varies[];
> EXTCONST U8 PL_varies[] = {
> EXTCONST U8 PL_simple[];
> EXTCONST U8 PL_simple[] = {
>
> ******************************
> D0:[CRAIG.KITS.PERLBUILD.SOURCE]REGNODES.H;1
>
> EXTCONST U8 PL_regkind[];
> EXTCONST U8 PL_regkind[] = {
>
> Possibly something is messed up with the definitions of EXTCONST or
> U8. I've certainly never seen anything quite like this problem.
> Peter, you did get a successful build on VAX 7.1?
Of perl yes. But I was using DEC C V5.3-006. The build with
build_perl.com hung later on something SDA1.c (or somesuch) in a module.
Unfortunately I nuked the build directory to make room for perl@10930.
Peter Prymmer
