Re: [rvm-research] Running RVM fails in Mavericks

Hi,

I downloaded the latest stable 3.1.3 and compiled it using Apple's
clang on OS X 10.9.2:

jikesrvm-3.1.3 $ gcc -v
Configured with:
--prefix=/Applications/Xcode.app/Contents/Developer/usr
--with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 5.1 (clang-503.0.38) (based on LLVM 3.4svn)
Target: x86_64-apple-darwin13.1.0
Thread model: posix

Using "ant -Dhost.name=x86_64-osx -Dconfig.name=development".

I had to modify build.xml to remove -fkeep-static-consts from the
jburg build as this flag is not supported by clang.

The resulting JikesRVM ran without problems on a range of Dacapo 2006
benchmarks.  Thus I would suggest that Erik might want to try clang.

Kind regards,

Carl


2014-04-10 17:00 GMT+01:00 Erik Brangs <[email protected]>:
> Hi,
>
> On 10.04.2014 16:17, Erik Österlund wrote:
>> In my ant build file we find: [...]
>>
>> host.name=x86_64-osx
>> target.name=x86_64-osx
>> config.name=development
> Looks ok so far. In particular, it seems that you're building with GNU Classpath as the class library. (The error that you posted earlier looks similar to RVM-925 which occurs when building with the Apache Harmony class library)
>
>> Compiled with GNU gcc 4.7 installed via macports (tried 4.9 too, same outcome)
>> No other strange compiler flags added, just a clean development build. (tried the prototype and production configurations too, same outcome)
> Just in case you don't know it already: if you want to change any compiler flags, you'll have to edit the appropriate file in build/hosts.
>
>> Any ideas?
> I don't have any ideas on what the underlying problem could be.
>
> I can't give you much advice on debugging the problem:
> - you can try to use various verbosity options (e.g. -X:verbose, -verbose, -X:verboseBoot) but they're probably not very useful because the problem seems to occur quite early
> - you can run the bootimage runner code with gdb by using "rvm -gdb". Note that this won't help if you need to debug code from the bootimage because debug symbols will be missing. In that case, use a prototype* or Base* configuration and build with "rvm.debug-symbols=true"
> - in general, you might also want to take a look at rdb, a debugger that was developed specifically for the Jikes RVM ( http://sape.inf.usi.ch/rdb )
>
> If you don't want to debug this problem, you could try to build in a Linux virtual machine.
>
>
> Kind regards,
>
> Erik Brangs
>
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Jikesrvm-researchers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers

------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees