[bug-notifications] [perl 0004547]: CSWperl 5.10.1, REV=2010.08.11 incompatible with Sun Studio 11

[Mantis Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4547 
====================================================================== 
Reported By:                ssinyagin
Assigned To:                dam
====================================================================== 
Project:                    perl
Issue ID:                   4547
Category:                   packaging
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
====================================================================== 
Date Submitted:             2010-09-09 11:06 CEST
Last Modified:              2011-01-27 16:41 CET
====================================================================== 
Summary:                    CSWperl 5.10.1,REV=2010.08.11 incompatible with Sun
Studio 11
Description: 
Sun Studio 11 is the last Studio release that is tar archive with solaris
packages. Studio 12 is a huge bourne shell archive, making it tricky to
install on remote systems. In Studio 11, I could simply extract the 3
packages and skip the rest of a half-gig distribution.

A simple program:
#include <perl.h>
int main() {}

now it fails when compiling by
 /opt/SUNWspro/bin/cc -I/opt/csw/lib/perl/5.10.1/CORE xx.c

The compiler reports syntax errors and undefined __attribute__ in
/opt/csw/lib/perl/5.10.1/CORE/perl.h

Also perl -V reports incompatible C flag (-m32).

It will be great to still be able to use Studio 11 with CSWperl.






====================================================================== 

---------------------------------------------------------------------- 
 (0008747) bonivart (manager) - 2011-01-27 16:41
 https://www.opencsw.org/mantis/view.php?id=4547#c8747 
---------------------------------------------------------------------- 
Is this bug ready to be closed?