Model Name: Mac mini
Model Identifier: Macmini1,1
Processor Name: Intel Core Duo
Processor Speed: 1.66 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 2 MB
Memory: 2 GB
Bus Speed: 667 MHz
I've been reading your back numbers (what fun) and I guess the lack of
full 64-bit may be a snag. But here goes
~ $ ruby -v
ruby 1.8.7 (2008-06-20 patchlevel 22) [i686-darwin8.11.1]
~ $ file -L `which ruby`
/usr/local/bin/ruby: Mach-O universal binary with 2 architectures
/usr/local/bin/ruby (for architecture i386): Mach-O executable i386
/usr/local/bin/ruby (for architecture ppc): Mach-O executable ppc
~ $ sudo gem install johnson -v "2.0.0.pre3"
Building native extensions. This could take a while...
ERROR: Error installing johnson:
ERROR: Failed to build gem native extension.
/usr/local/bin/ruby extconf.rb
checking for jsautocfg.h in /usr/local/lib/ruby/gems/1.8/gems/
johnson-2.0.0.pre3/vendor/tracemonkey... no
checking for jsapi.h in /usr/local/lib/ruby/gems/1.8/gems/
johnson-2.0.0.pre3/vendor/tracemonkey... no
creating Makefile
make
g++ -I. -I/usr/local/lib/ruby/1.8/i686-darwin8.11.1 -I/usr/local/lib/
ruby/1.8/i686-darwin8.11.1 -I. -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE -
fno-common -O2 -arch i686 -arch ppc -fno-common -pipe -fno-common -
g -Wall -Wextra -Wcast-qual -Wwrite-strings -Wconversion -
Wmissing-noreturn -Winline -DXP_UNIX -c context.cc
In file included from context.h:4,
from context.cc:1:
tracemonkey.h:9:19: error: jsapi.h: No such file or directory
tracemonkey.h:10:20: error: jshash.h: No such file or directory
etc
That was after trying a few different versions before that ... so it
took less time to fail. The thing is, I can see the jsapi.h and the
rest. I don't want to spend an age on Johnson - this week anyway - but
it would be cool to have the full McCoy if it's possible. If not, I'll
go in another direction.
Thanks in advance. It looks a great concept.
Richard
I'm not sure why, but that command looks bogus. The '-I.' right before the '-D_XOPEN_SOURCE' is not right: it should point to the vendored tracemonkey, not '.'.
There are two differences between what you have and what I build/test against: I have a 64 bit install and I don't use the native ruby. PL22 seems pretty old. compared to current (at least what RVM installs), which is PL249. 2008-06-20 was quite awhile ago. I wonder if the ext build stuff was broken?
Would using a newer ruby (say, via rvm), be possible for you?
--
To unsubscribe, reply using "remove me" as the subject.
Some questions. On parsing I used to_sexp as I found that form easier
to inspect. Is there a better way? Is there documentation?
Is TraceMonkey the same as SpiderMonkey these days?
Is anyone doing anything serious to link Johnson to V8?
This helped solve a key integration problem for me anyhow. Thanks for
that. I'll return :)
On Apr 13, 9:14 pm, Richard Drake <rdrak...@gmail.com> wrote:
> Embarrassing, using rvm's latest 1.8.7 seems to have fixed it.
>
> Should have spotted that but thanks.
>
Yes. We're planning on switching back to just calling it all SpiderMonkey.
> Is anyone doing anything serious to link Johnson to V8?
Not that I'm aware of. As it stands, Johnson is pretty tied to the SpiderMonkey API.
> On parsing I used to_sexp as I found that form easier
> to inspect. Is there a better way? Is there documentation?
I leave that to others ...