This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
On 64-bit vista build fails because of unavailable jna jar the workaround is to use 32-bit jdk to build netbeans on 64bit-windows systems generate-method-classes: _gmc_internal_: [echo] Generating invokers... [java] Exception in thread "main" java.lang.UnsatisfiedLinkError: jnidispatch (/com/sun/jna/win32-amd64/jnidispatch.dll) not found in resource path [java] at com.sun.jna.Native.loadNativeLibrary(Native.java:468) [java] at com.sun.jna.Native.<clinit>(Native.java:91) [java] at com.sun.jna.NativeLong.<clinit>(NativeLong.java:23) [java] at org.jruby.ext.ffi.jna.JNAPlatform.longSize(JNAPlatform.java:46) [java] at org.jruby.ext.ffi.StructLayoutBuilder.<clinit>(StructLayoutBuilder.java:60) [java] at java.lang.Class.forName0(Native Method) [java] at java.lang.Class.forName(Class.java:164) [java] at org.jruby.anno.InvokerGenerator.main(InvokerGenerator.java:36) BUILD FAILED C:\A\main\o.jruby.distro\build.xml:63: The following error occurred while executing this line: C:\A\main\o.jruby.distro\build.xml:54: The following error occurred while executing this line: C:\A\main\o.jruby.distro\unpatched_source\jruby-1.1.4\build.xml:389: The following error occurred while executing this line: C:\A\main\o.jruby.distro\unpatched_source\jruby-1.1.4\build.xml:166: The following error occurred while executing this line: C:\A\main\o.jruby.distro\unpatched_source\jruby-1.1.4\build.xml:171: Java returned: 1 Total time: 1 minute 55 seconds
Erno, any chance you might somehow take a look at this on your 64-bit machine?
Sorry, I don't have Vista at my disposal.
It doesn't have to be vista - i think the same problem is on 64bit XP with 64bitJDK
Don't have a 64bit XP either, unfortunately. If you have the time, could you try whether building JRuby works (http:// wiki.jruby.org/wiki/Getting_Started#Downloading_Source_and_Building_Yourself)?
Needs to fixed in jruby, although I guess there is a chance it's fixed already in the 1.2.0 we bundle now -- can you give it a try?