Can any of you good sparc people try to install the eclipse-cdt-bin (it will pull in dev-util/eclipse-sdk-2.1.3-r3), fire up eclipse, create a new project, and then create a new .c file to see if the C/C++ editor actually works, then reassign the bug back to me?
I emerged it here and tried running eclipse. Couple of questions however; Is a Java project ok? There didn't seem to be any project types that related to C If the Java project is OK, what should I expect to see when I create the .c file? I can create and save a simple hello.c file, but it doesn't appear to be doing anything that indicates it understands the syntax as C or any other type of file. However my experience with eclipse has just been summed up above so I could be missing something here.
It looks good here and I've added the ~sparc keyword. sparc64 users using ~sparc keywords may experience some problems as blackdown-jdk is built for sparcv8 processors and glibc is build for sparcv8+ processors. This can cause some java applications to crash when the jvm tries to do something that it expects libc to be built for the same type of processor. I was getting this here a bit with eclipse and the eclipse-cdt-bin.
Ookay. I'll keep that problem in mind. I've finally secured an ultra10 for myself, so I'll try do some more thorough testing later on. Thanks a bundle!
I had no luck installing eclipse-cdt-bin and following the directions for installing it on Karl's website. I get the same behavior as Jason Wever -- no recognition that C or C++ exists.
Does it show up in the plugins list (Help -> About Eclipse -> Plug-in Details)? If it doesn't check the log file (Help -> About Eclipse -> Configuration Details) and see if some exceptions occur. If you can't see any of this, chances are, you've not added the /opt/eclipse-extensions-3/ directory correctly. There may very well be a flaw in my instructions, if so, reopen this bug or make out a new one and I'll fix it.
