Laurent Sansonetti wrote:
On Nov 24, 2008, at 10:57 PM, Patrick Bennett wrote:
I would be using the stable branch but it seems like everything
assumes the development branch is being used (ie hotconsole).
Speaking of hotconsole - I've never been able to get it to build.
With the latest MacRub
On Nov 24, 2008, at 10:57 PM, Patrick Bennett wrote:
I would be using the stable branch but it seems like everything
assumes the development branch is being used (ie hotconsole).
Speaking of hotconsole - I've never been able to get it to build.
With the latest MacRuby (rev 756) [which now bu
I would be using the stable branch but it seems like everything
assumes the development branch is being used (ie hotconsole).
Speaking of hotconsole - I've never been able to get it to build.
With the latest MacRuby (rev 756) [which now builds] I get the
following when running macrake with t
Building doing "rake" then "sudo rake install" should work fine.
Sometimes a bug is introduced in miniruby which results in empty
Makefiles in extensions.
The error in irb you got was due to a bug that I fixed yesterday.
It's the problem you get when using the development branch, it's not
Weird, I deleted the empty makefile in ext/json/ext/parser and it
seemed to go from there (although now with the macruby I built and
installed things complain about ot finding stringio ?).
I also noticed rake clean doesn't clean up the generated Makefiles.
So, anyway, it builds now, but the ge
On Nov 24, 2008, at 4:38 PM, Patrick Bennett wrote:
No one? I check out a clean copy of macruby, it fails to build
(just running rake like it says), and NO ONE replies? :(
I did have a similar problem. I did things similarly - installed
first using the 0.3 binary, and then built from th
Latest gen MBP 4GB ram:
Darwin PMBMacOSX.local 9.5.1 Darwin Kernel Version 9.5.1: Fri Sep 19
16:19:24 PDT 2008; root:xnu-1228.8.30~1/RELEASE_I386 i386
ext/json/ext/parser/Makefile is 0-bytes
On Nov 24, 2008, at 8:06 PM, Laurent Sansonetti wrote:
Could you provide us more details about your en
Could you provide us more details about your environment (OS version +
processor architecture)?
Also, could you paste the content of ext/json/ext/parser/Makefile?
Laurent
On Nov 24, 2008, at 4:38 PM, Patrick Bennett wrote:
No one? I check out a clean copy of macruby, it fails to build
(ju
Patrick,
I don't have a solution, but my experience is that I was also unable
to build trunk sometime last week on my MBP. It failed during building
the extensions, so i ran the rake task to build the extensions, and it
managed to succeed.
A few days later I built from trunk (same revisio
No one? I check out a clean copy of macruby, it fails to build (just
running rake like it says), and NO ONE replies? :(
On Nov 22, 2008, at 10:20 AM, Patrick Bennett wrote:
I'm at revision 749 of the trunk and can't seem to build the trunk
(it's done this for several revisions).
It seems
I'm at revision 749 of the trunk and can't seem to build the trunk
(it's done this for several revisions).
It seems like I'm alone here but I've done nothing but fetch the
source and tried to build it. The only thing I can think of that
'might' be an issue is that before I ever downloaded th
not sure why I did it like that, I read it somewhere and then I was lazy and
didn't bother looking further :(
-Matt
On Wed, Nov 12, 2008 at 4:10 AM, Markus Prinz <[EMAIL PROTECTED]
> wrote:
>
> On 12.11.2008, at 07:26, Matt Aimonetti wrote:
>
> yay! I finally got it to build. Turns out that I s
On 12.11.2008, at 07:26, Matt Aimonetti wrote:
yay! I finally got it to build. Turns out that I still had the old
miniruby
which wasn't built properly. After cleaning up everything, restored
MacOsX
ruby and re tried, everything works fine :)
By the way, was there any reason why you remove
yay! I finally got it to build. Turns out that I still had the old miniruby
which wasn't built properly. After cleaning up everything, restored MacOsX
ruby and re tried, everything works fine :)
Time to have fun and learn Cocoa via ruby.
Thanks,
-Matt
On Tue, Nov 11, 2008 at 8:06 PM, Matt Aimon
The problem is that I can't build MacRuby itself :(
$ rake in the repo fails :(
-Matt
On Tue, Nov 11, 2008 at 7:50 PM, Jordan K. Hubbard <[EMAIL PROTECTED]> wrote:
> Erm. I must have missed something. Are you saying that rake build and
> rake install don't work for you either? I assumed y
Erm. I must have missed something. Are you saying that rake build
and rake install don't work for you either? I assumed you'd already
used those two commands to bootstrap yourself and then would use
macrake to do more esoteric stuff. You'll need macrake, for example,
to build the HotCoc
to use macrake I would need to be able to build MacRuby first ;)
-Matt
On Tue, Nov 11, 2008 at 7:11 PM, Jordan K. Hubbard <[EMAIL PROTECTED]> wrote:
>
> On Nov 11, 2008, at 1:28 PM, Matt Aimonetti wrote:
>
> booh I re added Ruby and Gem (I just had renamed them ruby.orig and
>> gem.orig) but I
On Nov 11, 2008, at 1:28 PM, Matt Aimonetti wrote:
booh I re added Ruby and Gem (I just had renamed them ruby.orig and
gem.orig) but I still can't build:
$ rake --trace
macrake
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
ht
booh I re added Ruby and Gem (I just had renamed them ruby.orig and
gem.orig) but I still can't build:
$ rake --trace
(in /Users/mattetti/src/MacRuby/trunk)
** Invoke default (first_time)
** Invoke all (first_time)
** Invoke macruby (first_time)
** Invoke macruby:build (first_time)
** Invoke macru
So I didn't really "remove" Ruby, I simply renamed the files/folders to
avoid conflict between macports Ruby and OSX Ruby. I believe this is
something very common and it might create issues for other people.
However, even after I changed the rake file, the build failed because of
miniruby:
https:/
Ouch, if you removed /usr/bin/ruby then yes it's going to fail :)
Either you manually edit the Rakefile and change the paths, or you re-
install your OS. Removing the default Ruby install is a very very bad
idea (as removing anything bundled with the OS), because some OS
functionality relies
Didn't work.
I believe the problem is that I removed MacOSX default Ruby install in favor
of the macports version (maybe not a wise move) and the rake task seems to
have a hard coded path to /usr/bin/ruby
Command failed with status (127): [/usr/bin/ruby tool/compile_prelude.rb
prel...]
Line 269
Rich and I got this problem a while ago, I was unable to find the root
of it and removing /Library/Frameworks/MacRuby.framework fixed it.
The problem was miniruby crashing when loading the strscan.bundle C
extension inside the dyld. I initially thought that it was a local
issue when copying
I just did:
$ /opt/local/bin/ruby tool/compile_prelude.rb prelude.rb miniprelude.c.new
and nothing happens, nothing in the console either. I have Ruby 1.8.6
installed by macports, could that cause a problem?
-Matt
On Sun, Nov 9, 2008 at 2:54 PM, Laurent Sansonetti <[EMAIL PROTECTED]>wrote:
>
Mmh I suspect it is the broken strscan.bundle problem again.
What does happen if you type the following from the source directory?
$ /usr/bin/ruby tool/compile_prelude.rb prelude.rb miniprelude.c.new
If you get a segmentation fault, could you attach the crash log from
Console.app?
Thanks,
L
[EMAIL PROTECTED] trunk]$ rake --trace
(in /Users/mattetti/src/MacRuby/trunk)
** Invoke default (first_time)
** Invoke all (first_time)
** Invoke macruby (first_time)
** Invoke macruby:build (first_time)
** Invoke macruby:dylib (first_time)
** Invoke rbconfig (first_time)
** Invoke miniruby (first_
26 matches
Mail list logo
