All three methods say, in the warning, that the method must override a superclass method. I have not modified the code at all yet. I checked that Eclipse recognizes the types as the same ones in the respective superclasses, and I have tried pressing control-shift-o to organize the imports, which was a fix suggested in this answer for a similar problem.

These overrides are part of the SDK, not any separate project. I set up the project to use Android SDK 2.2 as was shown on Facebook's instructions, and 4.0.3, which should be, theoretically, compatible with all previous versions. I have yet to get Facebook's own code to work. As a side note, is there a jar I can use instead? It would make this much easier.

The lazy, fast and easy fix is to remove the @Override annotations. The correct fix is to check that the project compiles to Java 1.5 or above, to use "fix project properties" from Eclipse, and possibly to check that the Facebook library project uses the same Android SDK for compiling against, as your project.

I did that at one point, but that only made it so it could compile, not run. I will edit my post, though, so I can mention that I cannot get the Facebook Android SDK itself to compile, not my project. And I've tried using different SDKs (Specifically, both 2.2, and the latest which should be compatible with all previous, theoretically), none worked.
–
PoikFeb 7 '12 at 4:04

have you checked the 'Problems' view from Eclipse? It's not shown by default in Indigo and usually contains all the information you need
–
zrgiuFeb 7 '12 at 4:05

That actually told me nothing that I didn't already see in code. "The method onClick(View) of type new View.OnClickListener(){} must override a superclass method", "The method onServiceConnected(ComponentName, IBinder) of type Facebook.TokenRefreshServiceConnection must override a superclass method", and "The method onServiceDisconnected(ComponentName) of type Facebook.TokenRefreshServiceConnection must override a superclass method".
–
PoikFeb 7 '12 at 4:14

Well, I tried removing the Override annotations again, and it worked. Color me crazy, but I was rather certain that abstract methods needed to be declared overridden. Apparently not? I checked where Eclipse thinks it's getting those methods, and it was veritably from the extended abstract classes. Also, both the library and my program work now. My only question is: why can I not use Override in this case, if the code is overriding abstract methods?
–
PoikFeb 7 '12 at 14:49