[bug-notifications] [pm_cpan_meta 0005024]: Need to modify Config.pm and Config_heavy.pm to get builds to work

Mantis Bug Tracker noreply at opencsw.org
Mon Nov 26 12:49:03 CET 2012

A NOTE has been added to this issue. 
Reported By:                lsiden
Assigned To:                dam
Project:                    pm_cpan_meta
Issue ID:                   5024
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Date Submitted:             2012-11-21 20:50 CET
Last Modified:              2012-11-26 12:49 CET
Summary:                    Need to modify Config.pm and Config_heavy.pm to get
builds to work
I tried to install a Perl module IO::Pty that was unavailable in the dublin
distro and was unable to compile anything.  

First I had to modify /opt/csw/lib/perl/5.10.1/Config.pm to point to the
gcc compiler instead of the one supplied by SunOS.

When trying to install again, CPAN complained that it could not run
/opt/csw/gcc4/bin/gcc although I could run it fine from a shell
command-line.  Inspecting the compile.log file under the build directory
for IO::Tty (the module it was attempting to build as a prerequisite to
IO::Pty) revealed that gcc could not cope with an argument -norunpath. 
There are many others that the Sun version of the C/C++ compiler and ld
will work with but gcc will not.

I am attaching both my modified Config.pm and Config_heavy.pl that allowed
installs requiring compiler runs to proceed successfully.

I believe that this issue applies equally to CPAN and CPANPLUS.

 (0010231) dam (administrator) - 2012-11-26 12:49
The standard SunOS C Compiler is also named Sun Studio or Solaris Studio or
Oracle Studio :-) Depending on the compiler version you may need to make a
link from /opt/SUNWspro to e.g. /opt/solarisstudio12.3.

I don't understand why you mention stlport as this is not related to the
compiler (up to the extend that gcc sun Sun Studio both ship an stlport).

Apart from that we have the module you needed:
Adding a module takes almost no time, so it is probably easiest when you
just drop the modules on #opencsw or on users at .

More information about the bug-notifications mailing list