public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Gerrit P. Haase" <gp@familiehaase.de>
To: "Albert L. Wagner" <alwagner@uark.edu>
Cc: Cygwin <cygwin@cygwin.com>,
	"ruby-talk@ruby-lang.org" <ruby-talk@ruby-lang.org>
Subject: Re: Compiling Berkeley db for Ruby under Cygwin
Date: Fri, 04 Jan 2002 15:23:00 -0000	[thread overview]
Message-ID: <2326966686.20020105002608@familiehaase.de> (raw)
In-Reply-To: <3C34978F.B943BF96@uark.edu>

Hallo Albert,

Am 2002-01-03 um 18:40 schriebst du:

> Even as a Linux user, I probably stay as confused about compiling
> under cygwin as some windows users. I cannot figure out just
> where the linker is looking to find cygwin-ruby16.

1. Use the correct linker flag `-L/path/to/librubys.a/' and look
   if there is a lib named libcygwin-ruby16.a, isn't the name of
   the import lib librubys.a or was it changed since 1.6.5 and 1.6.6?
2. use `my' ruby-1.6.5 package which is available at this URI:
   http://familiehaase.de/cywgin/ruby/ and installs the lib and
   headers and dll in `cygwin-usual' places (/usr/local/lib/ruby/...,
   /usr/local/bin)
3. Build ruby yourself:
   ./configure --enable-shared
   make
   make test
   make install

Gerrit
-- 
=^..^=                                        mailto:gp@familiehaase.de


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  parent reply	other threads:[~2002-01-04 23:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-03  9:38 Albert L. Wagner
2002-01-03 15:28 ` Gerrit P. Haase
2002-01-04 15:23 ` Gerrit P. Haase [this message]
2002-01-04 15:46   ` Gerrit P. Haase
2002-01-04 22:38     ` Charles Wilson
2002-01-05  3:35       ` Gerrit P. Haase
2002-01-03 15:11 Gareth Pearce

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2326966686.20020105002608@familiehaase.de \
    --to=gp@familiehaase.de \
    --cc=alwagner@uark.edu \
    --cc=cygwin@cygwin.com \
    --cc=ruby-talk@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).