X-Spam-Check-By: sourceware.org
Date: Mon, 18 Jun 2007 15:25:47 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: mysql.so: Permission denied (Ruby under Cygwin)
Message-ID: <20070618132547.GA18250@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <387E9FC1619C0849BA8934938037E54F0884D2 AT sv-muc-004 DOT venyon-mail DOT local> <46767F03 DOT 48C33276 AT dessent DOT net> <387E9FC1619C0849BA8934938037E54F0884D7 AT sv-muc-004 DOT venyon-mail DOT local> <20070618130340 DOT GO4179 AT calimero DOT vinschen DOT de> <387E9FC1619C0849BA8934938037E54F0884DA AT sv-muc-004 DOT venyon-mail DOT local> <46768651 DOT 82231835 AT dessent DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46768651.82231835@dessent.net>
User-Agent: Mutt/1.4.2.2i
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Jun 18 06:19, Brian Dessent wrote:
> Ronald Fischer wrote:
> 
> > There is none. I was told by Ruby-Talk people that I should use the
> > Windows
> > gem - it would work fine.
> 
> Ugh.

Indeed, ugh.  Who told you that, some random guy on ruby-talk or
somebody who actually knows what (s)he's talking about?

> You're mixing native win32 stuff with Cygwin stuff.  You're trying to
> load the module into a running copy of a Cygwin ruby but this module
> imports symbols from the other copy of ruby in in C:\ruby185\.  This
> means it probably expects data structures of the native build, and most
> likely will crash or act with very unpredictable behavior when used
> elsewhere.  In general this kind of cross-polination is never a good
> idea.
> 
> The *right* way to do it is to either stick to the win32 build (only) or
> to build all the components that you want to use as Cygwin modules.

Exactly.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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