On Wed, 27 Apr 2005, Craig A. Berry wrote:

> At 12:58 AM -0400 4/27/05, John E. Malmberg wrote:
> >[only monitoring vmsperl list]
> >Abe Timmerman wrote:
> >>Hi,
> >>
> >>I still can't build bleadperl on the VAX (without /ignore=warning):
> >>
> >>CC/DECC /Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=GLOBALS.obj/NoList/
> >>Define=PERL_CORE GLOBALS.C
> >>
> >>%VCG-W-BADPSECT, The program section(psect) specified by this statement has
> >>                conflicting 'nowrite' attributes with another definition
> >>                of the same program section.
> >>                At line number 1002 in BLDROOT:[000000]PERLAPI.H;1.
> >
> >That looks like a serious programming error, any idea what is causing it?
> >
> >It looks like it is saying that the same storage has been declared both as 
> >readonly and as writable at the same time.
>
> More specifically, the likely cause would be something declared EXT in
> one place and EXTCONST elsewhere, which on VMS means globaldef and
> globaldef readonly, respectively.  But the error message is less than
> helpful in identifying the problem since it points you to the last
> line in perlapi.h, well after any declarations.  Nothing pops out in
> a quick look at Abe's listing file, but I'll try to dig into more
> later.

Much of the time the line number is set to point to just before the next
line that the compiler sees that generates code or data.
You have to read backwards skipping all non-code or data generating
pre-processor statements.

I am noticing that in 5.8.6, EXTERN.H and INTERN.H have different definitions
for EXTCONST that might produce that type of error message if they got
mixed.

At the moment I can not think of an DECC ANSI acceptable syntax to replace this
usage of globalref/globaldef.

In ANSI mode, I think that specifying the psect name requires a #pragma which
needs to be on it's own line, but I would have to look that up to be sure.

Also, check to see if the symbol "readonly" is being defined to something else,
as I have encountered that as a problem on other open source products.

-John
[EMAIL PROTECTED]
Personal Opinion Only

Reply via email to