X-Spam-Check-By: sourceware.org
Message-ID: <4676E9B3.1B0A87CC@dessent.net>
Date: Mon, 18 Jun 2007 13:23:15 -0700
From: Brian Dessent <brian AT dessent DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
CC: ruby-talk AT ruby-lang DOT org
Subject: Re: mysql.so: Permission denied (Ruby under Cygwin)
References: <387E9FC1619C0849BA8934938037E54F0884D2 AT sv-muc-004 DOT venyon-mail DOT local> <20070618125654 DOT GL4179 AT calimero DOT vinschen DOT de> <387E9FC1619C0849BA8934938037E54F0884DC AT sv-muc-004 DOT venyon-mail DOT local> <f56br8$a6$1 AT sea DOT gmane DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

Andrew DeFaria wrote:

> Ronald Fischer wrote:
> > I see that I am here still on experimental ground. Maybe the idea of
> > using mysql from within Cygwin-Ruby was really not so good in the
> > first place....
> Didn't we, at one time, have an experimental mysql package for Cygwin?
> Well maybe not a package but I believe there was a mysql monitor program
> that could at least talk to my running mysqld on my Linux box. I don't
> recall if there was ever an experimental mysqld for Cygwin. I also seem
> to recall Brian's name in that past conversation...
> 
> I guess another question would be: If we don't have Cygwin packages for
> both mysql client and mysqld then why not (I can hear the "volunteers
> welcomed" from here...)

Well, Cygwin Ports has MySQL client and server packages so you can use
that if you want.

But in this case MySQL was a red herring, it wouldn't have made a
difference either way since the module itself was built against the
native Win32 ruby.  But of course having libmysqlclient-dev (or whatever
the package that contains development headers and import libs is named)
installed would be a prerequisite for properly rebuilding the module.

Brian

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