I think the best solution would be if RubyGems would apply the same
program prefix or suffix to the executables it installs. So in the
case of MacRuby, the executable would be: /usr/bin/macspec.
I haven't had the time to look at RubyGems yet though, if anyone wants
to take a stab at fixing
That would probably be the best solution in the interim.
I personally install all of my MacRuby gems in ~/.gem/macruby/1.9.0
(which is the default directory if you don't run macgem under sudo).
This way /usr/bin is not altered and when I want to run a MacRuby gem
helper I simply append ~/.g
#419: MacRuby build fails due to incompatible LLVM version?
+---
Reporter: manf...@… |Owner: lsansone...@…
Type: defect | Status: closed
Priority: major
Hi ALL, it's not too much of an issue if one is using the Ruby Version
Manager (RVM) because it creates separate executable and gem directories for
each Ruby implementation. I haven't used MacRuby under RVM but it seems to
do an excellent job of adding the appropriate executables to the path based
Hey Conrad,
I agree that you don't notice the issue if you use RVM. But the fact
remains that the issue still exists…
So as an interim solution you can indeed use RVM or, like Laurent
does, use a separate gem home, but on the long run, imo, RubyGems
should be enhanced to take care of this
Hi Eloy, I have spent a bit of time with it. Here's what I did to get
things going:
1) sudo gem install rvm
2) add the following to your .profile after the last 'export PATH='
setting:
if [ -s ~/.rvm/scripts/rvm ] ; then source ~/.rvm/scripts/rvm ; fi
Note: I didn't like running
Hey Conrad,
Hi Eloy, I have spent a bit of time with it. Here's what I did to
get things going:
1) sudo gem install rvm
2) add the following to your .profile after the last 'export PATH='
setting:
if [ -s ~/.rvm/scripts/rvm ] ; then source ~/.rvm/scripts/
rvm ; fi
Note:
On Mon, Nov 2, 2009 at 2:46 AM, Eloy Duran wrote:
> Hey Conrad,
>
> Hi Eloy, I have spent a bit of time with it. Here's what I did to get
> things going:
>
> 1) sudo gem install rvm
>
> 2) add the following to your .profile after the last 'export PATH='
> setting:
>
> if [ -s ~/.rvm/scri
#420: GCD serial dispatch queues and groups that contain serial queues do not
take surrounding scope reliably within loops/enumerators
---+
Reporter: johnmacs...@… | Owner: lsansone...@…
Type: de
#404: Segfault with ObjectSpace#each_object
---+
Reporter: keith.gautre...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: blocker
#404: Segfault with ObjectSpace#each_object
---+
Reporter: keith.gautre...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: blocker
Hey,
On Mon, Nov 2, 2009 at 12:06 AM, Eloy Duran wrote:
> I think the best solution would be if RubyGems would apply the same program
> prefix or suffix to the executables it installs. So in the case of MacRuby,
> the executable would be: /usr/bin/macspec.
> I haven't had the time to look at Ruby
Just FYI, I found one of the major issue with macruby + rspec, the problem
being that rspec relies on Kernel.caller and MacRuby's version isn't fully
compatible with C Ruby's.
Anyone knows of rspec matchers for bacon?
- Matt
On Mon, Nov 2, 2009 at 11:37 AM, John Barnette wrote:
> Hey,
>
> On Mo
#416: DRB does not work with MacRuby 5.0
--+-
Reporter: g...@… |Owner: lsansone...@…
Type: defect| Status: closed
Priority: blocker |Milesto
#396: open method from open-uri not working in macruby 0.5
---+
Reporter: dml...@… |Owner: lsansone...@…
Type: defect | Status: closed
Priority: minor
#286: YAML unable to load NSString
-+--
Reporter: ndnich...@… |Owner: lsansone...@…
Type: defect | Status: closed
Priority: minor|Miles
#187: YAML.load and non-native classes.
-+--
Reporter: eloy.de.en...@… |Owner: lsansone...@…
Type: defect | Status: closed
Priority: blocker
#108: Exception parsing XML file using REXML
--+-
Reporter: jon.lip...@… |Owner: lsansone...@…
Type: defect| Status: closed
Priority: blocker
#303: Method :open from 'open-uri' isn't working yet (multibyte problem)
+---
Reporter: wi...@… | Owner: lsansone...@…
Type: defect | Status: new
Priority: major
I've just discovered that there is an interaction between the LLVM
build process and OCaml - if OCaml is installed then LLVM 82747 will
try and build OCaml bindings, which for me at least stops the LLVM
build.
The trick is to configure LLVM with:
./configure --enable-bindings=none
Given
#199: Calling super from #respond_to? causes SystemStackError
-+--
Reporter: eloy.de.en...@… |Owner: lsansone...@…
Type: defect | Status: closed
Priorit
#303: Method :open from 'open-uri' isn't working yet (multibyte problem)
-+--
Reporter: wi...@… |Owner: lsansone...@…
Type: defect | Status: closed
Priority: m
Thank you for the suggestion, I updated the README.rdoc file in r2948.
Laurent
On Nov 2, 2009, at 7:54 PM, Antony Blakey wrote:
I've just discovered that there is an interaction between the LLVM
build process and OCaml - if OCaml is installed then LLVM 82747 will
try and build OCaml binding
#254: Let void-returning ObjC calls return the receiver.
+---
Reporter: mik...@…|Owner: lsansone...@…
Type: enhancement | Status: closed
Priority: minor
24 matches
Mail list logo
