Diablo-D3/DiabloMiner

Failure to build on OS X Lion (10.7.2)

Closed this issue · 1 comments

Here's the full output, though the main issue is that it fails because OS X Lion no longer supports the PowerPC architecture.

[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ DiabloMiner ---
[INFO] Building jar: /Users/phyreman/git/DiabloMiner/target/DiabloMiner.jar
[INFO]
[INFO] --- launch4j-plugin:1.5.0.0:launch4j (windows binary) @ DiabloMiner ---
[INFO] Platform-specific work directory already exists: /Users/phyreman/.m2/repository/org/bluestemsoftware/open/maven/plugin/launch4j-plugin/1.5.0.0
[INFO] launch4j: Compiling resources
[INFO] launch4j: Launch of "windres" failed: the PowerPC architecture is no longer supported.
[ERROR]
net.sf.launch4j.BuilderException: net.sf.launch4j.ExecException: Exec failed(2): [Ljava.lang.String;@2542880d
at net.sf.launch4j.Builder.build(Builder.java:145)
at com.akathist.maven.plugins.launch4j.Launch4jMojo.execute(Launch4jMojo.java:326)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: net.sf.launch4j.ExecException: Exec failed(2): [Ljava.lang.String;@2542880d
at net.sf.launch4j.Util.exec(Util.java:142)
at net.sf.launch4j.Cmd.exec(Builder.java:206)
at net.sf.launch4j.Builder.build(Builder.java:98)
... 22 more
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.070s
[INFO] Finished at: Sun Jan 15 21:49:14 PST 2012
[INFO] Final Memory: 11M/81M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.bluestemsoftware.open.maven.plugin:launch4j-plugin:1.5.0.0:launch4j (windows binary) on project DiabloMiner: Failed to build the executable; please verify your configuration. net.sf.launch4j.ExecException: Exec failed(2): [Ljava.lang.String;@2542880d -> [Help 1]

That bug has already been filed with launch4j. AFAIK they have not fixed it yet.

See: http://sourceforge.net/tracker/?func=detail&aid=3439121&group_id=95944&atid=613100