Re: [MacRuby-devel] MacRuby build issues with LLVM
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 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 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 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 UNIVERSAL_ARCH="i386 x86_64" CC=/usr/bin/gcc >>> CXX=/usr/bin/g++ ./configure --enable-bindings=none --enable-optimized >>> --with-llvmgccdir=/tmp --prefix=/opt/llvm-macruby >>> $ sudo env UNIVERSAL=1 UNIVERSAL_ARCH="i386 x86_64" CC=/usr/bin/gcc >>> CXX=/usr/bin/g++ make -j4 >>> $ sudo env UNIVERSAL=1 UNIVERSAL_ARCH="i386 x86_64" CC=/usr/bin/gcc >>> CXX=/usr/bin/g++ make install >>> >>> This has given me a complete but separate llvm tree in /opt/llvm-macruby/. >>> Within the MacRuby git clone (HEAD), I'm doing: >>> >>> rake llvm_path=/opt/llvm-macruby/ >>> >>> to allow it to see the llvm install. I've also added /opt/llvm-macruby/bin >>> to my shell path. But the build fails with a deep llvm voodoo issue that >>> I'm not even sure how to start addressing. It's in the part of the build >>> where miniruby is used to compile rbconfig.rb, and I've separated the >>> output here: >>> >>> $ ./miniruby -I. -I./lib bin/rubyc --internal --arch x86_64 -C >>> "rbconfig.rb" -o "./rbconfig.rbo" >>> LLVM ERROR: Cannot yet select: 0x103097410: f64 = bit_convert 0x1030b6c10 >>> [ORD=391] [ID=7] >>> 0x1030b6c10: i64 = and 0x1030b6f10, 0x103087e10 [ORD=390] [ID=6] >>> 0x1030b6f10: i64,ch = CopyFromReg 0x1039104a8, 0x1030b9010 [ORD=390] [ID=5] >>>0x1039104a8: ch = EntryToken [ORD=390] [ID=0] >>>0x1030b9010: i64 = Register %reg16384 [ORD=390] [ID=1] >>> 0x103087e10: i64 = Constant<-4> [ORD=390] [ID=2] >>> >>> I get exactly the same issue when I was trying to use the llvm from the >>> Homebrew port system, and also when I install llvm into /usr/local (which >>> I'd like to avoid, as I'm trying to use Homebrew for anything in that path). >>> >>> Anybody got a suggestion as to what I can try next? >>> >>> Thanks, >>> Nick >>> >>> >>> ___ >>> MacRuby-devel mailing list >>> [email protected] >>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >> >> ___ >> MacRuby-devel mailing list >> [email protected] >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] MacRuby build issues with LLVM
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 this is the issue, it might not help either. -- Thibault Martin-Lagardette On Wednesday, March 9, 2011 at 11:41, Nick Ludlam wrote: > 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 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 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 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 UNIVERSAL_ARCH="i386 x86_64" CC=/usr/bin/gcc > > > > CXX=/usr/bin/g++ ./configure --enable-bindings=none --enable-optimized > > > > --with-llvmgccdir=/tmp --prefix=/opt/llvm-macruby > > > > $ sudo env UNIVERSAL=1 UNIVERSAL_ARCH="i386 x86_64" CC=/usr/bin/gcc > > > > CXX=/usr/bin/g++ make -j4 > > > > $ sudo env UNIVERSAL=1 UNIVERSAL_ARCH="i386 x86_64" CC=/usr/bin/gcc > > > > CXX=/usr/bin/g++ make install > > > > > > > > This has given me a complete but separate llvm tree in > > > > /opt/llvm-macruby/. Within the MacRuby git clone (HEAD), I'm doing: > > > > > > > > rake llvm_path=/opt/llvm-macruby/ > > > > > > > > to allow it to see the llvm install. I've also added > > > > /opt/llvm-macruby/bin to my shell path. But the build fails with a deep > > > > llvm voodoo issue that I'm not even sure how to start addressing. It's > > > > in the part of the build where miniruby is used to compile rbconfig.rb, > > > > and I've separated the output here: > > > > > > > > $ ./miniruby -I. -I./lib bin/rubyc --internal --arch x86_64 -C > > > > "rbconfig.rb" -o "./rbconfig.rbo" > > > > LLVM ERROR: Cannot yet select: 0x103097410: f64 = bit_convert > > > > 0x1030b6c10 [ORD=391] [ID=7] > > > > 0x1030b6c10: i64 = and 0x1030b6f10, 0x103087e10 [ORD=390] [ID=6] > > > > 0x1030b6f10: i64,ch = CopyFromReg 0x1039104a8, 0x1030b9010 [ORD=390] > > > > [ID=5] > > > > 0x1039104a8: ch = EntryToken [ORD=390] [ID=0] > > > > 0x1030b9010: i64 = Register %reg16384 [ORD=390] [ID=1] > > > > 0x103087e10: i64 = Constant<-4> [ORD=390] [ID=2] > > > > > > > > I get exactly the same issue when I was trying to use the llvm from the > > > > Homebrew port system, and also when I install llvm into /usr/local > > > > (which I'd like to avoid, as I'm trying to use Homebrew for anything in > > > > that path). > > > > > > > > Anybody got a suggestion as to what I can try next? > > > > > > > > Thanks, > > > > Nick > > > > > > > > > > > > ___ > > > > MacRuby-devel mailing list > > > > [email protected] > > > > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > > > > > ___ > > > MacRuby-devel mailing list > > > [email protected] > > > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > ___ > > MacRuby-devel mailing list > > [email protected] > > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] MacRuby build issues with LLVM
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 simple C hello world to rule out llvm bugs. Cheers, Josh On Wed, Mar 9, 2011 at 5:41 AM, Nick Ludlam wrote: > 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 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 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 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_28llvm-2.8 > >>> $ env UNIVERSAL=1 UNIVERSAL_ARCH="i386 x86_64" CC=/usr/bin/gcc > CXX=/usr/bin/g++ ./configure --enable-bindings=none --enable-optimized > --with-llvmgccdir=/tmp --prefix=/opt/llvm-macruby > >>> $ sudo env UNIVERSAL=1 UNIVERSAL_ARCH="i386 x86_64" CC=/usr/bin/gcc > CXX=/usr/bin/g++ make -j4 > >>> $ sudo env UNIVERSAL=1 UNIVERSAL_ARCH="i386 x86_64" CC=/usr/bin/gcc > CXX=/usr/bin/g++ make install > >>> > >>> This has given me a complete but separate llvm tree in > /opt/llvm-macruby/. Within the MacRuby git clone (HEAD), I'm doing: > >>> > >>> rake llvm_path=/opt/llvm-macruby/ > >>> > >>> to allow it to see the llvm install. I've also added > /opt/llvm-macruby/bin to my shell path. But the build fails with a deep llvm > voodoo issue that I'm not even sure how to start addressing. It's in the > part of the build where miniruby is used to compile rbconfig.rb, and I've > separated the output here: > >>> > >>> $ ./miniruby -I. -I./lib bin/rubyc --internal --arch x86_64 -C > "rbconfig.rb" -o "./rbconfig.rbo" > >>> LLVM ERROR: Cannot yet select: 0x103097410: f64 = bit_convert > 0x1030b6c10 [ORD=391] [ID=7] > >>> 0x1030b6c10: i64 = and 0x1030b6f10, 0x103087e10 [ORD=390] [ID=6] > >>> 0x1030b6f10: i64,ch = CopyFromReg 0x1039104a8, 0x1030b9010 [ORD=390] > [ID=5] > >>>0x1039104a8: ch = EntryToken [ORD=390] [ID=0] > >>>0x1030b9010: i64 = Register %reg16384 [ORD=390] [ID=1] > >>> 0x103087e10: i64 = Constant<-4> [ORD=390] [ID=2] > >>> > >>> I get exactly the same issue when I was trying to use the llvm from the > Homebrew port system, and also when I install llvm into /usr/local (which > I'd like to avoid, as I'm trying to use Homebrew for anything in that path). > >>> > >>> Anybody got a suggestion as to what I can try next? > >>> > >>> Thanks, > >>> Nick > >>> > >>> > >>> ___ > >>> MacRuby-devel mailing list > >>> [email protected] > >>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > >> > >> ___ > >> MacRuby-devel mailing list > >> [email protected] > >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > ___ > > MacRuby-devel mailing list > > [email protected] > > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] MacRuby build issues with LLVM
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 rack LLVM ERROR: Cannot yet select: 0x10509ba10: f64 = bit_convert 0x10508ef10 [ORD=2615] [ID=7] 0x10508ef10: i64 = and 0x105062a10, 0x10509b010 [ORD=2614] [ID=6] 0x105062a10: i64,ch = CopyFromReg 0x1039108a8, 0x105099510 [ORD=2614] [ID=5] 0x1039108a8: ch = EntryToken [ORD=2614] [ID=0] 0x105099510: i64 = Register %reg16384 [ORD=2614] [ID=1] 0x10509b010: i64 = Constant<-4> [ORD=2614] [ID=2] $ macirb LLVM ERROR: Cannot yet select: 0x104852410: f64 = bit_convert 0x104858c10 [ORD=186] [ID=7] 0x104858c10: i64 = and 0x104853c10, 0x104851910 [ORD=185] [ID=6] 0x104853c10: i64,ch = CopyFromReg 0x103b0d028, 0x104856010 [ORD=185] [ID=5] 0x103b0d028: ch = EntryToken [ORD=185] [ID=0] 0x104856010: i64 = Register %reg16384 [ORD=185] [ID=1] 0x104851910: i64 = Constant<-4> [ORD=185] [ID=2] $ macrake LLVM ERROR: Cannot yet select: 0x10506d810: f64 = bit_convert 0x105047310 [ORD=800] [ID=7] 0x105047310: i64 = and 0x105067d10, 0x105063010 [ORD=799] [ID=6] 0x105067d10: i64,ch = CopyFromReg 0x103b0cf68, 0x105043110 [ORD=799] [ID=5] 0x103b0cf68: ch = EntryToken [ORD=799] [ID=0] 0x105043110: i64 = Register %reg16384 [ORD=799] [ID=1] 0x105063010: i64 = Constant<-4> [ORD=799] [ID=2] Interestingly, the macruby interpreter runs without error. "macgem --help" and "macgem --version" also run fine (but these options produce errors with macirb or macrake). FWIW, I only have Xcode 4 DP2 installed on this machine... although I assume the MacRuby framework doesn't have any runtime dev tool dependencies? (My understanding was it could be bundled with apps and distributed to end users who don't have dev tools installed.) Scott On Wednesday, March 9, 2011 at 10:40 AM, Joshua Ballanco wrote: > 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 simple C hello world to rule out llvm bugs. > > Cheers, > > Josh > > On Wed, Mar 9, 2011 at 5:41 AM, Nick Ludlam wrote: > > 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 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 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 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 UNIVERSAL_ARCH="i386 x86_64" CC=/usr/bin/gcc > > >>> CXX=/usr/bin/g++ ./configure --enable-bindings=none --enable-optimized > > >>> --with-llvmgccdir=/tmp --prefix=/opt/llvm-macruby > > >>> $ sudo env UNIVERSAL=1 UNIVERSAL_ARCH="i386 x86_64" CC=/usr/bin/gcc > > >>> CXX=/usr/bin/g++ make -j4 > > >>> $ sudo env UNIVERSAL=1 UNIVERSAL_ARCH="i386 x86_64" CC=/usr/bin/gcc > > >>> CXX=/usr/bin/g++ make install > > >>> > > >>> This has given me a complete but separate llvm tree in > > >>> /opt/llvm-macruby/. Within the MacRuby git clone (HEAD), I'm doing: > > >>> > > >>> rake llvm_path=/opt/llvm-macruby/ > > >>> > > >>> to allow it to see the llvm install. I've also added > > >>> /opt/llvm-macruby/bin to my shell path. But the build fails with a deep > > >>> llvm voodoo issue that I'm not even sure how to start addressing. It's > > >>> in the part of the build where miniruby is used to compile rbconfig.rb, > > >>> and I've separated the output here: > > >>> > > >>> $ ./miniruby -I. -I./lib bin/rubyc --internal --arch x86_64 -C > > >>> "rbconfig.rb" -o "./rbconfig.rbo" > > >>> LLVM ERROR: Cannot yet select: 0x103097410: f64 = bit_convert > > >>> 0x1030b6c10 [ORD=391] [ID=7] > > >>> 0x1030b6c10: i64 = and 0x1030b6f10, 0x103087e10 [ORD=390] [ID=6] > > >>> 0x1030b6f10: i64,ch = CopyFromReg 0x1039104a8, 0x1030b9
Re: [MacRuby-devel] MacRuby build issues with LLVM
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 can provide copies of my app to developers that would like to try to reproduce the problem. Thanks, Richard Here is a portion of the log that he sent me. 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] LLVM ERROR: Cannot yet select: 0x101899010: f64 = bit_convert 0x10191ae10 [ORD=315] [ID=7] 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] 0x10191ae10: i64 = and 0x10191b510, 0x10189a110 [ORD=314] [ID=6] 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] 0x10191b510: i64,ch = CopyFromReg 0x103911388, 0x10191c510 [ORD=314] [ID=5] 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] 0x103911388: ch = EntryToken [ORD=314] [ID=0] 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] 0x10191c510: i64 = Register %reg16384 [ORD=314] [ID=1] 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] 0x10189a110: i64 = Constant<-4> [ORD=314] [ID=2] 3/9/11 11:35:31 AM com.apple.launchd.peruser.501[112] ([0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927]) Exited with exit code: 1 > > 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 rack > LLVM ERROR: Cannot yet select: 0x10509ba10: f64 = bit_convert 0x10508ef10 > [ORD=2615] [ID=7] > 0x10508ef10: i64 = and 0x105062a10, 0x10509b010 [ORD=2614] [ID=6] > 0x105062a10: i64,ch = CopyFromReg 0x1039108a8, 0x105099510 [ORD=2614] [ID=5] > 0x1039108a8: ch = EntryToken [ORD=2614] [ID=0] > 0x105099510: i64 = Register %reg16384 [ORD=2614] [ID=1] > 0x10509b010: i64 = Constant<-4> [ORD=2614] [ID=2] > > > $ macirb > LLVM ERROR: Cannot yet select: 0x104852410: f64 = bit_convert 0x104858c10 > [ORD=186] [ID=7] > 0x104858c10: i64 = and 0x104853c10, 0x104851910 [ORD=185] [ID=6] > 0x104853c10: i64,ch = CopyFromReg 0x103b0d028, 0x104856010 [ORD=185] [ID=5] > 0x103b0d028: ch = EntryToken [ORD=185] [ID=0] > 0x104856010: i64 = Register %reg16384 [ORD=185] [ID=1] > 0x104851910: i64 = Constant<-4> [ORD=185] [ID=2] > > > $ macrake > LLVM ERROR: Cannot yet select: 0x10506d810: f64 = bit_convert 0x105047310 > [ORD=800] [ID=7] > 0x105047310: i64 = and 0x105067d10, 0x105063010 [ORD=799] [ID=6] > 0x105067d10: i64,ch = CopyFromReg 0x103b0cf68, 0x105043110 [ORD=799] [ID=5] > 0x103b0cf68: ch = EntryToken [ORD=799] [ID=0] > 0x105043110: i64 = Register %reg16384 [ORD=799] [ID=1] > 0x105063010: i64 = Constant<-4> [ORD=799] [ID=2] > > > > Interestingly, the macruby interpreter runs without error. "macgem --help" > and "macgem --version" also run fine (but these options produce errors with > macirb or macrake). > > FWIW, I only have Xcode 4 DP2 installed on this machine... although I assume > the MacRuby framework doesn't have any runtime dev tool dependencies? (My > understanding was it could be bundled with apps and distributed to end users > who don't have dev tools installed.) > > Scott > > On Wednesday, March 9, 2011 at 10:40 AM, Joshua Ballanco wrote: >> 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 simple C hello world to rule out llvm bugs. >> >> Cheers, >> >> Josh >> >> On Wed, Mar 9, 2011 at 5:41 AM, Nick Ludlam wrote: >>> 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: > ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] MacRuby build issues with LLVM
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 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 can provide copies of my app to developers that would like to try to > reproduce the problem. > > Thanks, > > Richard > > Here is a portion of the log that he sent me. > > 3/9/11 11:35:31 AM[0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] > LLVM ERROR: Cannot yet select: 0x101899010: f64 = bit_convert 0x10191ae10 > [ORD=315] [ID=7] > 3/9/11 11:35:31 AM[0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] > 0x10191ae10: i64 = and 0x10191b510, 0x10189a110 [ORD=314] [ID=6] > 3/9/11 11:35:31 AM[0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] > 0x10191b510: i64,ch = CopyFromReg 0x103911388, 0x10191c510 [ORD=314] > [ID=5] > 3/9/11 11:35:31 AM[0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] > 0x103911388: ch = EntryToken [ORD=314] [ID=0] > 3/9/11 11:35:31 AM[0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] > 0x10191c510: i64 = Register %reg16384 [ORD=314] [ID=1] > 3/9/11 11:35:31 AM[0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] > 0x10189a110: i64 = Constant<-4> [ORD=314] [ID=2] > 3/9/11 11:35:31 AMcom.apple.launchd.peruser.501[112] > ([0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927]) Exited with exit code: 1 > >> >> 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 rack >> LLVM ERROR: Cannot yet select: 0x10509ba10: f64 = bit_convert 0x10508ef10 >> [ORD=2615] [ID=7] >> 0x10508ef10: i64 = and 0x105062a10, 0x10509b010 [ORD=2614] [ID=6] >> 0x105062a10: i64,ch = CopyFromReg 0x1039108a8, 0x105099510 [ORD=2614] [ID=5] >> 0x1039108a8: ch = EntryToken [ORD=2614] [ID=0] >> 0x105099510: i64 = Register %reg16384 [ORD=2614] [ID=1] >> 0x10509b010: i64 = Constant<-4> [ORD=2614] [ID=2] >> >> >> $ macirb >> LLVM ERROR: Cannot yet select: 0x104852410: f64 = bit_convert 0x104858c10 >> [ORD=186] [ID=7] >> 0x104858c10: i64 = and 0x104853c10, 0x104851910 [ORD=185] [ID=6] >> 0x104853c10: i64,ch = CopyFromReg 0x103b0d028, 0x104856010 [ORD=185] [ID=5] >> 0x103b0d028: ch = EntryToken [ORD=185] [ID=0] >> 0x104856010: i64 = Register %reg16384 [ORD=185] [ID=1] >> 0x104851910: i64 = Constant<-4> [ORD=185] [ID=2] >> >> >> $ macrake >> LLVM ERROR: Cannot yet select: 0x10506d810: f64 = bit_convert 0x105047310 >> [ORD=800] [ID=7] >> 0x105047310: i64 = and 0x105067d10, 0x105063010 [ORD=799] [ID=6] >> 0x105067d10: i64,ch = CopyFromReg 0x103b0cf68, 0x105043110 [ORD=799] [ID=5] >> 0x103b0cf68: ch = EntryToken [ORD=799] [ID=0] >> 0x105043110: i64 = Register %reg16384 [ORD=799] [ID=1] >> 0x105063010: i64 = Constant<-4> [ORD=799] [ID=2] >> >> >> >> Interestingly, the macruby interpreter runs without error. "macgem --help" >> and "macgem --version" also run fine (but these options produce errors with >> macirb or macrake). >> >> FWIW, I only have Xcode 4 DP2 installed on this machine... although I assume >> the MacRuby framework doesn't have any runtime dev tool dependencies? (My >> understanding was it could be bundled with apps and distributed to end users >> who don't have dev tools installed.) >> >> Scott >> >> On Wednesday, March 9, 2011 at 10:40 AM, Joshua Ballanco wrote: >>> 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 simple C hello world to rule out llvm bugs. >>> >>> Cheers, >>> >>> Josh >>> >>> On Wed, Mar 9, 2011 at 5:41 AM, Nick Ludlam wrote: 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: >> > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-
Re: [MacRuby-devel] MacRuby build issues with 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 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 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 can provide copies of my app to developers that would like to try to >> reproduce the problem. >> >> Thanks, >> >> Richard >> >> Here is a portion of the log that he sent me. >> >> 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] >> LLVM ERROR: Cannot yet select: 0x101899010: f64 = bit_convert 0x10191ae10 >> [ORD=315] [ID=7] >> 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] >> 0x10191ae10: i64 = and 0x10191b510, 0x10189a110 [ORD=314] [ID=6] >> 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] >> 0x10191b510: i64,ch = CopyFromReg 0x103911388, 0x10191c510 [ORD=314] >> [ID=5] >> 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] >> 0x103911388: ch = EntryToken [ORD=314] [ID=0] >> 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] >> 0x10191c510: i64 = Register %reg16384 [ORD=314] [ID=1] >> 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] >> 0x10189a110: i64 = Constant<-4> [ORD=314] [ID=2] >> 3/9/11 11:35:31 AM com.apple.launchd.peruser.501[112] >> ([0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927]) Exited with exit code: 1 >> >>> >>> 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 rack >>> LLVM ERROR: Cannot yet select: 0x10509ba10: f64 = bit_convert 0x10508ef10 >>> [ORD=2615] [ID=7] >>> 0x10508ef10: i64 = and 0x105062a10, 0x10509b010 [ORD=2614] [ID=6] >>> 0x105062a10: i64,ch = CopyFromReg 0x1039108a8, 0x105099510 [ORD=2614] [ID=5] >>> 0x1039108a8: ch = EntryToken [ORD=2614] [ID=0] >>> 0x105099510: i64 = Register %reg16384 [ORD=2614] [ID=1] >>> 0x10509b010: i64 = Constant<-4> [ORD=2614] [ID=2] >>> >>> >>> $ macirb >>> LLVM ERROR: Cannot yet select: 0x104852410: f64 = bit_convert 0x104858c10 >>> [ORD=186] [ID=7] >>> 0x104858c10: i64 = and 0x104853c10, 0x104851910 [ORD=185] [ID=6] >>> 0x104853c10: i64,ch = CopyFromReg 0x103b0d028, 0x104856010 [ORD=185] [ID=5] >>> 0x103b0d028: ch = EntryToken [ORD=185] [ID=0] >>> 0x104856010: i64 = Register %reg16384 [ORD=185] [ID=1] >>> 0x104851910: i64 = Constant<-4> [ORD=185] [ID=2] >>> >>> >>> $ macrake >>> LLVM ERROR: Cannot yet select: 0x10506d810: f64 = bit_convert 0x105047310 >>> [ORD=800] [ID=7] >>> 0x105047310: i64 = and 0x105067d10, 0x105063010 [ORD=799] [ID=6] >>> 0x105067d10: i64,ch = CopyFromReg 0x103b0cf68, 0x105043110 [ORD=799] [ID=5] >>> 0x103b0cf68: ch = EntryToken [ORD=799] [ID=0] >>> 0x105043110: i64 = Register %reg16384 [ORD=799] [ID=1] >>> 0x105063010: i64 = Constant<-4> [ORD=799] [ID=2] >>> >>> >>> >>> Interestingly, the macruby interpreter runs without error. "macgem --help" >>> and "macgem --version" also run fine (but these options produce errors with >>> macirb or macrake). >>> >>> FWIW, I only have Xcode 4 DP2 installed on this machine... although I >>> assume the MacRuby framework doesn't have any runtime dev tool >>> dependencies? (My understanding was it could be bundled with apps and >>> distributed to end users who don't have dev tools installed.) >>> >>> Scott >>> >>> On Wednesday, March 9, 2011 at 10:40 AM, Joshua Ballanco wrote: 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 simple C hello world to rule out llvm bugs. Cheers, Josh On Wed, Mar 9, 2011 at 5:41 AM, Nick Ludlam wrote: > 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: >>> >> ___ >>
Re: [MacRuby-devel] MacRuby build issues with LLVM
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 supports the new hardware and that it doesn't introduce API breakage. 2) Re-build and install MacRuby trunk after doing a rake clean. Laurent On Mar 9, 2011, at 1:08 PM, Laurent Sansonetti wrote: > 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 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 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 can provide copies of my app to developers that would like to try to >>> reproduce the problem. >>> >>> Thanks, >>> >>> Richard >>> >>> Here is a portion of the log that he sent me. >>> >>> 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] >>> LLVM ERROR: Cannot yet select: 0x101899010: f64 = bit_convert 0x10191ae10 >>> [ORD=315] [ID=7] >>> 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] >>> 0x10191ae10: i64 = and 0x10191b510, 0x10189a110 [ORD=314] [ID=6] >>> 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] >>> 0x10191b510: i64,ch = CopyFromReg 0x103911388, 0x10191c510 [ORD=314] >>> [ID=5] >>> 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] >>> 0x103911388: ch = EntryToken [ORD=314] [ID=0] >>> 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] >>> 0x10191c510: i64 = Register %reg16384 [ORD=314] [ID=1] >>> 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] >>> 0x10189a110: i64 = Constant<-4> [ORD=314] [ID=2] >>> 3/9/11 11:35:31 AM com.apple.launchd.peruser.501[112] >>> ([0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927]) Exited with exit code: >>> 1 >>> 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 rack LLVM ERROR: Cannot yet select: 0x10509ba10: f64 = bit_convert 0x10508ef10 [ORD=2615] [ID=7] 0x10508ef10: i64 = and 0x105062a10, 0x10509b010 [ORD=2614] [ID=6] 0x105062a10: i64,ch = CopyFromReg 0x1039108a8, 0x105099510 [ORD=2614] [ID=5] 0x1039108a8: ch = EntryToken [ORD=2614] [ID=0] 0x105099510: i64 = Register %reg16384 [ORD=2614] [ID=1] 0x10509b010: i64 = Constant<-4> [ORD=2614] [ID=2] $ macirb LLVM ERROR: Cannot yet select: 0x104852410: f64 = bit_convert 0x104858c10 [ORD=186] [ID=7] 0x104858c10: i64 = and 0x104853c10, 0x104851910 [ORD=185] [ID=6] 0x104853c10: i64,ch = CopyFromReg 0x103b0d028, 0x104856010 [ORD=185] [ID=5] 0x103b0d028: ch = EntryToken [ORD=185] [ID=0] 0x104856010: i64 = Register %reg16384 [ORD=185] [ID=1] 0x104851910: i64 = Constant<-4> [ORD=185] [ID=2] $ macrake LLVM ERROR: Cannot yet select: 0x10506d810: f64 = bit_convert 0x105047310 [ORD=800] [ID=7] 0x105047310: i64 = and 0x105067d10, 0x105063010 [ORD=799] [ID=6] 0x105067d10: i64,ch = CopyFromReg 0x103b0cf68, 0x105043110 [ORD=799] [ID=5] 0x103b0cf68: ch = EntryToken [ORD=799] [ID=0] 0x105043110: i64 = Register %reg16384 [ORD=799] [ID=1] 0x105063010: i64 = Constant<-4> [ORD=799] [ID=2] Interestingly, the macruby interpreter runs without error. "macgem --help" and "macgem --version" also run fine (but these options produce errors with macirb or macrake). FWIW, I only have Xcode 4 DP2 installed on this machine... although I assume the MacRuby framework doesn't have any runtime dev tool dependencies? (My understanding was it could be bundled with apps and distributed to end users who don't have dev tools installed.) Scott On Wednesday, March 9, 2011 at 10:40 AM, Joshua Ballanco wrote: > 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 ins
Re: [MacRuby-devel] MacRuby build issues with 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 -pipe -fno-common -fexceptions -fblocks -g -O3 -Wall -Wno-deprecated-declarations -Werror -arch x86_64 -I./icu-1060 -c encoding.c -o .objs/encoding.o /usr/bin/g++-4.2 -I. -I./include -fblocks -g -Wall -Wno-deprecated-declarations -Werror -arch x86_64 -I/opt/llvm-macruby/include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -O3 -fno-rtti -fno-common -Woverloaded-virtual -I./icu-1060 -c main.cpp -o .objs/main.o In file included from vm.h:593, from main.cpp:17: compiler.h:82: error: ISO C++ forbids declaration of ‘DIFactory’ with no type compiler.h:82: error: expected ‘;’ before ‘*’ token rake aborted! Command failed with status (1): [/usr/bin/g++-4.2 -I. -I./include -fblocks ...] (See full trace by running task with --trace) On 9 Mar 2011, at 21:34, Laurent Sansonetti wrote: > 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 supports the new hardware and that > it doesn't introduce API breakage. > 2) Re-build and install MacRuby trunk after doing a rake clean. > > Laurent > > On Mar 9, 2011, at 1:08 PM, Laurent Sansonetti wrote: > >> 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 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 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 can provide copies of my app to developers that would like to try to reproduce the problem. Thanks, Richard Here is a portion of the log that he sent me. 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] LLVM ERROR: Cannot yet select: 0x101899010: f64 = bit_convert 0x10191ae10 [ORD=315] [ID=7] 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] 0x10191ae10: i64 = and 0x10191b510, 0x10189a110 [ORD=314] [ID=6] 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] 0x10191b510: i64,ch = CopyFromReg 0x103911388, 0x10191c510 [ORD=314] [ID=5] 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] 0x103911388: ch = EntryToken [ORD=314] [ID=0] 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] 0x10191c510: i64 = Register %reg16384 [ORD=314] [ID=1] 3/9/11 11:35:31 AM [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] 0x10189a110: i64 = Constant<-4> [ORD=314] [ID=2] 3/9/11 11:35:31 AM com.apple.launchd.peruser.501[112] ([0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927]) Exited with exit code: 1 > > 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 rack > LLVM ERROR: Cannot yet select: 0x10509ba10: f64 = bit_convert 0x10508ef10 > [ORD=2615] [ID=7] > 0x10508ef10: i64 = and 0x105062a10, 0x10509b010 [ORD=2614] [ID=6] > 0x105062a10: i64,ch = CopyFromReg 0x1039108a8, 0x105099510 [ORD=2614] > [ID=5] > 0x1039108a8: ch = EntryToken [ORD=2614] [ID=0] > 0x105099510: i64 = Register %reg16384 [ORD=2614] [ID=1] > 0x10509b010: i64 = Constant<-4> [ORD=2614] [ID=2] > > > $ macirb > LLVM ERROR: Cannot yet select: 0x104852410: f64 = bit_convert 0x104858c10 > [ORD=186] [ID=7] > 0x104858c10: i64 = and 0x104853c10, 0x104851910 [ORD=185] [ID=6] > 0x104853c10: i64,ch = CopyFromReg 0x103b0d028, 0x104856010 [ORD=185] > [ID=5] > 0x103b0d028: ch = EntryToken [ORD=185] [ID=0] > 0x104856010: i64 = Register %reg16384 [ORD=185] [ID=1] > 0x104851910: i64 = Constant<-4> [ORD=185] [ID=2] > > > $
Re: [MacRuby-devel] MacRuby build issues with LLVM
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 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 -pipe -fno-common -fexceptions > -fblocks -g -O3 -Wall -Wno-deprecated-declarations -Werror -arch x86_64 > -I./icu-1060 -c encoding.c -o .objs/encoding.o > /usr/bin/g++-4.2 -I. -I./include -fblocks -g -Wall > -Wno-deprecated-declarations -Werror -arch x86_64 -I/opt/llvm-macruby/include > -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -O3 > -fno-rtti -fno-common -Woverloaded-virtual -I./icu-1060 -c main.cpp -o > .objs/main.o > In file included from vm.h:593, > from main.cpp:17: > compiler.h:82: error: ISO C++ forbids declaration of ‘DIFactory’ with no type > compiler.h:82: error: expected ‘;’ before ‘*’ token > rake aborted! > Command failed with status (1): [/usr/bin/g++-4.2 -I. -I./include -fblocks > ...] > > (See full trace by running task with --trace) > > > > > On 9 Mar 2011, at 21:34, Laurent Sansonetti wrote: > >> 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 supports the new hardware and that >> it doesn't introduce API breakage. >> 2) Re-build and install MacRuby trunk after doing a rake clean. >> >> Laurent >> >> On Mar 9, 2011, at 1:08 PM, Laurent Sansonetti wrote: >> >>> 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 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 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 can provide copies of my app to developers that would like to try to > reproduce the problem. > > Thanks, > > Richard > > Here is a portion of the log that he sent me. > > 3/9/11 11:35:31 AM > [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] LLVM ERROR: > Cannot yet select: 0x101899010: f64 = bit_convert 0x10191ae10 [ORD=315] > [ID=7] > 3/9/11 11:35:31 AM > [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927]0x10191ae10: > i64 = and 0x10191b510, 0x10189a110 [ORD=314] [ID=6] > 3/9/11 11:35:31 AM > [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] 0x10191b510: > i64,ch = CopyFromReg 0x103911388, 0x10191c510 [ORD=314] [ID=5] > 3/9/11 11:35:31 AM > [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] > 0x103911388: ch = EntryToken [ORD=314] [ID=0] > 3/9/11 11:35:31 AM > [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] > 0x10191c510: i64 = Register %reg16384 [ORD=314] [ID=1] > 3/9/11 11:35:31 AM > [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] 0x10189a110: > i64 = Constant<-4> [ORD=314] [ID=2] > 3/9/11 11:35:31 AMcom.apple.launchd.peruser.501[112] > ([0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927]) Exited with exit > code: 1 > >> >> 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 rack >> LLVM ERROR: Cannot yet select: 0x10509ba10: f64 = bit_convert >> 0x10508ef10 [ORD=2615] [ID=7] >> 0x10508ef10: i64 = and 0x105062a10, 0x10509b010 [ORD=2614] [ID=6] >> 0x105062a10: i64,ch = CopyFromReg 0x1039108a8, 0x105099510 [ORD=2614] >> [ID=5] >> 0x1039108a8: ch = EntryToken [ORD=2614] [ID=0] >> 0x105099510: i64 = Register %reg16384 [ORD=2614] [ID=1] >> 0x10509b010: i64 = Constant<-4> [ORD=2614] [ID=2] >> >> >> $
Re: [MacRuby-devel] MacRuby build issues with LLVM
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 fixes the problem, we might need to roll out a MacRuby release with this new LLVM soon, as I suspect the problem will hit many people. Laurent On Mar 9, 2011, at 2:10 PM, Laurent Sansonetti wrote: > 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 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 -pipe -fno-common -fexceptions >> -fblocks -g -O3 -Wall -Wno-deprecated-declarations -Werror -arch x86_64 >> -I./icu-1060 -c encoding.c -o .objs/encoding.o >> /usr/bin/g++-4.2 -I. -I./include -fblocks -g -Wall >> -Wno-deprecated-declarations -Werror -arch x86_64 >> -I/opt/llvm-macruby/include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS >> -D__STDC_CONSTANT_MACROS -O3 -fno-rtti -fno-common -Woverloaded-virtual >> -I./icu-1060 -c main.cpp -o .objs/main.o >> In file included from vm.h:593, >>from main.cpp:17: >> compiler.h:82: error: ISO C++ forbids declaration of ‘DIFactory’ with no type >> compiler.h:82: error: expected ‘;’ before ‘*’ token >> rake aborted! >> Command failed with status (1): [/usr/bin/g++-4.2 -I. -I./include -fblocks >> ...] >> >> (See full trace by running task with --trace) >> >> >> >> >> On 9 Mar 2011, at 21:34, Laurent Sansonetti wrote: >> >>> 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 supports the new hardware and that it doesn't >>> introduce API breakage. >>> 2) Re-build and install MacRuby trunk after doing a rake clean. >>> >>> Laurent >>> >>> On Mar 9, 2011, at 1:08 PM, Laurent Sansonetti wrote: >>> 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 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 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 can provide copies of my app to developers that would like to try to >> reproduce the problem. >> >> Thanks, >> >> Richard >> >> Here is a portion of the log that he sent me. >> >> 3/9/11 11:35:31 AM >> [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] LLVM ERROR: >> Cannot yet select: 0x101899010: f64 = bit_convert 0x10191ae10 [ORD=315] >> [ID=7] >> 3/9/11 11:35:31 AM >> [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927]0x10191ae10: >> i64 = and 0x10191b510, 0x10189a110 [ORD=314] [ID=6] >> 3/9/11 11:35:31 AM >> [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] 0x10191b510: >> i64,ch = CopyFromReg 0x103911388, 0x10191c510 [ORD=314] [ID=5] >> 3/9/11 11:35:31 AM >> [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] >> 0x103911388: ch = EntryToken [ORD=314] [ID=0] >> 3/9/11 11:35:31 AM >> [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] >> 0x10191c510: i64 = Register %reg16384 [ORD=314] [ID=1] >> 3/9/11 11:35:31 AM >> [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] 0x10189a110: >> i64 = Constant<-4> [ORD=314] [ID=2] >> 3/9/11 11:35:31 AM com.apple.launchd.peruser.501[112] >> ([0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927]) Exited with exit >> code: 1 >> >>> >>> 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
Re: [MacRuby-devel] MacRuby build issues with LLVM
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 Sansonetti wrote: > 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 fixes the problem, we might need to roll out a MacRuby release with > this new LLVM soon, as I suspect the problem will hit many people. > > Laurent > > On Mar 9, 2011, at 2:10 PM, Laurent Sansonetti wrote: > >> 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 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 -pipe -fno-common -fexceptions >>> -fblocks -g -O3 -Wall -Wno-deprecated-declarations -Werror -arch x86_64 >>> -I./icu-1060 -c encoding.c -o .objs/encoding.o >>> /usr/bin/g++-4.2 -I. -I./include -fblocks -g -Wall >>> -Wno-deprecated-declarations -Werror -arch x86_64 >>> -I/opt/llvm-macruby/include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS >>> -D__STDC_CONSTANT_MACROS -O3 -fno-rtti -fno-common -Woverloaded-virtual >>> -I./icu-1060 -c main.cpp -o .objs/main.o >>> In file included from vm.h:593, >>> from main.cpp:17: >>> compiler.h:82: error: ISO C++ forbids declaration of ‘DIFactory’ with no >>> type >>> compiler.h:82: error: expected ‘;’ before ‘*’ token >>> rake aborted! >>> Command failed with status (1): [/usr/bin/g++-4.2 -I. -I./include -fblocks >>> ...] >>> >>> (See full trace by running task with --trace) >>> >>> >>> >>> >>> On 9 Mar 2011, at 21:34, Laurent Sansonetti wrote: >>> 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 supports the new hardware and that it doesn't introduce API breakage. 2) Re-build and install MacRuby trunk after doing a rake clean. Laurent On Mar 9, 2011, at 1:08 PM, Laurent Sansonetti wrote: > 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 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 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 can provide copies of my app to developers that would like to try to >>> reproduce the problem. >>> >>> Thanks, >>> >>> Richard >>> >>> Here is a portion of the log that he sent me. >>> >>> 3/9/11 11:35:31 AM >>> [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] LLVM ERROR: >>> Cannot yet select: 0x101899010: f64 = bit_convert 0x10191ae10 [ORD=315] >>> [ID=7] >>> 3/9/11 11:35:31 AM >>> [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927]0x10191ae10: >>> i64 = and 0x10191b510, 0x10189a110 [ORD=314] [ID=6] >>> 3/9/11 11:35:31 AM >>> [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] >>> 0x10191b510: i64,ch = CopyFromReg 0x103911388, 0x10191c510 [ORD=314] >>> [ID=5] >>> 3/9/11 11:35:31 AM >>> [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] >>> 0x103911388: ch = EntryToken [ORD=314] [ID=0] >>> 3/9/11 11:35:31 AM >>> [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] >>> 0x10191c510: i64 = Register %reg16384 [ORD=314] [ID=1] >>> 3/9/11 11:35:31 AM >>> [0x0-0xe20e2].com.rsepulveda.quickalarmtrial[2927] >>>
Re: [MacRuby-devel] Hey Apple, please be nice and share
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 have to maintain it for a certain amount of time, >> and since MacRuby hasn't hit the 1.0 milestone yet, they might not want to >> do it right now? >> >> Of course, this is just a guess :-) >> >> -- >> Thibault Martin-Lagardette >> > > I think the same as you. > I don't think MacRuby is mature enough to become a public framework yet. > It is great for developing Cocoa applications, but as a Ruby 1.9 > implementation I think it still has some way to go. Apple builds in other public source frameworks and libraries that they don't suggest you use as well. For example ICU is "built in" but Apple doesn't give you the headers and suggests that you build the library yourself, rather than link to their copy of the library, if you want to include it in your app. The reason they usually do that is because public source frameworks, like MacRuby, move on after the OS release. If their copy of the framework was public they would have to ensure that whatever apps they've created that use it track the public releases. By making the framework private, they ensure that they have the version that they've qualified their software against. I imagine their thoughts about MacRuby go along the same lines. Scott ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
