Bad regexp in Libtool m4 for PGI compiler version checking

[Jeff Squyres]

The PGI suite is soon to release version 10.0, which causes some  
problems for the regexps in Libtool's m4.  Here's an example  
(forwarded from one of PGI's engineers):

>          pgCC* | pgcpp*)
>            # Portland Group C++ compiler
>            case `$CC -V` in
>            *pgCC\ [1-5]* | *pgcpp\ [1-5]*)
>              prelink_cmds_CXX='tpldir=Template.dir~
>                rm -rf $tpldir~

The problem is that this first regexp (in a series of version-checking  
regexp's) now matches PGI v10.  Here's one possible solution:

>          pgCC* | pgcpp*)
>            # Portland Group C++ compiler
>            case `$CC -V` in
>            *pgCC\ [10]* | *pgcpp\ [10]*)
>              archive_cmds_CXX='$CC -shared $pic_flag $predep_objects
> $libobjs $deplibs $postdep_objects $compiler_flags ${wl}-soname
> ${wl}$soname -o $lib'
>              archive_expsym_cmds_CXX='$CC -shared $pic_flag
> $predep_objects $libobjs $deplibs $postdep_objects $compiler_flags
> ${wl}-soname ${wl}$soname ${wl}-retain-symbols-file ${wl} 
> $export_symbols
> -o $lib'
>            ;;
>            *pgCC\ [1-5]* | *pgcpp\ [1-5]*)
>              prelink_cmds_CXX='tpldir=Template.dir~
>                rm -rf $tpldir~
> ...etc.

We don't know if this would be the preferred Libtool way to fix the  
issue, but it is definitely *one* way to fix it.  :-)

Regardless, note that PGI has supplied what they believe to be the  
correct options and variables for their v10 series.  So even if the  
exact methodology/style isn't what is desired, the data that is needed  
is provided and can be plugged into any style that you want.

Thanks!

--
Jeff Squyres
address@hidden