OSX port

[Henri Gomez]

I tried my old build system for MLVM to produce a new package for OSX
but it fail :

(cd  /Users/henri/Documents/jenkins/data/jobs/openjdk-jdk8-mlvm/workspace/sources/build/macosx-x86_64/bin/..
&& /usr/bin/tar cf - \
	    `/usr/bin/find bin \( -type f -o -type l \) -print `) | \
	    (cd  /Users/henri/Documents/jenkins/data/jobs/openjdk-jdk8-mlvm/workspace/sources/build/macosx-x86_64/j2sdk-image
&& /usr/bin/tar xf -)
/usr/bin/touch /Users/henri/Documents/jenkins/data/jobs/openjdk-jdk8-mlvm/workspace/sources/build/macosx-x86_64/classes/META-INF/services/com.sun.tools.internal.xjc.Plugin
cd  /Users/henri/Documents/jenkins/data/jobs/openjdk-jdk8-mlvm/workspace/sources/build/macosx-x86_64/classes
&& \
	    /Library/Java/JavaVirtualMachines/1.7.0u4.jdk/Contents/Home/bin/jar
c0f /Users/henri/Documents/jenkins/data/jobs/openjdk-jdk8-mlvm/workspace/sources/build/macosx-x86_64/lib/tools.jar
\
	        META-INF/services/com.sun.jdi.connect.Connector
META-INF/services/com.sun.jdi.connect.spi.TransportService
sun/tools/asm sun/tools/jar sun/tools/java sun/tools/javac
sun/tools/jcmd sun/tools/jps sun/tools/jstat sun/tools/jstatd
sun/tools/native2ascii sun/tools/serialver sun/tools/tree
sun/tools/util sun/security/tools/JarBASE64Encoder.class
sun/security/tools/JarSigner.class
sun/security/tools/JarSignerParameters.class
sun/security/tools/JarSignerResources.class
sun/security/tools/JarSignerResources_ja.class
sun/security/tools/JarSignerResources_zh_CN.class
sun/security/tools/SignatureFile\$Block.class
sun/security/tools/SignatureFile.class
sun/security/tools/TimestampedSigner.class sun/rmi/rmic sun/applet
sun/jvmstat com/sun/javadoc com/sun/jdi com/sun/jarsigner
com/sun/source com/sun/tools/classfile com/sun/tools/doclets
com/sun/tools/example/debug/expr com/sun/tools/example/debug/tty
com/sun/tools/extcheck com/sun/tools/hat com/sun/tools/javac
com/sun/tools/javadoc com/sun/tools/javah com/sun/tools/javap
com/sun/tools/corba com/sun/tools/internal/xjc
com/sun/tools/internal/ws
META-INF/services/com.sun.tools.internal.ws.wscompile.Plugin
META-INF/services/com.sun.tools.internal.xjc.Plugin
com/sun/istack/internal/tools com/sun/tools/internal/jxc/ap
com/sun/tools/internal/ws/wscompile/plugin/at_generated
com/sun/codemodel com/sun/tools/internal/jxc
com/sun/xml/internal/rngom com/sun/xml/internal/xsom
org/relaxng/datatype com/sun/xml/internal/dtdparser com/sun/tools/jdi
com/sun/tools/script/shell
META-INF/services/com.sun.tools.attach.spi.AttachProvider
com/sun/tools/attach sun/tools/attach sun/tools/jstack sun/tools/jinfo
sun/tools/jmap -J-XX:-PrintVMOptions -J-XX:+UnlockDiagnosticVMOptions
-J-XX:-LogVMOutput -J-Djava.awt.headless=true -J-Xmx512m -J-Xms512m
-J-XX:PermSize=32m -J-XX:MaxPermSize=160m
META-INF/services/com.sun.tools.internal.ws.wscompile.Plugin : fichier
ou r?pertoire introuvable
com/sun/tools/internal/jxc/ap : fichier ou r?pertoire introuvable
com/sun/tools/internal/ws/wscompile/plugin/at_generated : fichier ou
r?pertoire introuvable
make[2]: *** [initial-image-jdk] Error 1
make[1]: *** [jdk-build] Error 2
make: *** [build_product_image] Error 2

What's current build process to be used ?

Thanks


2012/7/3 Henri Gomez <henri.gomez at gmail.com>:
> Ping on this subject, ie MLVM build for OSX (but not only) in a simpler way ?
>
> 2012/5/9 John Rose <john.r.rose at oracle.com>:
>> On May 9, 2012, at 11:07 AM, Charles Oliver Nutter wrote:
>>
>>> I managed to get MLVM to build on OS X Snow Leopard with Henri's scripts. Notes:
>>>
>>> * I get a failure like this at the end of the build, but this appears
>>> to be after the jdk/jre have successfully built (or at least it
>>> appears to work fine): https://gist.github.com/749b4fe1d3b469644c11
>>
>> Yes, I get this too.  I don't know where it comes from.  There is probably some configuration variable that will make it go away.  Like you, I saw that the build was usable and moved on.
>>
>>> * In order to get the meth-lazy patches to apply (I'm testing the new
>>> indy backend) I had to remove -testable from them. I'd like a cleaner
>>> way.
>>
>> Christian Thalinger, Michael Haupt, and I are working hard to get these patches ready for prime time.  There are several problems that show up in comprehensive testing.  The worst is that TieredCompilation mode shows some failures.  Until we get cleaner tests, we're keeping "-testable".
>>
>> (This raises the question of whether the keyword is misleading but I can't think of another candidate meaning for "testable".  Keyword means "able to pass reasonable tests", not "able to commence testing"; the latter phrase is the meaning of "buildable".)
>>
>> You could regard the act of removing "-testable" as the equivalent of clicking through the "yes I know what I'm doing" button.  You can disable the testable filter by adjusting either the series file (which is managed source code) or the guards file (which is unmanaged and private to the installation).
>>
>> — John
>>
>> _______________________________________________
>> mlvm-dev mailing list
>> mlvm-dev at openjdk.java.net
>> http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev