I could emerge eclipse from seden overlay a couple of moths ago and was happy with it.
But now it does not emerge anymore.

Since I rather prefer to work with eclipse than struggle with emerging it, I'm going to try out the binary package from the java-overlay. At least it emerged fine and I started it without any crash.
So the next step is really to use it (on my android project) to see if it satisfies my needs.

Last edited by lindegur on Mon Dec 17, 2012 8:08 pm; edited 1 time in total

Dear Yamakuzure first a big thank you for your quick response and support

In fact I somehow ended up with icedtea. But I switched back to dev-java/sun-jdk:1.6.
Then I updated the overlay to get dev-util/eclipse-sdk-3.7.1-r8::seden
Then I had to remove icedtea due to the blockage.

As I said before, I'm using overlay flora and it provides eclipse-sdk-3.7.1-r2 (I'm OK with this version). To be able to compile this version I had to chose -gnome in USE variable; so it was compiled using this comand:

Code:

USE="-gnome" emerge eclipse-sdk

After that I started having problems with SWT library; in a previous message you'll find a piece of the log. Digging a little bit around it is supposed Eclipse version and SWT must be the very same. So, I had to downgrad SWT to 3.7.1 and mask 3.7.2.

The option -gnome didn't seem to affect visual aspects of Eclipse so I'm happy with it. The compilation worked using sun-jdk-1.6.0.37 and oracle-jdk-bin-1.7.0.9 (this one is going to be ripped of soon).

This link seems to clarify a little bit about the problem. Glib can be included only once and it seems Eclipse doesn't do that (I mean glib.h and gslist.h are being both included, but onle glib.h is mandatory), they said in the bug report: "glib doesn't allow for any other inclusions than glib.h. This was announced a long time ago, and finally introduced in recent versions of glib. glib already includes gslist"

There are some patches along the bugreport but it is for 4.x branch.

I hope it can help you and please let people know if it worked or not.

Ah, this clarifies a lot, thank you for sharing. I have a (as much as possible) gnome-free system, so I never ran into that problem. But I'd rather like to try to create an ebuild for eclipse-sdk-4.2 than trying to fix 3.7.x. However, I do not think this will be possible for me before 2013 (if the world doesn't explode or anything), because I have much on my plate at the moment, and Eclipse is nothing to whip up an ebuild for in a day or two, I'm afraid.

However, I think this can be patched rather easily, so I'll see what can be done for the old 3.7.1.

btw.: -r8 just means that I have changed the ebuild 8 times. Same goes with flora overlay, I guess. The important part is "3.7.1", so both are emerging the same version of Eclipse. _________________elogind(elogind) - [TRACKER] sys-auth/elogind - Integration into Gentoo
"A conservative is a man who is too cowardly to fight and too fat to run."
-- Elbert Hubbard

So using the ebuild directly does not seem to allow me to reproduce the "Only <glib.h> can be included directly."-issue.
It seems the USE was ignored, libgnomeproxy is not built according to the log file.

I am therefore a bit puzzled right now about whether it might be indeed useful to add an ebuild for 3.8.0?

Edith wants to note: My eclipse-sdk-4.2.0.ebuild now successfully prepares eclipse-4.2.0. But I am a bit of a coward now and happy that my debugging of 3.7.1 with gnome USE flag is preventing me to start compiling 4.2.0.

Sorry, I can't reproduce the problem. Maybe its gone due to some new upstream patches? The eclipse-build archive is taken from git, so mine might be more current and have a patch for the problem already.

I am therefore a bit puzzled right now about whether it might be indeed useful to add an ebuild for 3.8.0?

Edith wants to note: My eclipse-sdk-4.2.0.ebuild now successfully prepares eclipse-4.2.0. But I am a bit of a coward now and happy that my debugging of 3.7.1 with gnome USE flag is preventing me to start compiling 4.2.0.

My experience is that 4.2 is SOOOOOOOO slow that you want to get out your eyes.

On the other hand, I haven't got any problem compiling and using eclipse with OpenJDK-1.7 (icedtea 7.2.3.3).

My experience is that 4.2 is SOOOOOOOO slow that you want to get out your eyes.

The Juno release has a terribly slow UI - 4 cores, ssd but 3 to 10 seconds to switch an editor. There are many bug reports at eclipse bugzilla and even a wiki page. Using updates from the repository improved the situation for me. Now i am using the 4.2 weekly maintenance build which is again faster._________________# cd /pub/
# more beer