X-Spam-Check-By: sourceware.org Message-ID: <45F5B05C.7020605@cheshirelaw.com> Date: Mon, 12 Mar 2007 12:56:12 -0700 From: "Geoffrey T. Cheshire" User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Problem with ruby and cygssl-0.9.8.dll Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Larry Hall Wrote: > You are right. I should have said this is the right solution > when you have these kinds of problems. The alternate solution > mentioned by Brian is done at the package level and will > generally make this problem disappear transparently for packages > that use it. It must be implemented on a package by package > basis and eventually all packages that come from the Cygwin > distribution will use this. This won't replace the need for > 'rebaseall' though. It will just mitigate it (with some > significance), at least for those packages that come as part of > the distribution. OK, thanks. But if you've used rebaseall once, won't you have to always rebase again any time you update cygwin? That is, if rebaseall arranges each image base in a contiguous block, then you need to rearrange them any time you add/change a dll. This is because you've created a "custom" image base location for each of your images, and --enable-auto-image-base doesn't help. Or am I wrong about this? Thanks again, Geoff -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/