[Top][All Lists]

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

Re: [PATCH] cygwin sharedlib build fixes, terminfo

From: Thomas E. Dickey
Subject: Re: [PATCH] cygwin sharedlib build fixes, terminfo
Date: Sun, 3 Aug 2003 16:23:14 -0400 (EDT)

On Sun, 3 Aug 2003, Charles Wilson wrote:

> Charles Wilson wrote:
> #1) why is ncurses configure determining that CXX should be 'c++' when
> libtool's build procedure auto-found 'g++'?

I'm not sure - I'm on a different system right now (and see that c++ is
a symbolic link), but running the configure script where I am not gives
g++.  So I'll have to look later when I'm back on the Slackware 7.1

> I wonder if this stanza in ncurses configure.in is somehow the culprit:
>          if test "$CXX" = "g++" ; then
>                  AC_PATH_PROG(CXX,g++)
>          fi
>          if test "$CXX" = "g++" ; then
>                  AC_MSG_WARN(ignoring hardcoded g++)
>                  cf_with_cxx=no; CXX=""; GXX="";
>          fi
> #2) How can we make this foolproof in ncurses?  What we really want is
> "if --with-libtool, then make sure that CC,CXX are set to the same value
> as that used by the libtool script we will be using."
> But, we can't just find the libtool script and do a grep on it --
> because it might be a wrapper script.
> Maybe this is just a user warning: "When using --with-libtool, you may
> need to manually set CC and CXX to the values expected by libtool"

it should be automatic...

(but the point was that there's more work to do than simply applying the
patch - last night I also tried the same patch with the automake 1.4.3
that I have for testing, and it didn't build with that either).

T.E.Dickey <address@hidden>

reply via email to

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