Yes, I've double checked that I'm running 2.8 RELEASE, and it's still bailing
out with that cryptic message. The only other thing I can think of is to remove
XCode 4 and reinstall the current XCode3 release.
On 9 Mar 2011, at 03:37, Matt Aimonetti wrote:
> I didn't read your email in details so
I'm not sure re-installing Xcode 3 would fix the problem though. You can try —
but I have Xcode 4 installed and it's working perfectly well.
Do you already have a version of LLVM installed in /usr/local ? If not, why did
you change the path to /opt/llvm-macruby then? Even though I don't think th
Nick,
I'm currently using Homebrew's llvm with MacRuby. Try passing the
"--universal" switch when you install llvm (i.e. "brew install llvm
--universal"). You also might try building and installing clang at the same
time (i.e. "brew install llvm --universal --clang") and see if clang can
compile a
Nick and group,
I'm seeing similar errors with the newest MacBook Pro -- after simply
downloading the 1.9 binary and running macgem, macirb, or macrake. In other
words, I'm not compiling from source, just trying to use the latest binary
distribution on a core i7 laptop.
$ sudo macgem install
I have a customer that is also having this same problem with my MacRuby Mac App
Store application running on his new MacBook Pro. I don't have
access to this type of Mac so I haven't been able to reproduce this problem.
He has tried MacRuby 0.8 and 0.9 versions of my app with the same results.
I
Yes, this looks like it's exactly the problem I'm having, from the look of the
log, so perhaps it's a Sandy Bridge / Core i5/7 issue. Curious!
On 9 Mar 2011, at 19:56, Richard Sepulveda wrote:
> I have a customer that is also having this same problem with my MacRuby Mac
> App Store application
Sorry the late reply. It's probably because this version of LLVM that we use
cannot target the new CPU yet. I will investigate :)
Laurent
On Mar 9, 2011, at 12:10 PM, Nick Ludlam wrote:
> Yes, this looks like it's exactly the problem I'm having, from the look of
> the log, so perhaps it's a Sa
It looks like it might take a while until I get my hands on a new MBP, so could
one try the following?
1) Grab a copy of https://llvm.org/svn/llvm-project/llvm/branches/release_29
using svn, then build it using the same instructions in README.rdoc. I am just
hoping that this new version of LLVM
Ok, well it's not failing in the same way, but it's still failing:
/usr/bin/gcc-4.2 -std=c99 -I. -I./include -pipe -fno-common -fexceptions
-fblocks -g -O3 -Wall -Wno-deprecated-declarations -Werror -arch x86_64
-I./icu-1060 -c ucnv.c -o .objs/ucnv.o
/usr/bin/gcc-4.2 -std=c99 -I. -I./include -pi
Okay, API breakage, but I can reproduce that on my machine :) I will hack on it
later today and post a message here once it's supposed to compile, this way you
can continue testing.
Laurent
On Mar 9, 2011, at 2:03 PM, Nick Ludlam wrote:
> Ok, well it's not failing in the same way, but it's sti
Okay, I committed support for LLVM 2.9 as of r5269 and verified that no
regression is introduced (the spec suite runs fine).
Please update your repository, do a rake clean, then build with the
CFLAGS="-D__SUPPORT_LLVM_29__" option. Example: $ rake
CFLAGS="-D__SUPPORT_LLVM_29__" jobs=8
If this
I got confirmation that trunk as of r5271 should work. Because of the severity
of this problem, and the recent changes in macruby_deploy regarding App Store
submissions, I think we should release 0.10 as soon as possible now. I will
work on it.
Laurent
On Mar 9, 2011, at 4:09 PM, Laurent Sans
On Mar 7, 2011, at 7:56 PM, Rob Gleeson wrote:
>
> On 7 Mar 2011, at 22:59, Thibault Martin-Lagardette wrote:
>
>> Even though I totally would rather see MacRuby as a public framework just
>> like everyone else here, isn't the reason because once it's in the Public
>> frameworks, Apple would
13 matches
Mail list logo
