raindrops RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Jonathan del Strother <maillist@steelskies.com>
To: raindrops@librelist.org
Subject: Re: Compilation on Solaris/SmartOS
Date: Wed, 28 Aug 2013 10:16:37 +0100	[thread overview]
Message-ID: <CAF5DW8+mhi2WVxzXCs4=jMH6_cum64CT53NTmKUeSHoVetQngQ@mail.gmail.com> (raw)
In-Reply-To: 20130827194052.GA22109@dcvr.yhbt.net

>  > I'm not familiar enough with building the atomic libs to say whether
> it's
> > definitely the correct fix, but it seems to work, and the ruby-atomic gem
> > needed something similar :
> > https://github.com/headius/ruby-atomic/blob/master/ext/extconf.rb.   Any
> > thoughts?
>
> How does Ruby 2.0.0 / trunk build?  That also uses __sync_* and I can't
> find -march=native anywhere.
>

Ruby 2 appears to build & run fine... I'm not sure what I'd need to execute
to ensure I run a __sync_* instruction, but messed around with threads &
mutexes without problems.


Interestingly, when I build raindrops with my regular ruby 1.9.3 install,
the generated makefile includes "ARCH_FLAG = -m32", but when I build
raindrops with ruby 2 / trunk, I get "ARCH_FLAGS = -march=i486".  When
built with that flag, Raindrops works fine.


  reply	other threads:[~2013-08-28  9:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27 11:02 Compilation on Solaris/SmartOS Jonathan del Strother
2013-08-27 19:40 ` Eric Wong
2013-08-28  9:16   ` Jonathan del Strother [this message]
2013-08-28 10:13     ` Eric Wong
2013-08-29  9:58       ` Jonathan del Strother

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='CAF5DW8+mhi2WVxzXCs4=jMH6_cum64CT53NTmKUeSHoVetQngQ@mail.gmail.com' \
    --to=maillist@steelskies.com \
    --cc=raindrops@librelist.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.
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).