raindrops RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: raindrops@librelist.org
Subject: Re: Rainbow gem install on solaris failed
Date: Thu, 19 Jan 2012 19:37:40 +0000	[thread overview]
Message-ID: <20120119193740.GA23333@dcvr.yhbt.net> (raw)
In-Reply-To: CAK0mJ0yJOG-xFejP87T=0i86VsdHfMZrcLPKO=yH5NP5qeAijQ@mail.gmail.com

Anjana Sarkar <anjanadeb@gmail.com> wrote:
> *I do have gcc 4+ installed , how do I tell mkmf to use that?*
> *mkmf.log shows it is using /opt/SUNWspro12/bin/cc*

First, don't send HTML to technical mailing lists.

You can probably override the CC env when running make after running
"ruby extconf.rb" manually.   Not sure how to do that easily via
"gem install"...

There might be a more generic way to specify an alternative
compiler when installing gems.

On the other hand, it might be easier to just install libatomic_ops
(or rebuild Ruby using gcc)

If you really want to get nasty, you can also edit the rbconfig.rb
file in your ruby installation so it points to GCC...  Totally hacky,

> *$gcc -v
> Using built-in specs.
> Target: sparc-sun-solaris2.10
> Configured with: ../gcc-4.3.5/configure --prefix=/opt/swt/install/gcc-4.3.5
> --with-gmp-lib=/opt/swt/lib --with-gmp-include=/opt/swt/include
> Thread model: posix
> gcc version 4.3.5 (GCC)
> *
> * *
> *$ uname -a
> SunOS sundev1 5.10 142900-02 sun4v sparc SUNW,T5240

Anyways I can't provide support for non-Free systems.  Maybe somebody
else on the list has more knowledge in these areas.

      reply	other threads:[~2012-01-19 19:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAK0mJ0x3fZnHX5RQRV3BNjTnSjbsU-avmeEU0vMaN-8U95T7tw@mail.gmail.com>
2012-01-19 12:53 ` Rainbow gem install on solaris failed Anjana Sarkar
2012-01-19 19:37   ` Eric Wong [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:

  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=20120119193740.GA23333@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=raindrops@librelist.org \


* 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


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).