Re: ncurses-5.6 build problems on Darwin/MacOSX

[sci-fi]

Hi,

I'll get right down to the libtool problem here ... we can talk
about the other configure parms later (mainly they all come from
the way Fink builds ncurses-5.4 which is detailed here:
<http://fink.cvs.sourceforge.net/fink/dists/10.4/stable/main/finkinfo/base/ncurses.info?revision=1.3&view=markup>
in 

particular look for lines labelled "ConfigureParams:" and
"SetLDFLAGS:" etc.).

> [...]
> > checking if you want to build libraries with libtool... 
> > /usr/local/bin/glibtool
> > checking version of libtool... 
> > configure: error: This is not libtool
> > 
> > [~/Projects/ncurses-5.6]root# _
> > <<<<
> > 
> > Here's the config.log from this run:
> ...
> > configure:3845: checking if you have specified an install-prefix
> > configure:3858: result: 
>
> I'd see what's going on in the configure script by going to line 4030,
> and adding a
>         set -x
> line.

Here's the console (Terminal) listing with set -x in effect there:
> > > >
[...]
checking if you have specified an install-prefix... 
+ echo 'configure:4030: checking if you want to build libraries with libtool'
+ echo 'checking if you want to build libraries with libtool... \c'
checking if you want to build libraries with libtool... + test set = set
+ withval=/usr/local/bin/glibtool
+ with_libtool=/usr/local/bin/glibtool
+ echo 'configure:4040: result: /usr/local/bin/glibtool'
+ echo /usr/local/bin/glibtool
/usr/local/bin/glibtool
+ test /usr/local/bin/glibtool '!=' no
+ test /usr/local/bin/glibtool '!=' yes
+ test x/usr/local '!=' xNONE
+ cf_path_syntax=/usr/local
+ case ".$with_libtool" in
+ LIBTOOL=/usr/local/bin/glibtool
+ test -z /usr/local/bin/glibtool
+ LIB_CREATE='${LIBTOOL} --mode=link ${CC} -rpath ${DESTDIR}${libdir} 
-version-info `cut -f1 ${srcdir}/VERSION` -o'
+ LIB_OBJECT='${OBJECTS}.o=.lo)'
+ LIB_SUFFIX=.la
+ LIB_CLEAN='${LIBTOOL} --mode=clean'
+ LIB_COMPILE='${LIBTOOL} --mode=compile'
+ LIB_LINK='${LIBTOOL} --mode=link'
+ LIB_INSTALL='${LIBTOOL} --mode=install'
+ LIB_UNINSTALL='${LIBTOOL} --mode=uninstall'
+ LIB_PREP=:
+ echo 'configure:4133: checking version of libtool'
+ echo 'checking version of libtool... \c'
checking version of libtool... ++ /usr/local/bin/glibtool --version
++ sed -e '2,$d' -e 's/([^)]*)//g' -e 's/^[^1-9]*//' -e 's/[^0-9.].*//'
+ cf_cv_libtool_version=
+ echo 'configure:4140: result: '
+ echo ''

+ test -z ''
+ echo 'configure:4143: error: This is not libtool'
+ echo 'configure: error: This is not libtool'
configure: error: This is not libtool
+ exit 1
+ exit 1
+ exit_status=1
+ echo
+ echo '## ----------------- ##'
+ echo '## Cache variables.  ##'
+ echo '## ----------------- ##'
+ echo
+ case `(ac_space=' '; set | grep ac_space) 2>&1` in
+ sed -n 
's/^\([_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789]*_cv_[_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789]*\)=\(.*\)/\1=\2/p'
+ 

sed '/^$/d' confdefs.h
+ test -s conftest.log
+ echo
+ echo '## ------------ ##'
+ echo '## confdefs.h.  ##'
+ echo '## ------------ ##'
+ echo
+ cat conftest.log
+ echo
+ echo
+ test 0 '!=' 0
+ echo 'configure: exit 1'
+ rm -rf conftest.c conftest.log conftest.o confdefs.h core 'core.*' 
'*.core' 'conf851*'
+ exit 1

# _
<<<<

Okay *now* I remember something about this version of libtool,
I think they changed the --version syntax just a bit:
> > > >
# /usr/local/bin/glibtool --version

ltmain.sh (GNU libtool) 1.5.23a (1.1220.2.416 2006/10/24 20:18:28)

Copyright (C) 2006  Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

# _
<<<<
That's verbatim with extra linefeeds & all.
Yeah I think I hit this before on other projects...

> [...]
> I think the immediate problem is why the configure script's not
> getting the libtool version.

Let's see what we need to do to get it working this far.  There
doesn't seem to be a "short version string" option, so I wonder if
this GNU team knows they may break scripts for not having a
standardised version text.  ;)

So ... what to do, where to go next?  In meantime I could force
configure to simply say 'yes' here and see what comes.  ;)

Thank you.