[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ncurses 5.3 backwards compatibility
From: |
Chris Zubrzycki |
Subject: |
Re: ncurses 5.3 backwards compatibility |
Date: |
Fri, 8 Nov 2002 14:26:36 -0500 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday, November 8, 2002, at 01:56 PM, Thomas E. Dickey wrote:
It appears you're talking about changes I made last year (see 20011208
for instance). Essentially yes a bug - in Mac's runtime loader if the
configure script is reporting things properly. It checks if a
workaround
is needed to link in data items from a shared library, using functions
to wrap them. The workaround has been in ncurses for some time; last
year I added acs_map to this case (cygwin's linker is more-broken than
the previous benchmark ;-).
Comparing with 5.2 though, and seeing the comment about strnames makes
it
apparent that the problem isn't just my changes - the 5.2 version would
have had the same issue with strnames. I suspect that someone tweaked
the 5.2 package (or the linker changed). So that's the issue to
resolve.
Well, the 5.2 package was tweaked, and this time i'm trying to build
using libtool so we get all the correct dynamic libs, but i cannot even
rebuild lynx with 5.3 because of the undefined functions.
what we use for 5.2 is here, and you may be correct, our patch could
have something to do with this:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/fink/dists/10.2/
unstable/main/finkinfo/base/ncurses-5.2-8.info?rev=1.1&content-
type=text/vnd.viewcvs-markup
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/fink/dists/10.2/
unstable/main/finkinfo/base/ncurses-5.2-8.patch?rev=1.1&content-
type=text/vnd.viewcvs-markup
- -chris zubrzycki
- - --
PGP public key: http://homepage.mac.com/beren/publickey.txt
ID: 0xA2ABC070
Fingerprint: 26B0 BA6B A409 FA83 42B3 1688 FBF9 8232 A2AB C070
_________________________________________________
This message is encoded using the Rot-26 encoding method. Unauthorized
decoding of this message may result in extreme penalties under the
DMCA. These penalties include, but are not limited to: US$100,000
fine, life imprisonment, castration, death, limp hair, terminal
halitosis, and amputation of the extremities.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (Darwin)
iD8DBQE9zA/w+/mCMqKrwHARAuHMAJ4kiOnT7NC7gXZnWlotvUu+WObB+ACeMviG
hRzorBGqBGF6O7x1z+2D5Dk=
=AN9o
-----END PGP SIGNATURE-----