libtool-patches
[Top][All Lists]
Advanced

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

Re: CC can be a program name *with arguments*


From: Bob Friesenhahn
Subject: Re: CC can be a program name *with arguments*
Date: Wed, 2 Mar 2005 09:30:26 -0600 (CST)

On Wed, 2 Mar 2005, Peter O'Gorman wrote:

Bob Friesenhahn wrote:
I want, in a libtoolized project,
 ../configure CC='pgcc-78.9 -foo-option'
to succeed in choosing Portland compiler options.  No multiple compilers
involved here.

Libtool also lives as a stand-alone utility, which may be installed!


I am going to stand up again (because I like being shot down) and ask if the "stand alone utility" bit is really necessary. I think I asked this before and was told to shut up :)

I doubt that anyone here told you to "shut up". We are more imaginative than that.

Libtool has been a "stand alone utility" since day one. That was its original focus. We don't control who uses it and can have no way of knowing who is using libtool stand-alone.

Libtool is a better linker than 'gcc' or 'ld' since it understands libtool dependency information. As a result, it may be used by simple programs/packages which don't even include so much as a configure script or for "proprietary" in-house uses where there is no need to "configure" the software.

Libtool does not handle changes to compiler switches very well, -m to gcc will confuse it, it certainly can not handle multiple compilers, why not just stop pretending that it is useful as a stand alone utility?

It is useful as a stand alone utility, but certainly the user must take care to use only the tools it was configured with.

Bob
======================================
Bob Friesenhahn
address@hidden, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/




reply via email to

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