Error installing Forge source for MC 1.4.5

[jarrett]

Update: Problem solved. See my comment later in the thread for the solution.

 

I'm attempting to develop a mod for 1.4.5. (The mod is written and working in 1.4.7, but I'm now trying to support 1.4.5 for compatibility with IC2.)

 

Based on this page, I believe that I should be using Forge 6.4.1.436. I downloaded the source for that version. When running install.sh, I get this error:

 

81 errors
13 warnings
==================

Client recompile failed, correct source then rerun updatemd5

 

The error message is actually much longer than what I've pasted, and includes 81 errors and 13 warnings, all seemingly coming from the Java compiler.

 

The exact steps I performed were:

 

[*]Download source

[*]Extract zip file

[*]Set permissions on install.sh

[*]Run install.sh

 

Should I be doing something different to make this version of Forge install? Or is there a different Forge source version I should download to target MC 1.4.5?

[SanAndreaP]

Can we see your complete mcp.log? Use pastebin for that.

[jarrett]

Yep, here's the complete log:

 

http://pastebin.com/9mBWqWcq

[LexManos]

We actually need the console log not mcp.log

[jarrett]

Sorry, could you clarify what you mean by the console log?

 

If you're referring to the output on the OS X terminal when running install.sh, here it is:

 

http://pastebin.com/dKa0kd1n

 

If you're referring to the log generated when the Minecraft client boots, unfortunately I haven't even gotten that far yet. The error occurs when installing the Forge dev environment via install.sh. Because I can't get past that step, it's not possible for me to boot the client either.

 

In any case, I'd be totally fine with using a different Forge release, if that would be an easy solution. I'd be happy with any Forge version that enables me to target MC 1.4.5. Would you recommend a different build?

 

Thanks so much for your help. It is much appreciated.

[SanAndreaP]

  On 5/4/2013 at 5:23 PM, jarrett said:

Sorry, could you clarify what you mean by the console log?

 

If you're referring to the output on the OS X terminal when running install.sh, here it is:

 

http://pastebin.com/dKa0kd1n

 

If you're referring to the log generated when the Minecraft client boots, unfortunately I haven't even gotten that far yet. The error occurs when installing the Forge dev environment via install.sh. Because I can't get past that step, it's not possible for me to boot the client either.

 

In any case, I'd be totally fine with using a different Forge release, if that would be an easy solution. I'd be happy with any Forge version that enables me to target MC 1.4.5. Would you recommend a different build?

 

Thanks so much for your help. It is much appreciated.

 

reformating disabled due to no astyle or config

 

As far as I know, you need one of those. I can only speak for Linux, but I have astyle installed.

[LexManos]

So..

Your console gets spammed to shit saying that EVERY SINGLE HUNK OF EVERY SINGLE PATCH failed..

And you think that isn't important information to share with us?

 

...

 

Anyways install astyle.

[jarrett]

Well the weird thing is, astyle is installed. For verification:

 

$ which astyle
/usr/local/bin/astyle

 

But thanks for pointing out the line where it says it couldn't find astyle. I didn't notice that before. I think that does get us closer to the root of the problem. How does Forge look for astyle? Does it just search the $PATH? Or is there some specific place it looks? If the latter, I could always symlink from there.

 

Here's another line in the console output I find curious:

 

# found ff, ff patches, srgs, name csvs, doc csvs, param csvs, renumber csv, astyle config

 

Also, in case it wasn't clear before, I have successfully installed other versions of Forge on this computer. I even have a working mod. It's really just this particular Forge version that's giving me trouble.

[jarrett]

Looking at it again, I don't think the line I called "curious" is very curious after all. I misunderstood it to mean it was seeing astyle installed. But now I believe it means that it just found the astyle config file in the Forge distribution. So I guess that's not really odd after all.

 

But any thoughts on why install.sh isn't seeing astyle? If worst comes to worst, I'll dig into the Python script and see where it's looking. But I'm hoping that maybe somebody knows a quick fix off the top of their head.

[jarrett]

I have solved my problems. I'd like to post my experiences for the benefit of anyone else who is having similar problems.

 

I've had astyle installed all along. But it appears that 6.4.1.436 cannot detect an installed astyle under some circumstances. I'm not sure exactly what triggers this error, but it happened to me. Thus far, 6.4.1.436 is the only build for which this error occurs for me. I've tested a number of builds, but certainly not anywhere near all of them. I never did figure out what was going on there, but that's OK, because I didn't have to.

 

My solution was to switch to a later build, specifically, 6.4.2.448. This appears to be the last build for MC 1.4.5, which is why I chose it. Interestingly, the Releases forum topic for 1.4.5 doesn't point to this build. Instead, it points to 6.4.1.436, which is the one that gave me problems. I don't know what to make of that. Is 6.4.1.436 the officially supported build? Is 6.4.2.448 OK to use? I don't know the answers to these questions, but maybe someone more knowledgeable could fill in the gaps.

 

In any case, I'm sticking with 6.4.2.448, unless someone advises me to do otherwise. It works for me, and I'm able to deploy my finished mod to a 1.4.5 instance running in MultiMC.