From: Troex Nevelin <list@mrtech.ru>
To: raindrops@librelist.com
Subject: Re: Build failed on FreeBSD
Date: Mon, 27 Jun 2011 13:00:57 +0300 [thread overview]
Message-ID: <4E0854D9.7020409@mrtech.ru> (raw)
In-Reply-To: 20110625001918.GB18193@dcvr.yhbt.net
On 25/06/2011 03:19, Eric Wong wrote:
> Can you let me know if that fixes things for you? Thanks!
Confirm! Build on FreeBSD 8.0-RELEASE-p4 (GENERIC) successful.
# gem install raindrops
Fetching: raindrops-0.7.0.gem (100%)
Building native extensions. This could take a while...
Successfully installed raindrops-0.7.0
1 gem installed
prev parent reply other threads:[~2011-06-27 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 22:56 Build failed on FreeBSD Troex Nevelin
2011-04-14 0:30 ` Eric Wong
2011-06-23 14:08 ` Troex Nevelin
2011-06-24 8:08 ` Eric Wong
2011-06-25 0:19 ` Eric Wong
2011-06-27 10:00 ` Troex Nevelin [this message]
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
List information: https://yhbt.net/raindrops/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E0854D9.7020409@mrtech.ru \
--to=list@mrtech.ru \
--cc=raindrops@librelist.com \
/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.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/raindrops.git/
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).