Hi Geoffrey,
Yes, you can use trunk or the latest nightly builds. We are still working on
the Xcode4 templates to release 0.10, and it's taking some time (the new
template system is very different, and quite complex to understand). But
besides the templates, trunk is ready, so you can bundle it
On 18.03.2011, at 19:56, Geoffrey Grosenbach wrote:
> On Thu, Mar 10, 2011 at 1:34 PM, Laurent Sansonetti
> wrote:
>> Thanks for verifying the fixes. I will release trunk as 0.10 tomorrow
>> evening.
>
> Is this still the plan? Many customers are on the new MacBook and I've
> had them roll bac
On Thu, Mar 10, 2011 at 1:34 PM, Laurent Sansonetti
wrote:
> Thanks for verifying the fixes. I will release trunk as 0.10 tomorrow evening.
Is this still the plan? Many customers are on the new MacBook and I've
had them roll back to a previous version of my app so it launches.
Or, should I build
My customers with new MacBook Pro's have confirmed that the new version of my
QuickAlarm app with the new MacRuby 0.1/LLVM works!
Good job everybody!
> Yes, it was a problem in LLVM, which wasn't generating code for the proper
> architecture. I hope this was an exception and that we won't need
On Mar 10, 2011, at 1:34 PM, Laurent Sansonetti wrote:
> Thanks for verifying the fixes. I will release trunk as 0.10 tomorrow evening.
Not 0.9.1? A, why should OpenSSL get all the cool version numbering?? ;-)
___
MacRuby-devel mailing list
MacRub
Yes, it was a problem in LLVM, which wasn't generating code for the proper
architecture. I hope this was an exception and that we won't need to target new
LLVM versions each time new architectures are introduced :)
Thanks for verifying the fixes. I will release trunk as 0.10 tomorrow evening.
L
I can also confirm this now builds correctly. Thanks very much for the speedy
turnaround, Laurent.
Out of interest, do you know why the Core i7 chip in this laptop behaves
differently to the Core 2 Duo in my previous laptop? Is it perhaps just that
LLVM is failing to detect the CPU correctly, a
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
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
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
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
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
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
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
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
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
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
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
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 didn't read your email in details sorry, but did you follow the README
instructions with the specific LLVM revision etc..
- Matt
Sent from my iPhone
On Mar 8, 2011, at 16:05, Nick Ludlam wrote:
> Just following up on my own issue, would an install of XCode 4 along side my
> existing XCode
Just following up on my own issue, would an install of XCode 4 along side my
existing XCode 3 cause this sort of problem? I've got XCode 4 in a separate
directory, but I don't know how much cross linking into common paths there is.
On 6 Mar 2011, at 12:12, Nick Ludlam wrote:
> Hi all,
> I've ju
Hi all,
I've just got myself set up on one of the Sandy Bridge laptops, and I've broken
my compile environment for MacRuby, and cannot seem to get it back.
I've done the following to get llvm-2.8:
$ svn co https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_28 llvm-2.8
$ env UNIVERSAL=1 UNIVERSA
22 matches
Mail list logo
