libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Patch for Portland compiler support


From: Jeff Squyres
Subject: Patch for Portland compiler support
Date: Wed, 17 Nov 2004 09:00:22 -0500

Greetings.

As I've posted to the list before, we use libtool in some fairly large software packages. Thanks for all the excellent work on libtool!

Some of the consumers of our software use the Portland Group compilers (http://www.pgroup.com/). Libtool 1.5.x doesn't seem to recognize these compilers, and therefore doesn't always do the Right Things.

I have *barely* dived into the libtool source, but I have come up with a patch for the current CVS branch-1-5 that seems to make libtool do the Right Things for pgcc on Linux (I didn't try for an analogue on the CVS trunk for the 2.x series). Could this patch be considered for future releases of Libtool?

[5:51] hbar:~/libtool % cvs diff libtool.m4
Index: libtool.m4
===================================================================
RCS file: /cvsroot/libtool/libtool/Attic/libtool.m4,v
retrieving revision 1.314.2.50
diff -u -r1.314.2.50 libtool.m4
--- libtool.m4  19 Sep 2004 12:13:50 -0000      1.314.2.50
+++ libtool.m4  17 Nov 2004 13:54:58 -0000
@@ -4952,6 +4952,11 @@
        _LT_AC_TAGVAR(lt_prog_compiler_pic, $1)='-KPIC'
        _LT_AC_TAGVAR(lt_prog_compiler_static, $1)='-static'
         ;;
+      pgcc*)
+       _LT_AC_TAGVAR(lt_prog_compiler_wl, $1)='-Wl,'
+       _LT_AC_TAGVAR(lt_prog_compiler_pic, $1)='-fpic'
+       _LT_AC_TAGVAR(lt_prog_compiler_static, $1)='-Bstatic'
+        ;;
       ccc*)
         _LT_AC_TAGVAR(lt_prog_compiler_wl, $1)='-Wl,'
         # All Alpha code is PIC.

Please forgive me if this patch is egregiously wrong -- if it is, any advice on making it Right would be tremendously appreciated!

Many thanks for your time.

--
{+} Jeff Squyres
{+} address@hidden
{+} http://www.lam-mpi.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]