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: Albert Chin
Subject: Re: CC can be a program name *with arguments*
Date: Thu, 3 Mar 2005 09:21:28 -0600
User-agent: Mutt/1.5.6i

On Thu, Mar 03, 2005 at 01:49:20AM -0500, Charles Wilson wrote:
> I have a few concerns about removing this functionality: namely, I 
> maintain a bunch of cygwin packages, and some of those use libtool but 
> not automake (nor, in one case, autoconf).  Namely, libjpeg(*) and 
> ncurses; I'm sure there are others.
> 
> (*) libjpeg builds its own libtool during configure, but it's too old to 
> build DLLs on cygwin so I replace it on-the-fly with the "installed" 
> version of libtool.  Can't relibtoolize or autoconf because libjpeg 
> ships ONLY the configure script, not configure.in/ac.
> 
> Breaking this behavior would make that much harder -- and would probably 
> force me to give up on providing shared libraries for ncurses, at the 
> very least.  But, because ncurses is a dependency of so many other 
> packages -- and because libtool won't link a DLL if it has non-DLL 
> dependencies -- this would cause havoc and ripple thru the whole cygwin 
> distro.  Similar effects may occur on other systems -- unless somebody 
> wants to fork the upstream ncurses and make it use the "full" autotool 
> system; the current maintainer's position on automake is quite clear.

I have the configure.in for jpeg and a patch for proper libtool
support in ncurses if you're willing to change your mind :)

-- 
albert chin (address@hidden)




reply via email to

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