This is the mail archive of the
mailing list for the Cygwin project.
Re: [HEADSUP] Dropping libopenssl098 from distro
- From: Ken Brown <kbrown at cornell dot edu>
- To: cygwin-apps at cygwin dot com
- Date: Fri, 30 Jan 2015 08:25:49 -0500
- Subject: Re: [HEADSUP] Dropping libopenssl098 from distro
- Authentication-results: sourceware.org; auth=none
- References: <20150114141344 dot GG15791 at calimero dot vinschen dot de> <87ppahz3kt dot fsf at Rainer dot invalid> <20150114172404 dot GN15791 at calimero dot vinschen dot de> <87h9vtz254 dot fsf at Rainer dot invalid> <54B6DD5D dot 4060705 at cornell dot edu> <54C25113 dot 10200 at cornell dot edu> <54CA9721 dot 6090200 at cornell dot edu> <20150130094148 dot GO14265 at calimero dot vinschen dot de>
On 1/30/2015 4:41 AM, Corinna Vinschen wrote:
On Jan 29 15:25, Ken Brown wrote:
On 1/23/2015 8:48 AM, Ken Brown wrote:
My guess is correct. lisp.exe uses bit 31 (counting from the LSB) as a marker
during garbage collection, and this is incompatible with Cygwin's use of high
memory for the heap. I think I know how to fix this (by defining
LINUX_NOEXEC_HEAPCODES in the Cygwin build), but I haven't finished testing it yet.
I've now built clisp-2.48 with this change (32-bit only), and I've tested it
as well as I can, given that I'm not a clisp user. The build passes all but
a handful of about 12,000 tests, so I think it's probably OK. (None of the
test failures involved crashes.)
Sounds great to me (not being a clisp user myself).
I'm attaching the patches that I applied (on top of Reini's patches) in
order to make the build succeed. I also had to use libdb4.5 instead of
Is that ok? I mean, shouldn't a package always try to use the latest
version? What's the problem you're observing ? Maybe Volker can help
The clisp-2.48 code uses some macros and structures that are defined in the
db4.5 headers but have changed or disappeared in db4.8. I'll see if I can
figure out how to update the code for db4.8.