Both Eclipse 3.1 and 3.2 require sys-libs/libstdc++-v3 for the SWT browser widget to work. This maybe should be fixed by the fix-swt-targets() function in the ebuild but for one reason or another is not. My guess is this: I tried building SWT manually myself but the build failed (at least on the mozilla part). I am using GCC 4.1.1 and I think this with the combination of an AMD64 system caused the build to fail. The build failed complaining about loss of precision casting a pointer to jint (which I am assuming is a 32bit integer). So I am assuming that because fix-swt-targets() fails to build SWT the shipped .so files are used and they depend on libstdc++.so.5 (which is provided by sys-libs/libstdc++-v3). I hope this makes some sense, if not, feel free to ask. I will submit a bug upstream about not being able to build on 64bit systems with GCC 4.1.1 but it would be nice to see some solution for this setup incorporated into portage. Without sys-libs/libstdc++-v3 I get one of the following error when trying to set the internal browser in Window->Preferences...->General->Web Browser: !ENTRY org.eclipse.ui.browser 2 0 2006-07-06 23:17:36.231 !MESSAGE Internal browser is not available: No more handles (java.lang.UnsatisfiedLinkError: swt-mozilla-gtk-3232 (Not found in java.library.path)) !ENTRY org.eclipse.ui.browser 2 0 2006-07-09 23:41:16.283 !MESSAGE Internal browser is not available: No more handles (java.lang.UnsatisfiedLinkError: /home/niskel/Apps/eclipse/configuration/org.eclipse.osgi/bundles/49/1/.cp/libswt-mozilla-gtk-3232.so (libstdc++.so.5: cannot open shared object file: No such file or directory))
Closing as this almost certainly does not apply to newer Eclipse versions.
