[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ncurses-5.6 build problems on Darwin/MacOSX
From: |
sci-fi |
Subject: |
Re: ncurses-5.6 build problems on Darwin/MacOSX |
Date: |
Fri, 29 Dec 2006 11:44:46 -0600 |
User-agent: |
Unison/1.7.7 |
Hi,
On Fri, 29 Dec 2006, address@hidden wrote:
> 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.
It looks as if it's putting out a blank line at the beginning.
That's easy to fix in a sed script.
I'll try to see if they know about it in some manner at
savannah.gnu.org...
> # _
> <<<<
> 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. ;)
It's a problem with more than one. I've made 2-3 fixes to keep up with
gcc.
I'm thinking to ask in the gnulib maillist if we should be
considering an autoconf or m4 macro or ~something~ so these tools
can produce "expectable" (predictable) version output (heh, does
that make sense? ;) ). I think if it's in gnulib, the other GNU
projects might be easier to be talked into using it.
> So ... what to do, where to go next? In meantime I could force
> configure to simply say 'yes' here and see what comes. ;)
That "should" work, since it's not using the version for anything
specific.
Oh good ... then I've bypassed that one if-fi section e.g.:
--- configure_origg 2006-12-28 09:44:31 -0600
+++ configure 2006-12-29 04:51:31 -0600
@@ -4139,11 +4139,11 @@
cf_cv_libtool_version=`$LIBTOOL --version 2>&1 | sed -e '2,$d' -e
's/([^)]*)//g' -e 's/^[^1-9]*//' -e 's/[^0-9.].*//'`
echo "$as_me:4140: result: $cf_cv_libtool_version" >&5
echo "${ECHO_T}$cf_cv_libtool_version" >&6
- if test -z "$cf_cv_libtool_version" ; then
- { { echo "$as_me:4143: error: This is not libtool" >&5
-echo "$as_me: error: This is not libtool" >&2;}
- { (exit 1); exit 1; }; }
- fi
+# if test -z "$cf_cv_libtool_version" ; then
+# { { echo "$as_me:4143: error: This is not libtool" >&5
+#echo "$as_me: error: This is not libtool" >&2;}
+# { (exit 1); exit 1; }; }
+# fi
# special hack to add --tag option for C++ compiler
case $cf_cv_libtool_version in
<<<<
... and the build & install went fine -- libtool definitely is
very careful about not leaving a missing-lib hole while
installing. As for proof, fwiw, a test shows:
[~/Projects/ncurses-5.6/test]# ./ncurses
Welcome to ncurses 5.6.20061223. Press ? for help.
This is the ncurses main menu
a = keyboard and mouse input test
b = character attribute test
c = color test pattern
d = edit RGB color values
e = exercise soft keys
f = display ACS characters
g = display windows and scrolling
i = test of flushinp()
k = display character attributes
m = menu code test
o = exercise panels library
p = exercise pad features
q = quit
r = exercise forms code
s = overlapping-refresh test
? = repeat this command summary
q
<<<<
Some of the playthings here esp. tclock has issues erasing the
background colours (full single-line black areas), but that might
be an Apple Terminal problem, too (but it's not the same shade of
black I've set for Terminal to use, just so I can tell these
things ;) ). I'll research it further as I can...
fwiw I never can afford a $pay-for$ ADC account so I'm not privvy
to see what's going on with Leopard, but I'm hoping we can
band-together and get Apple to update every open project they
provide as part of OSX. Only method I know is to fill-out
bugreports separately requesting each piece to be updated...
Thank you for helping. I would like to document another headache
with ncurses-5.x but I'll scoot for now to get some R&R. :)