[Top][All Lists]

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

Re: ncurses 5.3-20030719

From: Thomas E. Dickey
Subject: Re: ncurses 5.3-20030719
Date: Thu, 21 Aug 2003 04:55:50 -0400 (EDT)

On Tue, 19 Aug 2003, Chris Zubrzycki wrote:

> > "--with-libtool" overrides (cancels the effect of) the other 3 models
> > ("--with-shared", "--with-normal" and "--with-debug").  Checking with
> > your options, it seems that the parameter for --with-libtool is
> > confusing
> > my script (it's not looking for a value, so "--with-libtool" gives a
> > value of "yes").  I can modify that.  For a workaround, if you set
> > $LIBTOOL to /usr/bin/glibtool, and use the "--with-libtool" option
> > (and discard "--with-shared"), it should work.
> Ok, well, I tested this. It does not work correctly. It seems to grab
> the directory that libtool is in, but on os x the gnu libtool is called
> glibtool. When I use --with-libtool=/usr/bin/glibtool it seems to
> correctly grab the libtool name and location, but no .la files are
> created. Very odd indeed...

I'll put something in this week's patch to fix it.

> And you stopped making the c++ dynamic lib? What if some apps depend on
> it? Is there an option to re-enable it?

I didn't _stop_: libtool didn't support it.  I'm told that libtool 1.5
does support c++ shared libraries.

T.E.Dickey <address@hidden>

reply via email to

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