>Number:         15935
>Category:       pkg
>Synopsis:       perl package's Config.pm holds unusable values for cpp and cppflags
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Mar 15 08:55:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Stoned Elipot
>Release:        NetBSD 1.5.x
>Organization:
SCRIPT, Paris VII University, France
>Environment:
System: NetBSD bandsept 1.5.2 NetBSD 1.5.2 (BANDSEPT) #0: Mon Oct 1 19:35:25 CEST 2001 seb@bandsept:/script/src/nbsd/kernels/build sparc
System: NetBSD runabout 1.5.2 NetBSD 1.5.2 (RUNABOUT) #0: Thu Mar 14 15:20:13 CET 2002 root@runabout:/usr/src/sys/arch/i386/compile/RUNABOUT i386
>Description:
Perl package's Config.pm holds cpp and cpp flags for module compilation -
and more ? (I am not a perl expert). On a 1.5.x systems those values
are not usable together. As an example latest CPAN module IO-Tty -as of this
writing it is at version 1.00, (c.f. http://search.cpan.org/search?dist=IO-Tty)
cannot be installed...
Note: on -current the values are the same but are usable...
>How-To-Repeat:
With a failry recent perl package installed try:
$ perl -V:cpp
cpp='cpp';
$ perl -V:cppflags  
cppflags='-fno-strict-aliasing -I/usr/pkg/include';
$ eval `perl -V:cpp`; eval `perl -V:cppflags` ; $cpp $cppflags /dev/null
cpp: Invalid option `-fno-strict-aliasing'
>Fix:
Unknown. Perhaps our perl's package maintainer should look after this (hint,
hint) ?
>Release-Note:
>Audit-Trail:
>Unformatted:
 1.5.x systems
 From: seb
 Reply-To: seb
 X-send-pr-version: 3.95