Re: Perl 5.12.1 build report

[email protected] ("Craig A. Berry") Thu, 24 Jun 2010 18:48:27 -0500
Newsgroups perl.vmsperl
Message-ID <[email protected]>
On Jun 24, 2010, at 2:03 PM, Mark Berryman wrote:

>
> On Jun 24, 2010, at 12:08 PM, Craig A. Berry wrote:
> .
>>
>> You can get /NAMES=AS_IS by configuring the Perl build with:
>>
>> $ @configure -"Dbe_case_sensitive=Y" -"des"
>
> I tried this once.  The build fails to even build miniperl.

Of course I should know better than to recommend an option I haven't  
tried in years.  I'll take a look.

> The missing GLOBALS module is caused by the fact that, when built on  
> an ODS-5 disk, the filenames are all lowercase so they are entered  
> into the library in lowercase.  This doesn't happen when built on an  
> ODS-2 disk, of course, but the rest of the errors do.  At least some  
> of the errors are caused by VMS.C undefining what it learned from  
> the system include files and then redefining without the lowercase  
> to uppercase definition the include files do.  Here is an extract  
> from the MMS file I use to build libtidy, which is required by  
> HTML::Tidy.  It addresses the first problem regardless of what type  
> of build disk is being used.
>
> .c.obj :
>        @ if f$parse(f$search("$(MMS$SOURCE)"),,,"NAME") .nes. f 
> $edit(f$parse(f$search("$(MMS$SOURCE)"),,,"NAME"),"UPCASE") then  
> rename $(MMS$SOURCE) 'f$edit("$(MMS$SOURCE)","UPCASE")
>        $(CC) $(DBGOPT) $(CFLAGS) $(MMS$SOURCE)
>
> .obj.olb :
>        $(LIBR)$(LIBRFLAGS) $(MMS$TARGET) $(MMS$SOURCE)

Interesting.  I think I would rather do it on the obj.olb rule than  
the .c.obj rule; somehow changing the names of object files seems less  
intrusive since those are just intermediate build products.


>

________________________________________
Craig A. Berry
mailto:[email protected]

"... getting out of a sonnet is much more
  difficult than getting in."
                  Brad Leithauser