Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Sun, 12 Jun 2005 11:01:00 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: ri dumps core
Message-ID: <20050612090100.GD6568@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <42A9CD52.6050407@elementcxi.com> <20050610173406.GA18885@trixie.casa.cgf.cx> <42AA5A48.5020805@elementcxi.com> <42AA7EE6.DFE3DC85@dessent.net> <20050611164209.GA4092@tishler.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050611164209.GA4092@tishler.net>
User-Agent: Mutt/1.4.2i

On Jun 11 12:42, Jason Tishler wrote:
> On Fri, Jun 10, 2005 at 11:04:22PM -0700, Brian Dessent wrote:
> > Steve Kelem wrote:
> > > Okay.  I ran rebase.  Then I get the same problem.
> > 
> > I just noticed that ruby uses .so for the name of its dynamic modules,
> > but I think the rebaseall script only looks for .dll.  Make a list of
> > all the .so files in the ruby package and pass that to rebaseall with
> > the -T flag, or modify the rebaseall script to look for files ending
> > in .so.  I think this could be a bug in the rebaseall script.
> 
> Do others agree?  If so, then I will change rebaseall to look for .so
> files too.  Any other extensions besides .so?

I agree and *.so is the only other extension, AFAICS.  The next OpenSSL
version will bring them, too.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin@cygwin.com
Red Hat, Inc.

--
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/

