Eclipse Galileo (3.5) was released yesterday. I hope it will make it's way into portage some day?! Reproducible: Always
Also hope someone can make an ebuild. I installed eclipse-3.5 classic from original tar.gz on my x86_64 system, and get the error "org.eclipse.swt.SWTError: XPCOM error -2147467262" when using javadoc tooltips or Here some info about this error on eclipse faq: http://wiki.eclipse.org/IRC_FAQ#Eclipse_gets_past_the_splash_screen_but_then_an_empty_window_appears_.2F_Eclipse_is_crashing_on_me_whenever_I_initiate_a_browser_component_such_as_hovering_over_Java_methods_for_javadoc_tooltips... I have xulrunner installed in version 1.9.0.11, i don't figure out what can solves the problem (still use 3.4, i need a working eclipse day by day). I read that install "xulrunner 1.9.1 stable" should solve that problem. There is no ebuild in portage tree fpr xulrunner 1.9.1, so i cannot test that. Any other experiencies about this?
(In reply to comment #1) > I have xulrunner installed in version 1.9.0.11, i don't figure out what can ... > Any other experiencies about this? I'm using xulrunenr 1.9.1_rc2 from mozilla overlay - eclipse classic 3.5 from tar.gz works fine for me.
@Sebastian Mueller: I can't confirm your problems with xulrunner-1.9.0.11 On my x86 system everything is fine after installing from the classic tarball. Do you use the same configuration directory as for 3.4? I had some problems with old configuration and workspace, so I created a new ~/.eclipse directory and everything runs as expected.
(In reply to comment #3) > @Sebastian Mueller: I can't confirm your problems with xulrunner-1.9.0.11 > > On my x86 system everything is fine after installing from the classic tarball. > > Do you use the same configuration directory as for 3.4? I had some problems > with old configuration and workspace, so I created a new ~/.eclipse directory > and everything runs as expected. > Even if i delete .eclipse folder and use an empty folder as new workspace i got this error and eclipse is closing. org.eclipse.swt.SWTError: XPCOM error -2147467259 maybe the problem only exists on x86_64. Is there anybody with x86_64 and no problem with eclipse 3.5? @Bohdan Popovych: i will try.
> Even if i delete .eclipse folder and use an empty folder as new workspace i got > this error and eclipse is closing. > > org.eclipse.swt.SWTError: XPCOM error -2147467259 > > maybe the problem only exists on x86_64. Is there anybody with x86_64 and no > problem with eclipse 3.5? > > @Bohdan Popovych: i will try. > *sigh* sadly I can confirm bug with: java version "1.6.0_13" Java(TM) SE Runtime Environment (build 1.6.0_13-b03) Java HotSpot(TM) 64-Bit Server VM (build 11.3-b02, mixed mode) net-libs/xulrunner-1.9.0.11 with error: Unhandled event loop exception XPCOM error -2142830590 (fwiw: eclipse runs poorly in server mode... the 32-bit version runs fine as expected)
> > *sigh* sadly I can confirm bug with: > > java version "1.6.0_13" > Java(TM) SE Runtime Environment (build 1.6.0_13-b03) > Java HotSpot(TM) 64-Bit Server VM (build 11.3-b02, mixed mode) > > net-libs/xulrunner-1.9.0.11 So the problem seems to exist only on x86_64 systems. This is what i have installed: dev-java/sun-jdk-1.6.0.13 dev-java/swt-3.4-r2 net-libs/xulrunner-1.9.0.11 and, of course, eclipse-3.5 from tar.gz in my opinion this problem is in one of this packages (i read a lot articles about this problem yesterday and all solutions i found are like: "use xulrunner-1.9.1" and "use a newer swt") i will now try a newer xulrunner from overlay
> i will now try a newer xulrunner from overlay > I tried to install xulrunner-1.9.1_rc3 from mozilla overlay. I also had to update mozilla-firefox-3.5_rc3 from overlay, to have a running firefox at all. After update that i had to run revdep-rebuild to resolve some dependencies with nss (now use dev-libs/nss-3.12.3-r1) and epiphany (now using www-client/epiphany-2.26.2). After that i cleared all configurations (~/.eclipse, ~/.mozilla, [WORKSPACE]/.metadata), and tested eclipse-3.5. The problem resists, when starting eclipse and create a new workspace folder, it crashes with the swt error (xpcom). When i then start, it opens, i can work a short while, then the error appears, mostly when using code-completion or view the javadoc tooltips in the source editor. After the error message, it shows me a dialog that i should close the workspace. If i don't close it, some functions in eclipse don't work until i restart. Its the same problem with xulrunner 1.9.0.11 and 1.9.1_rc3. I also testet swt-3.4.1 and swt-3.4-r2, no difference. Short overview: dev-java/sun-jdk-1.6.0.13 dev-java/swt-3.4.1 net-libs/xulrunner-1.9.1_rc3 dev-libs/nss-3.12.3-r1 Steps to reproduce: 1. Use x86_64 gentoo, you can use stable or testing versions of xulrunner and swt, that make no difference. 2. Install dev-java/sun-jdk-1.6.0.13 3. Unpack eclipse-3.5 classic from original tar.gz 4. clear all configuration, and make an empty folder as new workspace 5. Start eclipse with that workspace. Eclipse will crash. (reproducible always, swt error xpcom) 6. Restart eclipse, use the same workspace. Eclipse will start. 7. Do normal working stuff, use javadoc and code completion in the source editor. After a while i get the error, and eclipse wants to close. The wired thing is that javadoc and code completion works a while, and then stops working. i don't have a clue how to reproduce this, i am just shure that it happens after a half hour of working. (not really reproducible) In [WORKSPACE]/.metadata/.log the error look like this: eclipse.buildId=I20090611-1540 java.version=1.6.0_13 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=de_DE Command-line arguments: -os linux -ws gtk -arch x86_64 !ENTRY org.eclipse.ui 4 0 2009-06-29 18:35:46.348 !MESSAGE Unhandled event loop exception !STACK 0 org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: XPCOM error -2142830590) at org.eclipse.swt.SWT.error(SWT.java:3884) at org.eclipse.swt.SWT.error(SWT.java:3799) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) Caused by: org.eclipse.swt.SWTError: XPCOM error -2142830590 at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:2023) at org.eclipse.swt.browser.Mozilla.OnStateChange(Mozilla.java:2718) at org.eclipse.swt.browser.Mozilla$10.method3(Mozilla.java:1529) at org.eclipse.swt.internal.mozilla.XPCOMObject.callback3(XPCOMObject.java:266) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:1858) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3110) at org.eclipse.jface.internal.text.html.BrowserInformationControl.setVisible(BrowserInformationControl.java:355) at org.eclipse.jface.text.AbstractInformationControlManager.showInformationControl(AbstractInformationControlManager.java:1246) at org.eclipse.jface.text.TextViewerHoverManager.showInformationControl(TextViewerHoverManager.java:283) at org.eclipse.jface.text.AbstractInformationControlManager.internalShowInformationControl(AbstractInformationControlManager.java:1210) at org.eclipse.jface.text.AbstractInformationControlManager.presentInformation(AbstractInformationControlManager.java:1139) at org.eclipse.jface.text.AbstractHoverInformationControlManager.presentInformation(AbstractHoverInformationControlManager.java:902) at org.eclipse.jface.text.TextViewerHoverManager.doPresentInformation(TextViewerHoverManager.java:243) at org.eclipse.jface.text.TextViewerHoverManager$5.run(TextViewerHoverManager.java:233) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) ... 23 more for now i give up, and use eclipse-3.4. Newer xulrunner or swt versions make no difference, i guess the problem is that the jdk starts server-mode, and eclipse should be started with client mode vm. (like letrec mentioned) My java only knows the -server option, the -client option simply not exists. myself@lapslave ~ $ java -version java version "1.6.0_13" Java(TM) SE Runtime Environment (build 1.6.0_13-b03) Java HotSpot(TM) 64-Bit Server VM (build 11.3-b02, mixed mode) Hope this helps someone else to find a workaround, i will now downgrade my packages to stable versions again (xulrunner, swt, nss) and use eclipse-3.4 for now.
I can not confirm this issue using eclipse classic (eclipse-SDK-3.5-linux-gtk-x86_64.tar.gz). Tried to reproduce the issue as described with the following JDK's. OpenJDK7/IcedTea 1.10 [icedtea] OpenJDK6/IcedTea6 1.5 [icedtea6] Sun JDK 1.6.0.13 [sun-jdk-1.6] Steps executed in order to reproduce the issue were 3, 4, 5 (for each JDK) as described in comment #7. I didn't have the time yet for more extensive testing. Further version info: dev-libs/nss-3.12.3-r1 dev-java/swt-3.4.1 net-libs/xulrunner-1.9.1 Btw if simply executing the downloaded and extracted version the eclipse configuration is found in dir_where_files_were_extracted_to/configuration.
Anyone seen any ebuilds around? There is one for 3.5 in here http://bugs.gentoo.org/attachment.cgi?id=188403 but I was hoping to find something more recent.
I can confirm the problem on my x86_64; yesterday i was running eclipse 3.4 without problem and this morning both eclipse 3.4 and 3.5 dont work and i dont update anything :)
(In reply to comment #10) > I can confirm the problem on my x86_64; yesterday i was running eclipse 3.4 > without problem and this morning both eclipse 3.4 and 3.5 dont work and i dont > update anything :) > Then delete your WORKSPACE/.metadata, ~/.mozilla/eclipse, ~/.eclipse. Like Stephan mentioned, there are problems with old configurations. Your problem sounds like eclipse-3.5 changes your configurations, and now eclipse-3.4 has problems with it. On my system eclipse-3.4 runs well! @r.c.g@gmx.de: I also used the classic edition eclipse-SDK-3.5-linux-gtk-x86_64.tar.gz I have no time yet to do further testing, but i will do the next two weeks.
Based on the comments in https://bugs.eclipse.org/bugs/show_bug.cgi?id=276332, I put the following into my eclipse.ini file: -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/firefox Then eclipse didn't crash any more. I'm running Eclipse-3.5 release on x86_64 with xulrunner-1.9.1.
(In reply to comment #12) > Based on the comments in https://bugs.eclipse.org/bugs/show_bug.cgi?id=276332, > I put the following into my eclipse.ini file: > > -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/firefox That solution doesn't work with Eclipse-3.4. I tried to set MOZILLA_FIVE_HOME to /usr/lib64/xulrunner-1.9.1 (where libxpcom.so is located) and set also -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-1.9.1 after -vmargs in /usr/lib64/eclipse-3.4/eclipse.ini. I get always that error message from Comment #1
(In reply to comment #13) > That solution doesn't work with Eclipse-3.4. Respectfully, the discussion in this bug is about eclipse-3.5. > I get always that error message from Comment #1 Since you are getting this error message from eclipse-3.4, perhaps you should file a different bug.
Created attachment 197504 [details] fedora 12 rpm spec, any can write a ebuild? fedora 12 include eclipse 3.5 build script, who can write a ebuild?
(In reply to comment #15) > Created an attachment (id=197504) [edit] > fedora 12 rpm spec, any can write a ebuild? > > fedora 12 include eclipse 3.5 build script, who can write a ebuild? > I am working on the ebuild, I have the deps done up in my personal overlay at the moment soon as I get it all finished and working properly I will pass it along to the java herd for review so we can get it commited in the tree. I just need a bit of help from the java herd which I have already ping'd a dev to help point me in the right direction to getting the final issues resolved.
I am trying to get an ebuild ready too. So far I only got the deps ready by more or less bumping the relevant packages. Also so far I filed a bug about a new swt ebuild -> http://bugs.gentoo.org/show_bug.cgi?id=277704 Maybe we can coordinate our efforts. (In reply to comment #16) > (In reply to comment #15) > > Created an attachment (id=197504) [edit] > > fedora 12 rpm spec, any can write a ebuild? > > > > fedora 12 include eclipse 3.5 build script, who can write a ebuild? > > > > I am working on the ebuild, I have the deps done up in my personal overlay at > the moment soon as I get it all finished and working properly I will pass it > along to the java herd for review so we can get it commited in the tree. I just > need a bit of help from the java herd which I have already ping'd a dev to help > point me in the right direction to getting the final issues resolved. >
Created attachment 198120 [details] eclipse-3.5.tar.gz This is not a full working ebuild as of yet. I am adding it to allow more eyes on it to help fix the last few compile issues. Only ebuild that will need updating is eclipse-sdk-3.5 all other are working as expected. This is based off the 3.5_pre6 ebuild just updated for the final 3.5 release.
(In reply to comment #18) > Created an attachment (id=198120) [edit] > eclipse-3.5.tar.gz > > This is not a full working ebuild as of yet. I am adding it to allow more eyes > on it to help fix the last few compile issues. Only ebuild that will need > updating is eclipse-sdk-3.5 all other are working as expected. This is based > off the 3.5_pre6 ebuild just updated for the final 3.5 release. > The ebuild as it is atm uses EAPI="1". With this version src_prepare() is not executed so I think EAPI should be set to "2". With EAPI="2" some other errors occur related to the paths in the working directory.
Created attachment 198258 [details, diff] Patch to fix problems with EAPI version and work dir The errors related to the working directory can be resolved by setting S="${WORKDIR}" in pkg_setup(). See also the attached patch.
Ah sorry ... was still using the older version of the eclipse-3.5.tar.gz. In the one in here both things are already fixed.
What do you think of the following link: http://dev.eclipse.org/mhonarc/lists/linuxtools-dev/msg00130.html This seems to be exactly what we want.
Comment on attachment 198120 [details] eclipse-3.5.tar.gz correct mimetype so file can be downloaded.
(In reply to comment #0) > Eclipse Galileo (3.5) was released yesterday. > > I hope it will make it's way into portage some day?! > > Reproducible: Always > Got an error using the ebuilds from eclipse-3.5.tar.gz. While emerging eclipse-sdk, I get this: ant_tasks/helpbase-ant.jar: [mkdir] Created dir: /var/tmp/portage/dev-util/eclipse-sdk-3.5/work/plugins/org.eclipse.help.base/temp.folder/ant_tasks/helpbase-ant.jar.bin [javac] Compiling 1 source file to /var/tmp/portage/dev-util/eclipse-sdk-3.5/work/plugins/org.eclipse.help.base/temp.folder/ant_tasks/helpbase-ant.jar.bin [javac] ---------- [javac] 1. ERROR in /var/tmp/portage/dev-util/eclipse-sdk-3.5/work/plugins/org.eclipse.help.base/src_ant/org/eclipse/help/internal/base/ant/BuildHelpIndex.java (at line 17) [javac] import org.eclipse.ant.core.AntCorePlugin; [javac] ^^^^^^^^^^^^^^^ [javac] The import org.eclipse.ant cannot be resolved [javac] ---------- [javac] 2. ERROR in /var/tmp/portage/dev-util/eclipse-sdk-3.5/work/plugins/org.eclipse.help.base/src_ant/org/eclipse/help/internal/base/ant/BuildHelpIndex.java (at line 62) [javac] .getReferences().get(AntCorePlugin.ECLIPSE_PROGRESS_MONITOR); [javac] ^^^^^^^^^^^^^ [javac] AntCorePlugin cannot be resolved [javac] ---------- [javac] 2 problems (2 errors) [javac] Compilation failed. Compiler errors are available in /var/tmp/portage/dev-util/eclipse-sdk-3.5/work/plugins/org.eclipse.help.base/temp.folder/ant_tasks/helpbase-ant.jar.bin.log Here's my emerge --info: Portage 2.2_rc33 (default/linux/amd64/2008.0/desktop, gcc-4.4.1, glibc-2.10.1-r0, 2.6.30-gentoo-r4 x86_64) ================================================================= System uname: Linux-2.6.30-gentoo-r4-x86_64-Intel-R-_Core-TM-2_Duo_CPU_P8400_@_2.26GHz-with-gentoo-2.0.1 Timestamp of tree: Fri, 24 Jul 2009 22:25:01 +0000 ccache version 2.4 [enabled] app-shells/bash: 4.0_p24 dev-java/java-config: 2.1.8-r1 dev-lang/python: 2.4.4-r15, 2.5.4-r2, 2.6.2-r1 dev-python/pycrypto: 2.0.1-r8 dev-util/ccache: 2.4-r8 dev-util/cmake: 2.6.4-r1 sys-apps/baselayout: 2.0.1 sys-apps/openrc: 0.4.3-r3 sys-apps/sandbox: 2.0 sys-devel/autoconf: 2.13, 2.63-r1 sys-devel/automake: 1.4_p6, 1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.2, 1.11 sys-devel/binutils: 2.19.1-r1 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.2.6a virtual/os-headers: 2.6.30 ACCEPT_KEYWORDS="amd64 ~amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -pipe -fno-delete-null-pointer-checks -march=native" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/lib64/ccs/conf /usr/share/config" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/splash /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS="-O2 -pipe -fno-delete-null-pointer-checks -march=native" DISTDIR="/usr/portage/distfiles" FEATURES="ccache distlocks fixpackages parallel-fetch preserve-libs protect-owned sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="en_US.UTF-8" LDFLAGS="-Wl,-O1" LINGUAS="en" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage/layman/roslin /usr/local/portage/layman/thelinux /usr/local/portage/layman/portato /usr/local/portage/layman/yarik-overlay /usr/local/portage/layman/desktop-effects /usr/local/portage/layman/java-overlay /usr/local/portage/layman/sunrise /usr/local/portage/layman/jokey /usr/local/portage/layman/rbu /usr/local/portage/layman/gnome /usr/local/portage/layman/ruby /usr/local/portage/layman/gcc-porting /usr/local/portage/layman/devnull /usr/local/portage/abby" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X a52 aac aalib acl acpi adplug ads aio alsa amd64 amr amrnb ao apache2 aspell atmo audacious avahi bash-completion bcmath beagle berkdb bidi blender-game bluetooth bonjour branding bzip2 cairo caps cardbus ccache cdda cddax cddb cdio cdr cdrom cdrtools chardet chm cifsupcall cjk clamav clamd clamdtop cleartype cli consolekit context contrib corefonts cpio cpudetection cracklib crypt cscope css csv cups cupsddk curl daap dbus dc1394 devhelp dhclient dirac djvu dri dts dv dvb dvd dvdr dvdread dvi dynamicplugin eds emboss encode evo exif expat faac faad fam fasttrack fat fbcon fbcondecor ffmpeg firefox firefox3 fits flac fluidsynth fontforge fortran freetds ftp fuse gadu gcj gconf gd gdbm gdm ggi gif gimp glade glitz glut gmedia gmp gnome gnome-keyring gnome-print gnomecanvas gnomecd gnutella gnutls gpg gpgme gphoto2 gpm graphviz groupwise grub gs gsm gstreamer gtk gtkstyle guile gutenprint hal hddtemp hdf hdf5 hdri iconv icq id3 id3tag idn ieee1394 imagemagick imap imlib ipv6 isdnlog jack java java6 jbig jce joystick jpeg jpeg2k kerberos kpathsea krb4 kvm lame latex lcms ldap libass libcaca libffi libnotify libsamplerate libsysfs libv4l2 live lm_sensors logrotate lua lzma lzo mad matroska mbox mbrola mbx mdnsresponder-compat meanwhile mhash midi mikmod mime mjpeg mmap mmx mng modplug mono mp2 mp3 mp3rtp mp3tunes mp4 mpd mpeg mpeg2 mplayer mtp mudflap multilib musepack mysql nautilus ncurses netpbm networking networkmanager nfs nls nntp nptl nptlonly nsplugin nss ntp nuv octave odbc offensive ogg ogg123 ogm openal openexr opengl openmp pam pcmcia pcre pcsc-lite pdf perl php pidgin pkcs11 plasma player png policykit pop ppds ppm pppd prediction pvr python qdbm qq qt3 qt3support qt4 quicktime rar raw rdesktop readline realmedia reflection rss rtc rtsp ruby samba sasl scanner schroedinger scrobbler sdl sdl-image sdl-sound sdlaudio sensord serial session shout sid silc skins smartcard smime smp sms smtp sndfile sockets socks5 sourceview speex spell spl sqlite srt sse sse2 sse3 sse4a sse5 ssl startup-notification stream subversion svg svgz swat sysfs taglib tcl tcpd tga theora thesaurus threads tiff timidity tk tordns truetype tta type3 unicode upnp usb utils v4l v4l2 valgrind vcd vdr vhook vhosts video videos vim-syntax vistafree vlm vnc voice vorbis wav wavpack webkit wifi winbind winpopup wireshark wma wma-fixed wmf wmp wxwindows x264 xanim xbase xcb xcf xcomposite xemacs xext xft xine xinerama xml xmlreader xmlrpc xmp xorg xpm xrandr xrender xulrunner xv xvid yahoo yv12 zephyr zlib zvbi" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="evdev keyboard synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en" USERLAND="GNU" VIDEO_CARDS="radeonhd radeon" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LC_ALL, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Build eclipse 3.5 from eclipse-sourceBuild-srcIncluded-3.5.zip is broken: http://dev.eclipse.org/mhonarc/lists/linuxtools-dev/msg00139.html Instead it is recommended to use the eclipse-build from the Eclipse Linux Tools project.
I'd to help test recent ebuilds - and am also running against the latest mozilla overlay (for xulrunner, etc) Is the latest version of "the consented ebuild" available here? - or is it on an external overlay. Would be nice to get things moving... new PHP development/auto-completion added via plug-ins in this version =D
Attempted to compile from the attached ebuild (tar.gz), and with the EAPI_and_workdir_fix.diff . Got the same compiler error/output as Comment #24. --------------- init: ant_tasks/helpbase-ant.jar: [mkdir] Created dir: /var/tmp/portage/dev-util/eclipse-sdk-3.5/work/plugins/org.eclipse.help.base/temp.folder/ant_tasks/helpbase-ant.jar.bin [javac] Compiling 1 source file to /var/tmp/portage/dev-util/eclipse-sdk-3.5/work/plugins/org.eclipse.help.base/temp.folder/ant_tasks/helpbase-ant.jar.bin [javac] ---------- [javac] 1. ERROR in /var/tmp/portage/dev-util/eclipse-sdk-3.5/work/plugins/org.eclipse.help.base/src_ant/org/eclipse/help/internal/base/ant/BuildHelpIndex.java (at line 17) [javac] import org.eclipse.ant.core.AntCorePlugin; [javac] ^^^^^^^^^^^^^^^ [javac] The import org.eclipse.ant cannot be resolved [javac] ---------- [javac] 2. ERROR in /var/tmp/portage/dev-util/eclipse-sdk-3.5/work/plugins/org.eclipse.help.base/src_ant/org/eclipse/help/internal/base/ant/BuildHelpIndex.java (at line 62) [javac] .getReferences().get(AntCorePlugin.ECLIPSE_PROGRESS_MONITOR); [javac] ^^^^^^^^^^^^^ [javac] AntCorePlugin cannot be resolved [javac] ---------- [javac] 2 problems (2 errors) [javac] Compilation failed. Compiler errors are available in /var/tmp/portage/dev-util/eclipse-sdk-3.5/work/plugins/org.eclipse.help.base/temp.folder/ant_tasks/helpbase-ant.jar.bin.log -------------- Portage 2.1.6.13 (default/linux/amd64/2008.0, gcc-4.3.2, glibc-2.9_p20081201-r2, 2.6.29-gentoo-r5 x86_64) ================================================================= System uname: Linux-2.6.29-gentoo-r5-x86_64-AMD_Athlon-tm-_64_Processor_3500+-with-gentoo-1.12.11.1 Timestamp of tree: Thu, 06 Aug 2009 11:45:01 +0000 app-shells/bash: 3.2_p39 dev-java/java-config: 2.1.8-r1 dev-lang/python: 2.6.2-r1 dev-util/cmake: 2.6.4 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.6-r2 sys-devel/autoconf: 2.13, 2.63-r1 sys-devel/automake: 1.8.5-r3, 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.27-r2 ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-march=k8 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks fixpackages parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="C" LDFLAGS="-Wl,-O1" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage/layman/mozilla /usr/local/portage/myportage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="3dnow X a52 aac acl acpi alsa amd64 apache2 apm avahi bash-completion berkdb bzip2 bzlib cdda cdr cli cracklib crypt css cups dbus dri dts dv dvd dvdr dvdread encode enscript esd fam ffmpeg fortran ftp gdbm gif gnome gphoto2 gpm gstreamer gtk hal iconv ieee1394 ipv6 isdnlog joystick jpeg jpeg2k lirc matroska mmx mp3 mpeg msn mudflap multilib ncurses networkmanager nls nptl nptlonly offensive ogg opengl openmp pam pcmcia pcre pdf perl png pppd python quicktime raw rdesktop readline reflection rss samba session sockets socks5 spell spl sse sse2 ssl symlink sysfs tcpd tiff truetype unicode usb vcd vorbis wifi x264 xcomposite xine xorg xscreensaver xulrunner xv xvid zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="radeon" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LC_ALL, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Created attachment 203204 [details] Ebuild and dependencies for eclipse-sdk-3.5 This ebuild uses eclipse-build-R0_3_0 in order to build eclipse from eclipse-I20090611-1540-fetched-src.tar.bz2. This is a basic ebuild. The aim was to compile eclipse-sdk at all.
Created attachment 203209 [details] Ebuild and dependencies for eclipse-sdk-3.5 r2 Fixed some issues in src_install() and removed some unused files.
Created attachment 203218 [details] eclipse-sdk-3.5.ebuild Forgot to do "doins" to actually install the files. Fixed this and set permissions on executable properly.
Created attachment 203233 [details] Fixed eclipse-sdk-3.5.ebuild *Sigh* Was still using a hack to set the path to java properly. Now the path to java in build.properties and pdebuild.properties is set correctly and build works without additional hacks.
Created attachment 203436 [details] eclipse-3.5-ebuilds.tar.bz2 Here is a vastly improved ebuild for Eclipse 3.5. Returning are the following benefits: * 'doc' and 'source' USE flags to reduce build time and disk footprint. * Removes plugins for irrelevant platforms to reduce build time. * Rewrites dependency bundles to use system-installed libraries. * Uses system-installed SWT native libraries. * Installing features with the P2 GUI works. * Fewer hacks than the other Eclipse 3.5 ebuilds floating around here. If you're just curious to see the ebuild real quick, you can glance at it here: http://dpaste.com/90843/ To actually install Eclipse 3.5 using this ebuild, you should extract the attached tarball into a Portage overlay directory.
(In reply to comment #32) > Here is a vastly improved ebuild for Eclipse 3.5. Thanks a lot! Missing ant-eclipse-ecj-3.5.ebuild: Corresponding patch available at: . . . --> Bug #278000
Created attachment 203517 [details, diff] Fix build on x86 The attached patch fixes a build problem on x86 with Matt Whitlock's ebuild. Unfortunately the result fails at runtime. You can find the log at -> http://pastebin.com/m31e859f0
(In reply to comment #33) > Missing ant-eclipse-ecj-3.5.ebuild: > Corresponding patch available at: > . . . --> Bug #278000 The Eclipse-Build system bootstraps its own ECJ (Eclipse Compiler for Java), and it does not use the Ant ECJ task, since it uses Eclipse's own PDEBuild to do the actual compilation. Therefore, neither dev-java/eclipse-ecj nor dev-java/ant-eclipse-ecj are required for this ebuild. That is why I omitted them from the tarball.
If the ebuild that eventually makes it into the tree is based on my ebuild from comment #32, then bug #277998 and bug #278000 can be removed from the dependencies list of this bug, as neither is necessary for Eclipse Build.
Created attachment 203548 [details] eclipse-3.5-ebuilds.tar.bz2 (In reply to comment #34) > Created an attachment (id=203517) [edit] > Fix build on x86 > > The attached patch fixes a build problem on x86 with Matt Whitlock's ebuild. > > Unfortunately the result fails at runtime. > You can find the log at -> http://pastebin.com/m31e859f0 > Thanks to Ruediger Gad for identifying the build problem on x86. Attached is a new tarball incorporating a fix similar to the one in his patch of comment #34. (Actually, the new ebuild is a bit more general with its 'javaHome' fixup.) Also, I removed the dev-java/swt-3.5 ebuild from my tarball since it's already in the main Portage tree. I was unable to reproduce the runtime problems you saw. I emerged dev-util/eclipse-sdk-3.5 on my 32-bit chroot Gentoo-stable ("x86") system with the following in my /etc/portage/package.keywords: # for Eclipse 3.5 =dev-java/icu4j-4.0.1* ~x86 ~dev-java/sat4j-core-2.1 ~x86 ~dev-java/sat4j-pseudo-2.1 ~x86 ~dev-java/swt-3.5 ~x86 ~dev-util/eclipse-sdk-3.5 ~x86 I was then able to run the produced Eclipse SDK, create a Java project, create a Java class, type some code into it, compile it, and execute it inside the Eclipse IDE. No problems. Ruediger, did you install using the 'emerge' command, which would have built and installed all dependencies, or did you try installing using the 'ebuild' command? It seems like you didn't get dev-java/sat4j installed properly.
(In reply to comment #35) > (In reply to comment #33) > > Missing ant-eclipse-ecj-3.5.ebuild: > ... Therefore, neither dev-java/eclipse-ecj nor > dev-java/ant-eclipse-ecj are required for this ebuild. That is why I omitted > them from the tarball. Hi, Matt, I agree upon that - but nevertheless my emerge refused to build without upgrading that dependency ;( ?? (my workstation is based upon amd64).
Created attachment 203605 [details] Build failure on ~x86 Hello, I tried to update to eclipse 3.5 from 3.4 using the ebuilds from comment #37 on my ~x86 machine with USE="cairo gnome opengl xulrunner -doc -source -test java6" and got a build error. Updating dev-java/ant-eclipse-ecj and dev-java/eclipse-ecj to 3.5 did not help. Here is (IMHO) the most relevant part of the error I got: [java] !ENTRY org.eclipse.osgi 2 0 2009-09-09 17:25:07.412 [java] !MESSAGE One or more bundles are not resolved because the following root constraints are not resolved: [java] !SUBENTRY 1 org.eclipse.osgi 2 0 2009-09-09 17:25:07.412 [java] !MESSAGE Bundle initial@reference:file:plugins/org.eclipse.jface_3.5.0.I20090525-2000/ was not resolved. [java] !SUBENTRY 2 org.eclipse.jface 2 0 2009-09-09 17:25:07.413 [java] !MESSAGE Missing required bundle org.eclipse.swt_[3.4.0,4.0.0). [java] [java] !ENTRY org.eclipse.osgi 2 0 2009-09-09 17:25:07.414 [java] !MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists: [java] !SUBENTRY 1 org.eclipse.osgi 2 0 2009-09-09 17:25:07.414 [java] !MESSAGE Bundle org.eclipse.jface_3.5.0.I20090525-2000 [63] was not resolved. [java] !SUBENTRY 2 org.eclipse.jface 2 0 2009-09-09 17:25:07.414 [java] !MESSAGE Missing required bundle org.eclipse.swt_[3.4.0,4.0.0). [java] !SUBENTRY 1 org.eclipse.osgi 2 0 2009-09-09 17:25:07.414 [java] !MESSAGE Bundle org.eclipse.jface.text_3.5.0.v20090602 [65] was not resolved. [java] !SUBENTRY 2 org.eclipse.jface.text 2 0 2009-09-09 17:25:07.414 [java] !MESSAGE Missing required bundle org.eclipse.jface_[3.5.0,4.0.0). BUILD FAILED /var/tmp/portage/dev-util/eclipse-sdk-3.5/work/eclipse-build-R0_3_0/build.xml:101: Java returned: 13 Total time: 3 minutes 15 seconds * * ERROR: dev-util/eclipse-sdk-3.5 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 4266: Called die * The specific snippet of code: * ./build.sh || die * The die message: * (no error message) * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-util/eclipse-sdk-3.5/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-util/eclipse-sdk-3.5/temp/environment'. * This ebuild is from an overlay named 'local': '/usr/local/portage/' * !!! When you file a bug report, please include the following information: GENTOO_VM=sun-jdk-1.6 CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.6.0.16" JAVACFLAGS="-source 1.6 -target 1.6" COMPILER="" # emerge --info Portage 2.2_rc40 (default/linux/x86/10.0/desktop, gcc-4.3.4, glibc-2.10.1-r0, 2.6.30-gentoo-r6 i686) ================================================================= System uname: Linux-2.6.30-gentoo-r6-i686-AMD_Athlon-tm-_64_Processor_3500+-with-gentoo-2.0.1 Timestamp of tree: Sun, 06 Sep 2009 11:15:01 +0000 ccache version 2.4 [disabled] app-shells/bash: 4.0_p28 dev-java/java-config: 2.1.9 dev-lang/python: 2.6.2-r1, 3.1.1 dev-util/ccache: 2.4-r8 dev-util/cmake: 2.6.4-r2 sys-apps/baselayout: 2.0.1 sys-apps/openrc: 0.4.3-r3 sys-apps/sandbox: 2.1 sys-devel/autoconf: 2.13, 2.63-r1 sys-devel/automake: 1.9.6-r2, 1.10.2, 1.11 sys-devel/binutils: 2.19.1-r1 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.2.6a virtual/os-headers: 2.6.30-r1 ACCEPT_KEYWORDS="x86 ~x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=athlon64 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config /var/lib/hsqldb" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/splash /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c" CXXFLAGS="-O2 -march=athlon64 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="assume-digests collision-protect distlocks fixpackages multilib-strict parallel-fetch preserve-libs protect-owned sandbox sfperms strict unmerge-logs unmerge-orphans userfetch" GENTOO_MIRRORS="http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://de-mirror.org/distro/gentoo/ http://mirror.switch.ch/ftp/mirror/gentoo/ http://mirror.switch.ch/ftp/mirror/gentoo/" LANG="en_US.UTF-8" LC_ALL="en_US.UTF-8" LDFLAGS="-Wl,-O1" LINGUAS="en" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage/layman/java-overlay /usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage/" USE="3dnow 3dnowext X X509 a52 aac aalib acpi aiglx alias alsa asf audiofile avahi bash-completion binary-drivers branding bzip2 cairo cdinstall cdparanoia cdr chroot cli cmake connectionstatus cracklib crypt cscope css cups curl custom-cflags custom-optimization dbus dedicated dga directfb divx djvu dri dts dvd dvdr eds embedded emboss enca encode evo exif exiv2 expat fam fat fbcon fbcondecor fbsplash ffmpeg fftw firefox firefox3 flac fltk fontconfig foomaticdb ftp fuse gdbm gif gimp gimpprint glib glitz glut gmedia gmp gmplayer gnutls google-gadgets gphoto2 gpm graphviz gs gstreamer gtk hal hddtemp hdri history hpn iconv icq idn imagemagick imlib inotify ip4100 irc isdnlog jabber java java6 javascript jbig jce jikes jpeg jpeg2k kde kipi kpathsea lame latex lcms ldap libcaca libnotify live lm_sensors logitech-mouse logrotate lzo mad mdnsresponder-compat mikmod mime mjpeg mmap mmx mmxext mozdevelop mozilla moznocompose moznoirc moznomail mp2 mp3 mp4 mpeg mplayer mudflap mysql ncurses nls no-old-linux nptl nptlonly nsplugin ntfs nvidia offensive ogg openal openexr opengl openmp oscar pam pango pcre pdf perl plasma png ppds pppd profilei psyco python qmake qt3 qt3support qt4 quicktime rar raster readline realmedia reflection reiserfs replytolist rss rtc rtsp sasl sdl servicetools session speex spell spl sql srt sse sse2 ssl startup-notification statistics subversion svg svnserve sysfs syslog taglib tagwriting tcpd texteffect theora threads threadsafe thumbnail thunar tiff tk tordns translator truetype unicode upnp urandom usb userlocales utempter v4l v4l2 vcd vim vim-syntax vim-with-x visualization vorbis webkit webpresence win32codecs wma wmf wmp x264 x86 xcb xcomposite xforms xfs xft xine xml xmp xorg xulrunner xv xvid xvmc zlib zsh-completion" ALSA_CARDS="via82xx" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="alias auth_basic auth_digest authn_anon authn_dbd authn_default authz_default authz_host authz_owner authz_user autoindex cache dbd deflate dir disk_cache env expires ext_filter file_cache filter headers ident imagemap include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack" ELIBC="glibc" INPUT_DEVICES="evdev keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en" NETBEANS_MODULES="cnd ide dlight ergonomics java profiler harness nb websvccommon" USERLAND="GNU" VIDEO_CARDS="nvidia" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS The following packages are installed from java-overlay (if that matters): dev-java/ant-eclipse-ecj-3.4.1 dev-java/dom4j-1.6.1-r6 dev-java/eclipse-ecj-3.4.1-r1 dev-util/eclipse-sdk-3.4.1 java-virtuals/jaxb-api-2 virtual/jdk-1.6.0-r2 It seems to fail finding swt although I have both version 3.4 and 3.5 installed, any ideas?
(In reply to comment #37) > Created an attachment (id=203548) [edit] > eclipse-3.5-ebuilds.tar.bz2 > > (In reply to comment #34) > > Created an attachment (id=203517) [edit] > > Fix build on x86 > > > > The attached patch fixes a build problem on x86 with Matt Whitlock's ebuild. > > > > Unfortunately the result fails at runtime. > > You can find the log at -> http://pastebin.com/m31e859f0 > > > > Thanks to Ruediger Gad for identifying the build problem on x86. Attached is a > new tarball incorporating a fix similar to the one in his patch of comment #34. > (Actually, the new ebuild is a bit more general with its 'javaHome' fixup.) > > Also, I removed the dev-java/swt-3.5 ebuild from my tarball since it's already > in the main Portage tree. > > I was unable to reproduce the runtime problems you saw. I emerged > dev-util/eclipse-sdk-3.5 on my 32-bit chroot Gentoo-stable ("x86") system with > the following in my /etc/portage/package.keywords: > > # for Eclipse 3.5 > =dev-java/icu4j-4.0.1* ~x86 > ~dev-java/sat4j-core-2.1 ~x86 > ~dev-java/sat4j-pseudo-2.1 ~x86 > ~dev-java/swt-3.5 ~x86 > ~dev-util/eclipse-sdk-3.5 ~x86 > > I was then able to run the produced Eclipse SDK, create a Java project, create > a Java class, type some code into it, compile it, and execute it inside the > Eclipse IDE. No problems. > > Ruediger, did you install using the 'emerge' command, which would have built > and installed all dependencies, or did you try installing using the 'ebuild' > command? It seems like you didn't get dev-java/sat4j installed properly. > Thanks for your quick response. The problem turned out to be related to an earlier eclipse installation. After deleting ~/.eclipse eclipse starts up fine.
(In reply to comment #37) > Created an attachment (id=203548) [edit] > eclipse-3.5-ebuilds.tar.bz2 I was trying to emerge eclipse with this ebuild. I run into 2 problems first one with a moving file line in the ebuild, output below: * Checking for at least 512MBytes RAM ... [ ok ] * Checking for at least 3072MBytes disk space at ${T} ... [ ok ] >>> Unpacking eclipse-build-R0_3_0.tar.gz to /var/tmp/portage/dev-util/eclipse-sdk-3.5/work mv: cannot move `/var/tmp/portage/dev-util/eclipse-sdk-3.5/distdir/eclipse-I20090611-1540-fetched-src.tar.bz2' to `/var/tmp/portage/dev-util/eclipse-sdk-3.5/work/eclipse-build-R0_3_0/eclipse-I20090611-1540-fetched-src.tar.bz2': Permission denied * * ERROR: dev-util/eclipse-sdk-3.5 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 4342: Called die * The specific snippet of code: * mv "${DISTDIR}/eclipse-${BUILD_ID}-fetched-src.tar.bz2" "${S}"/ || die; * The die message: * (no error message) I changed the command from mv to cp in this line and then the build started, but after few minutes it stopped with same build error as in comment #39. My emerge --info: Portage 2.2_rc40 (default/linux/x86/2008.0/desktop, gcc-4.4.1, glibc-2.9_p20081201-r2, 2.6.30-tuxonice-r5 i686) ================================================================= System uname: Linux-2.6.30-tuxonice-r5-i686-Intel-R-_Pentium-R-_M_processor_1600MHz-with-gentoo-2.0.1 Timestamp of tree: Tue, 08 Sep 2009 11:15:01 +0000 distcc 3.1 i686-pc-linux-gnu [enabled] ccache version 2.4 [enabled] app-shells/bash: 3.2_p39 dev-java/java-config: 2.1.9 dev-lang/python: 2.4.6, 2.5.4-r2, 2.6.2-r1, 3.1.1 dev-python/pycrypto: 2.0.1-r8 dev-util/ccache: 2.4-r8 dev-util/cmake: 2.6.4-r2 sys-apps/baselayout: 2.0.1 sys-apps/openrc: 0.4.3-r3 sys-apps/sandbox: 2.1 sys-devel/autoconf: 2.13, 2.63-r1 sys-devel/automake: 1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.2.6a virtual/os-headers: 2.6.27-r2 ACCEPT_KEYWORDS="x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium-m -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/config /var/lib/hsqldb" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/splash /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS="-O2 -march=pentium-m -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="assume-digests ccache distcc distlocks fixpackages metadata-transfer parallel-fetch paraller-fetch preserve-libs protect-owned sandbox sfperms strict unmerge-logs unmerge-orphans userfetch userpriv usersandbox" GENTOO_MIRRORS="http://ftp.spline.inf.fu-berlin.de/mirrors/gentoo/ http://gentoo.zie.pg.gda.pl http://gentoo.mirror.pw.edu.pl/ " LANG="pl_PL.utf8" LDFLAGS="-Wl,--as-needed" LINGUAS="pl en" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage/local/layman/kde-testing /usr/portage/local/layman/sunrise /usr/portage/local/layman/zugaina /usr/portage/local/layman/desktop-effects /usr/portage/local/layman/java-overlay /usr/portage/local/layman/qting-edge /usr/portage/local/layman/mozilla /usr/portage/local/layman/sabayon /usr/portage/local/manual" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="7zip X a52 aac aalib acl acpi akonadi alsa amr amrnb amrwb bash-completion berkdb bluetooth branding bzip2 cairo cdaudio cdda cddb cdr chm cli consolekit cracklib crypt cups curl custom-cflags custom-cxxflags dbus dga dhcp directfb djvu dmx doc dri dts dv dvd dvdr editor emboss enca encode evo exif fbcon fbcondecor fbsplash ffmpeg firefox flac fontconfig fortran fpx ftp gcj gd gdbm ggi gif glitz gnokii gnutls gohoto2 gpm gps graphviz gs gsm gstreamer hal hddtemp hdri htmlhandbook i8x0 ical iconv icu id3tag ieee1394 imagemagick ipod irda isdnlog java java5 java6 javascript jbig jce jingle joystick jpeg jpeg2k kde kerberos kipi ladspa lame laptop lcms libcaca libnotify libsamplerate lm_sensors log4j logrotate lzo mad matroska midi mikmod mjpeg mmx mmxext mng mono mp2 mp3 mp3rtp mp4 mpeg mpi msn mudflap musepack musicbrainz mysql ncurses network networkmanager nls nptl nptlonly nsplugin ogg openal openexr opengl openmp oscar pam pcre pdf perl phonon plasma pmu png ppds pppd python qt3 qt3support qt4 quicktime rar raw rdesktop readline reflection rss samba schroedinger sdl semantic-desktop sensord session shroedinger slp sms sndfile soundtouch sox speex spell spl sql sqlite sse sse2 ssl startup-notification svg svga symlink sysfs syslog taglib tcpd theora threads thumbnail thunar tidy tiff timidity truetype twolame unicode usb v4l v4l2 vcd vidix vnc vorbis wavpack webkit win32codecs winpopup wlm wmf x264 x86 xanim xcb xcomposite xinerama xml xmldoclet xmp xorg xpm xprint xscreensaver xulrunner xv xvid xvmc yahoo zeroconf zlib" ALSA_CARDS="intel8x0" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CAMERAS="canon" ELIBC="glibc" INPUT_DEVICES="synaptics mouse keyboard joystick" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="pl en" USERLAND="GNU" VIDEO_CARDS="radeon vesa v4l" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LC_ALL, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
(In reply to comment #38) > (In reply to comment #35) > > > (In reply to comment #33) > > > Missing ant-eclipse-ecj-3.5.ebuild: > > > ... Therefore, neither dev-java/eclipse-ecj nor > > dev-java/ant-eclipse-ecj are required for this ebuild. That is why I omitted > > them from the tarball. > > Hi, Matt, > I agree upon that - but nevertheless my emerge refused to build > without upgrading that dependency ;( ?? > (my workstation is based upon amd64). > Could you double check you are using only the ebuild and dependencies Matt provided? E.g. by deleting everything related to eclipse and its dependencies in your local overlay and then again copy the files from the latest tar in here. Here everything builds and runs fine with neither ant-eclipse-ecj nor eclipse-ecj being installed. I also run eclipse using the ebuild from the most recent tar on a x86_64 machine at work.
I would just like to note that Attachment #203548 [details] builds a perfectly functional (~amd64) Eclipse Galileo for me without any trouble at all. All I did was extract the tarball into my PORTDIR_OVERLAY and emerge -av eclipse-sdk. Dependencies were pulled in and built without trouble, and Eclipse launched and opened my workspace without so much as a complaint. I didn't even have trouble with Xulrunner (gasp!) Kudos to Matt! Great job!
(In reply to comment #39) > [java] !ENTRY org.eclipse.osgi 2 0 2009-09-09 17:25:07.412 > [java] !MESSAGE One or more bundles are not resolved because the following > root constraints are not resolved: > [java] !SUBENTRY 1 org.eclipse.osgi 2 0 2009-09-09 17:25:07.412 > [java] !MESSAGE Bundle > initial@reference:file:plugins/org.eclipse.jface_3.5.0.I20090525-2000/ was not > resolved. > [java] !SUBENTRY 2 org.eclipse.jface 2 0 2009-09-09 17:25:07.413 > [java] !MESSAGE Missing required bundle org.eclipse.swt_[3.4.0,4.0.0). > It seems to fail finding swt although I have both version 3.4 and 3.5 > installed, any ideas? It looks to me like the more important error is at line 4328 of your log file: [javac] The system is out of resources. [javac] Consult the following stack trace for details. [javac] java.lang.OutOfMemoryError: Java heap space Perhaps the max heap size for the java invocation needs to be increased. My system has 8 GB of memory, so the default max heap size (which seems to be calculated based on the amount of system RAM) is likely sufficient. A system with less RAM might need a max heap size specified explicitly to avoid running into that OutOfMemoryError. When I run the build, a chain of java processes is invoked (each a child of the last), and they use an ungodly amount of RAM. For example: Grandparent process's RSS: 1277048 KB Parent process's RSS: 951868 KB Child process's RSS: 300200 KB I'm not sure which of these might need its -Xmx set explicitly on your system, nor do I know an appropriate value to set. Theoretically, this problem belongs to the Linux-Tools team at Eclipse, since all the ebuild is doing at that point is calling ./build.sh. Maybe you could file a bug at: http://wiki.eclipse.org/Linux_Tools_Project/Eclipse_Build#To-do_list (In reply to comment #41) > (In reply to comment #37) > > Created an attachment (id=203548) [edit] > > eclipse-3.5-ebuilds.tar.bz2 > > I was trying to emerge eclipse with this ebuild. I run into 2 problems first > one with a moving file line in the ebuild, output below: > * Checking for at least 512MBytes RAM ... > [ ok ] > * Checking for at least 3072MBytes disk space at ${T} ... > [ ok ] > >>> Unpacking eclipse-build-R0_3_0.tar.gz to /var/tmp/portage/dev-util/eclipse-sdk-3.5/work > mv: cannot move > `/var/tmp/portage/dev-util/eclipse-sdk-3.5/distdir/eclipse-I20090611-1540-fetched-src.tar.bz2' > to > `/var/tmp/portage/dev-util/eclipse-sdk-3.5/work/eclipse-build-R0_3_0/eclipse-I20090611-1540-fetched-src.tar.bz2': > Permission denied This is bizarre. Are you running emerge as root? Try changing the 'mv' to an 'ln -s'.
> This is bizarre. Are you running emerge as root? Try changing the 'mv' to an > 'ln -s'. > Thanks a lot for such a quick answer. Sure I was running as root (all deps were installed w/o any problem) and Yes I agree this is bizarre :D. I had exactly same problem on my 2nd machine. But both cp or ln -s did the job and the building is now staring. Still there was a out of memory problem: [javac] The system is out of resources. [javac] Consult the following stack trace for details. [javac] java.lang.OutOfMemoryError: Java heap space My notebook has 1GB of ram and my other computer has 3GB both had the same problem. After little search i found this: http://bugs.gentoo.org/show_bug.cgi?id=229609#c47 So I added ANT_OPTS="-Xmx512M" just before build.sh in src_compile() and guess what, it helped. I was able to emerge and use eclipse-3.5 on both computers. The only problem is that setting this in that static way it's not the best solution I think. But that's what did the job for me. I'm happy I can use Eclipse the gentoo way. Thx for the ebuilds and additional info u provided great job guys.
(In reply to comment #45) > So I added ANT_OPTS="-Xmx512M" just before build.sh in src_compile() and guess > what, it helped. I was able to emerge and use eclipse-3.5 on both computers. > The only problem is that setting this in that static way it's not the best > solution I think. But that's what did the job for me. That seems like a reasonable way to set the max heap size for the build, though it might slow down the build for people with large amounts of RAM since it would artificially limit the heap size on systems on which it could grow larger by default. What if you specify a large value for the *initial* heap size, -Xms? Then maybe it would ensure enough heap is available on systems with little memory but not artificially limit heap growth on systems with lots of memory. Could you see if ANT_OPTS="-Xms384M" (that's "Xms", not "Xmx") lets the build complete with no OutOfMemoryError? If you still get the OOME at 384 MB, try bumping it up by small increments (maybe 32 MB at a time) until the error goes away. Whatever value we end up with, we'll need to set CHECKREQS_MEMORY in the ebuild to 3 times that value (since it seems there are at most 3 java processes active at a time).
(In reply to comment #44) > It looks to me like the more important error is at line 4328 of your log file: > > [javac] The system is out of resources. > [javac] Consult the following stack trace for details. > [javac] java.lang.OutOfMemoryError: Java heap space > > Perhaps the max heap size for the java invocation needs to be increased. My > system has 8 GB of memory, so the default max heap size (which seems to be > calculated based on the amount of system RAM) is likely sufficient. A system > with less RAM might need a max heap size specified explicitly to avoid running > into that OutOfMemoryError. > Thanks, I have indeed only 1G of RAM and the Xmx setting was too low. (In reply to comment #46) > That seems like a reasonable way to set the max heap size for the build, though > it might slow down the build for people with large amounts of RAM since it > would artificially limit the heap size on systems on which it could grow larger > by default. > I have used -Xmx2048M in a similar way as in comment #45 and it worked fine, although I have only 1G of RAM (and 1G of swap). So, using ANT_OPTS="-Xmx2048M" ./build.sh in the ebuild seems to be a good solution for everyone.
(In reply to comment #47) > I have used -Xmx2048M in a similar way as in comment #45 and it worked fine, > although I have only 1G of RAM (and 1G of swap). So, using ANT_OPTS="-Xmx2048M" > ./build.sh in the ebuild seems to be a good solution for everyone. I don't think that's a good solution, either, because it will result in a lot of swapping on systems with less than 2 GB of RAM. Running the garbage collector more often is still going to be faster than swapping garbage to and from the disk all the time. What we really want is the following: * A lower bound on the maximum heap size that is large enough to allow the build to complete without an OutOfMemoryError. * An upper bound on the maximum heap size that is small enough to prevent excessive swapping. * After the above two constraints are met, a large heap size that reduces the number of garbage collection runs that need to occur. The JVM seems to have some built-in intelligence about default values for Xms (initial heap size) and Xmx (maximum heap size) depending on the amount of system RAM. I proposed in comment #46 that we allow the JVM to pick the maximum size using its heuristics but we force an initial size that is large enough to allow the build to complete successfully. (On systems with little RAM, the initial size we specify might actually be larger than the maximum size that the JVM would choose, but I think the explicit initial size will be honored and the assumed maximum size will be adjusted to accommodate it.)
I installed eclipse 3.5 with the latest ebuild attached to this bug report. Developing of OSGi bundles is currently not possible, if one of the following bundles is used from the default Target Platform: org.apache.commons.codec org.apache.commons.httpclient org.apache.commons.logging I checked the bundles in /usr/lib64/eclipse-3.5/bundles and they contain only the plugin.properties and MANIFEST.MF files. All compiled classes are missing in that bundle/jar files. I did not investigate if this is an issue of the ebuild or the ant build.
(In reply to comment #49) > I installed eclipse 3.5 with the latest ebuild attached to this bug report. > > Developing of OSGi bundles is currently not possible, if one of the following > bundles is used from the default Target Platform: > org.apache.commons.codec > org.apache.commons.httpclient > org.apache.commons.logging > > I checked the bundles in /usr/lib64/eclipse-3.5/bundles and they contain only > the plugin.properties and MANIFEST.MF files. All compiled classes are missing > in that bundle/jar files. I did not investigate if this is an issue of the > ebuild or the ant build. Yes, that is what the dependency unbundling step does. Look at the manifests, and you will see a "Bundle-ClassPath" property that references the jars installed on your system in /usr/share/commons-{codec,httpclient-3,logging}/. As for why your project's class path is not picking up the referenced "external" jars, I couldn't tell you.
(In reply to comment #46) That seems like a reasonable way to set the max heap size for the build, though > it might slow down the build for people with large amounts of RAM since it > would artificially limit the heap size on systems on which it could grow larger > by default. > > What if you specify a large value for the *initial* heap size, -Xms? Then > maybe it would ensure enough heap is available on systems with little memory > but not artificially limit heap growth on systems with lots of memory. Could > you see if ANT_OPTS="-Xms384M" (that's "Xms", not "Xmx") lets the build > complete with no OutOfMemoryError? If you still get the OOME at 384 MB, try > bumping it up by small increments (maybe 32 MB at a time) until the error goes > away. > > Whatever value we end up with, we'll need to set CHECKREQS_MEMORY in the ebuild > to 3 times that value (since it seems there are at most 3 java processes active > at a time). > I must say i did try to follow the test u suggested but the results are so weird that I don't know what to say. First i tried to set -Xms384M and what i got it was not even an outOfMemory but: >>> Compiling source in /var/tmp/portage/dev-util/eclipse-sdk-3.5/work/eclipse-build-R0_3_0 ... Error occurred during initialization of VM Incompatible minimum and maximum heap sizes specified I was trying to find out when this problem begins and I tried to set -Xms to very low values and the conclusion is: any value lower or equal to 64MB is making the eclipse build but with OutOfMemmory error. Any value -Xms higher then 64MB is giving the Incompatible minimum and maximum heap sizes specified output. I was also trying to set up both values -Xms and -Xmx first lover 2nd higher with quite a few values but any values I put I end up with Incompatible minimum and maximum heap sizes specified.
(In reply to comment #50) > Yes, that is what the dependency unbundling step does. Look at the manifests, > and you will see a "Bundle-ClassPath" property that references the jars > installed on your system in /usr/share/commons-{codec,httpclient-3,logging}/. > > As for why your project's class path is not picking up the referenced > "external" jars, I couldn't tell you. Ah, I see. I will check why those external classpath references do not work in my setup.
I was also trying to set up both values -Xms and -Xmx first lover 2nd > higher with quite a few values but any values I put I end up with Incompatible > minimum and maximum heap sizes specified. > woops I misplaced letters (-Xxm) did not noticed it so what I wrote earlier is obviously not true, when 2 values are set the eclipse is building (even if -Xms is very low like 64M). The -Xms alone is acting as I wrote.
Created attachment 203689 [details] eclipse-3.5-ebuilds.tar.bz2 (In reply to comment #53) > woops I misplaced letters (-Xxm) did not noticed it so what I wrote earlier is > obviously not true, when 2 values are set the eclipse is building (even if -Xms > is very low like 64M). The -Xms alone is acting as I wrote. Thanks for trying. Now we know my proposal doesn't work. I guess we'll have to live with ANT_OPTS="-Xmx512M" and CHECKREQS_MEMORY="1536". I ran an informal benchmark to compare the build times for the two cases: No ANT_OPTS: real 6m11.286s user 6m14.781s sys 1m51.282s ANT_OPTS='-Xmx512M' real 6m7.273s user 6m21.129s sys 1m48.142s Apparently it doesn't make much of a difference in speed. Attached is an updated tarball with the 'ln -s' change to address Andrzej's problem (comment #41) and ANT_OPTS='-Xmx512M' passed to build.sh to address the OutOfMemoryError issue (comment #44).
thanx, works like a charm on my core2.
Created attachment 204167 [details] tar with screenshot from eclipse and exported OSGi test bundle I tested OSGi bundle development. And I still have the problem that classes imported by externally referenced jar files are not found. javax.servlet bundle of my eclipse installation references /usr/share/tomcat-servlet-api-2.5/lib/servlet-api.jar and the classes of that jar are not available. I don't know where to search for the cause of that problem. Can you give me any advice how to solve that issue?
> I tested OSGi bundle development. And I still have the problem that classes > imported by externally referenced jar files are not found. javax.servlet bundle > of my eclipse installation references > /usr/share/tomcat-servlet-api-2.5/lib/servlet-api.jar and the classes of that > jar are not available. I don't know where to search for the cause of that > problem. Can you give me any advice how to solve that issue? Look at section 20.4 of this document: http://www.eclipse.org/orbit/documents/RCP_Chapter20.pdf I imported your project into Eclipse and see the same errors you see. I think Eclipse's compiler must not support the "external" keyword in the Bundle-ClassPath manifest property. I was able to compile your source file when I added "/usr/share/tomcat-servlet-api-2.5/lib/servlet-api.jar" as an external JAR on the project's build path. Doing so does not affect the dependency shown under "Plug-In Dependencies," so I think this should probably work. OSGi clearly supports "external" jars in the Bundle-ClassPath since Eclipse is able to start up with many of its bundles (including SWT!) gutted and switched to "external" references to system-installed jars beneath /usr/share. So try adding the servlet-api.jar as an external JAR on your project's build path, build the plugin, and do whatever you do to make it actually run, and see if OSGi figures out the "external" reference at runtime.
(In reply to comment #57) > I imported your project into Eclipse and see the same errors you see. I think > Eclipse's compiler must not support the "external" keyword in the > Bundle-ClassPath manifest property. > > So try adding the servlet-api.jar as an external JAR on your project's build > path, build the plugin, and do whatever you do to make it actually run, and see > if OSGi figures out the "external" reference at runtime. Then this is only another bad behavior of the eclipse compiler during development that is completely different than in runtime. Many thanks for your advice. So I can only state that this eclipse 3.5 build is really cool stuff and works nice for me! And only OSGi bundle development sucks even more than ever before ;-)
Well, Eclipse 3.5.1 == Galileo SR1 is out, including numerous bug fixes. But be warned: Network acces to the eclipse servers is worse than horrrible at the moment (typically around ~2.5 kiloByte/s). Trying to upgrade via the internal "Check for updates" yields . . "nothing to update". Trying to explicitly "install new software" = selecting the Eclipse SDK 3.5.1.M20090917-0800 yields . . "Cannot complete the request. . . See the error log for details. . . Eclipse SDK will be ignored because it is already installed, . . and updates are not permitted." The latter 'not permitted' seems quite strage to me ... and is reported to be created by org.eclipse.equinox.p2.ui P.S.: As update sites, I have enabled . . http://download.eclipse.org/releases/galileo and . . http://download.eclipse.org/eclipse/updates/3.5 which should be sufficient for updating the . . Eclipse SDK 3.5.0.I20090611-1540 from org.eclipse.sdk.ide itself.
(In reply to comment #59) > Well, Eclipse 3.5.1 == Galileo SR1 is out, including numerous bug fixes.... I ran into the slow downloads as well. I wasn't able to update 3.5.0 to 3.5.1 either. I'm guessing that you have to start fresh with SR1. That's what I did.
(In reply to comment #60) > (In reply to comment #59) > ... you have to start fresh with SR1. That's what I did. Which way? The eclipse-sdk-3.5.ebuild is relying upon BUILD_ID="I20090611-1540" SRC_URI="http://download.eclipse.org/technology/linuxtools/eclipse-build/eclipse-${BUILD_ID}-fetched-src.tar.bz2 - and understandably, they have not published anything newer than eclipse-I20090611-1540-fetched-src.tar.bz2 yet. So I assume you went the road of a direct local install via downloading the (binary) dist.file?
(In reply to comment #61) > (In reply to comment #60) > > (In reply to comment #59) Or did you adapt from eclipse-sdk-3.4.2.ebuild to a -3.5.1 ?
(In reply to comment #61) > (In reply to comment #60) > > ... you have to start fresh with SR1. That's what I did. > > Which way? I've never been happy using Eclipse ebuilds. I just get the distributions from eclipse.org and install them in my home directory. (If there's a better way, please let me know.)
(In reply to comment #63) I see - thanks for you quick answer. ( Perhaps I will investigate -> /usr/local or -> /opt ) Kind regards Manfred
The Linux-Tools team is preparing for a Linux-Tools 0.4 release, which I would guess will include a fetch-src tarball of Eclipse 3.5.1.
(In reply to comment #65) Indeed, it seems that linuxtools look promising: 0.4 release: Milestone 2009-10-07: disclosed at http://www.eclipse.org/projects/project-plan.php?projectid=technology.linux-distros 0.4 RC0 and RC1 already published (at least since 21- and 24-Sep-2009) at http://download.eclipse.org/technology/linuxtools/eclipse-build/ 0.5 release: already planned for only ~ 8 weeks later: mentioned in http://dev.eclipse.org/mhonarc/lists/linuxtools-dev/msg00217.html 1.0 release is targeted at 2010 Q2: "SDK packaging tools: 3.5 eclipse-build, SDK tests, plugin-building scripts, testing scripts. Native development tools: Tracing tools, Systemtap integration, autotools, libhover, ChangeLog, OProfile, Valgrind, GProf, GCov."
(In reply to comment #65) > The Linux-Tools team is preparing for a Linux-Tools 0.4 release, which I would > guess will include a fetch-src tarball of Eclipse 3.5.1. Good news! Andrew Overholt is preparing eclipse-I20090917-0800-fetched-src.tar.bz2 as we speak. Quoting from his post to the linuxtools-dev discussion list, dated 28-Sep-2009 8:54 am: > I was trying to generate it on Friday but I think everyone > hitting the servers to update was killing them. I'm going to try again > today.
eclipse-3.5-ebuilds.tar.bz2 seems not to work for me - missing non-existsing swt-3.5
(In reply to comment #68) > eclipse-3.5-ebuilds.tar.bz2 seems not to work for me - missing non-existsing > swt-3.5 > When was the last time you sync'd your Portage tree? -rw-r--r-- 1 root root 5902 2009-07-20 09:05 /usr/portage/dev-java/swt/swt-3.5.ebuild
Created attachment 205690 [details] eclipse-3.5.1-ebuilds.tar.bz2 Attached is a new tarball containing ebuilds for Eclipse 3.5.1.
(In reply to comment #70) > Created an attachment (id=205690) [edit] > eclipse-3.5.1-ebuilds.tar.bz2 > > Attached is a new tarball containing ebuilds for Eclipse 3.5.1. > Thanks! Great! P.S.: The transfer rates with eclipse.org are still horrible. Can we ease their burden, e.g. by specifying a local mirror to the ebuild - e.g. http://ftp-stud.fht-esslingen.de/pub/Mirrors/eclipse/technology/linuxtools/eclipse-build/ ?
(In reply to comment #71) > The transfer rates with eclipse.org are still horrible. How does Portage's mirrors URL scheme work? Is there a file I can put into the overlay to introduce a new magic mirror like mirrors://eclipse/...?
(In addendum to comment #71 and in reply to comment #72) Hi, Matt, as a quick hack, I manually downloaded the files from the local Mirror and placed them into portage's distfiles directory, thus circumventing a download rate ~ 2 kByte cumulationg into an estimated download time of approx. above 3 h (!) resulting in ~ 2 min. ;) Your ebuild worked like a charm ... Afterwards, into Window -> preferences -> Install/Update, I placed my mirror: # (disabled) http://download.eclipse.org/releases/galileo http://ftp-stud.fht-esslingen.de/pub/Mirrors/eclipse/releases/galileo/ # (disabled) http://download.eclipse.org/eclipse/updates/3.5 http://ftp-stud.fht-esslingen.de/pub/Mirrors/eclipse/eclipse/updates/3.5 "checked for updates" and installed e.g. C++ tools in less than a minute.
(In reply to comment #72) > (In reply to comment #71) > > The transfer rates with eclipse.org are still horrible. > > How does Portage's mirrors URL scheme work? Is there a file I can put into the > overlay to introduce a new magic mirror like mirrors://eclipse/...? > We should expect eclipse to re-sort to a GeoDNS based bind server (named-geodns). This means that, at the dns query level, servers will attempt to re-direct to the nearest / fastest eclipse.org mirror, and their primary site would become almost idle :)
Created attachment 206057 [details] eclipse-3.5.1-ebuilds.tar.bz2 Unbundled org.hamcrest.core plugin in favor of system-installed dev-java/hamcrest-core.
I've experienced the problems described in https://bugs.eclipse.org/bugs/show_bug.cgi?id=291257 while using x11-libs/gtk+-2.18.1 from the Gnome overlay. If anyone experiences problems with non-responding buttons, this can be solved by running eclipse with "GDK_NATIVE_WINDOWS=true eclipse-3.5". Though >=x11-libs/gtk+-2.18 is not yet in portage, it might be wise to add "export GDK_NATIVE_WINDOWS=true" to the eclipse-3.5 wrapper script.
I tried installing eclipse using your 3.5.1 ebuild, and it worked fine. However, i was unable to install some plugins from the galileo update site afterwards. The errors made it sound like a version error in the base Eclipse install which lead to some dependencies being unable to be fullfilled. I tried installing the Java Language Tools, fwiw. I noticed you still use the 0.3.0 linuxtools scripts, while their page says only 0.4* is compatible with 3.5.1, might that cause that?
(In reply to comment #77) > I noticed you still use the 0.3.0 linuxtools scripts, while their page says > only 0.4* is compatible with 3.5.1, might that cause that? I did have to hack the 0.3.0 Eclipse Build a bit to make it build Eclipse 3.5.1, as the Eclipse Build scripts and config files are very brittle and version-specific. There is a possibility I missed something. Has Eclipse Build 0.4 been released?
Any idea when this ebuild will hit portage? It seems to work fine. Portage users are still stuck on 3.4.1.
(In reply to comment #78) > > Has Eclipse Build 0.4 been released? > Not yet, the newest version is still 0.4_RC1.
(In reply to comment #66) (In reply to comment #80) > 0.4 release: Milestone 2009-10-07: These plans have been postponed to the end of this month: "2009-10-28" Unfortunately, the former envisioned goal to integrate AutoTools has been dropped ;( for this 0.4 release; it now reads: "Integration of GProf contribution, initial tracing framework implementation scripts for running SDK tests against distro packages" (In reply to comment #79) PROPOSAL: To me, together with 0.4, this ebuild should result into a reasonable stable combination to get it into portage at the beginning of next month (at least as "M~") (and finally close this bug). Many thanks to Matt again!
(In reply to comment #81) > Unfortunately, the former envisioned goal to integrate AutoTools has been > dropped ;( for this 0.4 release Sorry, I have to correct myself: There's still hope (at least): http://dev.eclipse.org/mhonarc/lists/linuxtools-dev/msg00224.html
(In reply to comment #81) > (In reply to comment #79) PROPOSAL: > To me, together with 0.4, this ebuild should result into a reasonable stable > combination to get it into portage at the beginning of next month (at least as > "M~") (and finally close this bug). Many thanks to Matt again! > Unfortunately I can do what I want, I can't install eclipse-sdk-3.5.1 with the above ebuilds. I've even unmerged eclipse-sdk-3.4 and removed everything related with --deplclean and emerged 3.5.1 with ACCEPT_KEYWORDS="~amd64". Everytime I get: -------------------------------------------- [java] !ENTRY org.eclipse.osgi 2 0 2009-10-16 14:48:23.232 [java] !MESSAGE One or more bundles are not resolved because the following root constraints are not resolved: [java] !SUBENTRY 1 org.eclipse.osgi 2 0 2009-10-16 14:48:23.233 [java] !MESSAGE Bundle initial@reference:file:plugins/org.eclipse.jface_3.5.1.M20090826-0800/ was not resolved. [java] !SUBENTRY 2 org.eclipse.jface 2 0 2009-10-16 14:48:23.233 [java] !MESSAGE Missing required bundle org.eclipse.swt_[3.5.0,4.0.0). [java] [java] !ENTRY org.eclipse.osgi 2 0 2009-10-16 14:48:23.243 [java] !MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists: [java] !SUBENTRY 1 org.eclipse.osgi 2 0 2009-10-16 14:48:23.243 [java] !MESSAGE Bundle org.eclipse.jface_3.5.1.M20090826-0800 [63] was not resolved. [java] !SUBENTRY 2 org.eclipse.jface 2 0 2009-10-16 14:48:23.244 [java] !MESSAGE Missing required bundle org.eclipse.swt_[3.5.0,4.0.0). [java] !SUBENTRY 1 org.eclipse.osgi 2 0 2009-10-16 14:48:23.244 [java] !MESSAGE Bundle org.eclipse.jface.text_3.5.1.r351_v20090708-0800 [65] was not resolved. [java] !SUBENTRY 2 org.eclipse.jface.text 2 0 2009-10-16 14:48:23.244 [java] !MESSAGE Missing required bundle org.eclipse.jface_[3.5.0,4.0.0). BUILD FAILED ----------------------------------------- Both with downloaded archives from the above mirror and from the official site.
(In reply to comment #83) After re-reading this whole thread I started "playing around" with the -Xms and -Xmx settings mentioned in comments 40-50 but without any success. Although I do get an OutOfMemory Exception (even with -Xmx 2048M), I have no line stating that the system is out of resources. The build fails with this: --------------------------------- [java] [javac] [reading org/eclipse/jface/text/templates/TemplateContext.class] [java] [javac] [reading org/eclipse/jface/text/templates/DocumentTemplateContext.class] [java] [java] BUILD FAILED [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-R0_3_0/bootstrap/plugins/org.eclipse.pde.build/scripts/build.xml:36: The following error occurred while executing this line: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-R0_3_0/bootstrap/plugins/org.eclipse.pde.build/scripts/build.xml:105: The following error occurred while executing this line: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-R0_3_0/build/eclipse-R3_5_1-fetched-src/buildConfigs/eclipse-build-config/customTargets.xml:18: The following error occurred while executing this line: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-R0_3_0/build/eclipse-R3_5_1-fetched-src/buildConfigs/eclipse-build-config/allElements.xml:16: The following error occurred while executing this line: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-R0_3_0/bootstrap/plugins/org.eclipse.pde.build_3.5.0.v20090527-1800/scripts/genericTargets.xml:114: The following error occurred while executing this line: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-R0_3_0/bootstrap/plugins/org.eclipse.pde.build_3.5.0.v20090527-1800/scripts/genericTargets.xml:124: The following error occurred while executing this line: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-R0_3_0/build/eclipse-R3_5_1-fetched-src/compile.eclipse-build-feature.xml:261: The following error occurred while executing this line: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-R0_3_0/build/eclipse-R3_5_1-fetched-src/plugins/org.eclipse.jdt.ui/build.xml:396: The following error occurred while executing this line: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-R0_3_0/build/eclipse-R3_5_1-fetched-src/plugins/org.eclipse.jdt.ui/build.xml:324: java.lang.reflect.InvocationTargetException [java] [java] Total time: 9 minutes 8 seconds [java] [java] !ENTRY org.eclipse.osgi 4 0 2009-10-17 09:59:54.356 [java] !MESSAGE Application error [java] !STACK 1 [java] java.lang.reflect.InvocationTargetException (... alot of "exception X caused by" and all stating an InvocationTargetException ...) ... later it results in an OutOfMemory Exception: [java] Caused by: java.lang.reflect.InvocationTargetException [java] at sun.reflect.GeneratedMethodAccessor71.invoke(Unknown Source) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:597) [java] at org.eclipse.jdt.core.JDTCompilerAdapter.execute(JDTCompilerAdapter.java:79) [java] ... 37 more [java] Caused by: java.lang.OutOfMemoryError: Java heap space [java] at java.io.BufferedReader.<init>(BufferedReader.java:80) [java] at java.io.BufferedReader.<init>(BufferedReader.java:91) [java] at org.eclipse.jdt.internal.compiler.util.Util.getInputStreamAsCharArray(Util.java:385) ... from now on everything ends in an [java] Caused by: java.lang.OutOfMemoryError: Java heap space at ...alot... [java] --- Nested Exception --- found 11 times in the log. --------------------- But I noticed that this output: !!! When you file a bug report, please include the following information: GENTOO_VM=sun-jdk-1.6 CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.6.0.15" JAVACFLAGS="-source 1.6 -target 1.6" COMPILER="" states that CLASSPATH and COMPILER are empty?
(In reply to comment #84) > Although I do get an OutOfMemory Exception (even with -Xmx 2048M) Could you post a diff of your modified ebuild against the ebuild in my tarball? I want to make sure you're setting ANT_OPTS correctly. Don't attach your diff to this bug (you might confuse others who don't read the comments) -- instead, paste the diff into a comment or email it to me. > But I noticed that this output: > > !!! When you file a bug report, please include the following information: > GENTOO_VM=sun-jdk-1.6 CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.6.0.15" > JAVACFLAGS="-source 1.6 -target 1.6" COMPILER="" > > states that CLASSPATH and COMPILER are empty? The ebuild uses Eclipse-Build from the Linux-Tools project to perform the build. Portage knows nothing about what goes on inside Eclipse-Build, so most of what is reported there is meaningless.
(In reply to comment #85) > (In reply to comment #84) > > Although I do get an OutOfMemory Exception (even with -Xmx 2048M) > > Could you post a diff of your modified ebuild against the ebuild in my tarball? First: I tried to emerge 3.5 first, because some posts read like 3.5.1 might need to update an existing 3.5 installation. But 3.5 fails in exactly the same way. Second: I tried with an unmodified ebuild first, setting Xms and Xmx didn't change anything. Here's the diff: --------------------------- sed-notebook sed # diff -au /home/sed/Downloads/software/eclipse-3.5.1-ebuilds/dev-util/eclipse-sdk/eclipse-sdk-3.5.1.ebuild /usr/local/portage/dev-util/eclipse-sdk/eclipse-sdk-3.5.1.ebuild --- /home/sed/Downloads/software/eclipse-3.5.1-ebuilds/dev-util/eclipse-sdk/eclipse-sdk-3.5.1.ebuild 2009-10-05 07:58:02.000000000 +0200 +++ /usr/local/portage/dev-util/eclipse-sdk/eclipse-sdk-3.5.1.ebuild 2009-10-17 09:41:32.378556800 +0200 @@ -129,7 +129,8 @@ } src_compile() { - ANT_OPTS='-Xmx512M' ./build.sh || die +# ANT_OPTS='-Xmx512M' ./build.sh || die + ANT_OPTS='-Xms768M -Xmx2048M' ./build.sh || die } src_install() {
(In reply to comment #86) > Second: I tried with an unmodified ebuild first, setting Xms and Xmx didn't > change anything. I can't imagine that any part of the Eclipse build would suffer an OOME with those enormous heap parameters, unless you don't have enough available memory for the heaps of the various Java processes to expand to those sizes. With an -Xmx of 2048M, you'll need at least 4.75 GB (2*Xmx + 1*Xms) of free RAM when starting the build. This is because, from what I can tell, there are at most three Java processes invoked concurrently, each using the heap parameters you specify, and the heaps of the first two may have already grown to their max sizes when the third starts.
(In reply to comment #87) > (In reply to comment #86) > > Second: I tried with an unmodified ebuild first, setting Xms and Xmx didn't > > change anything. > > I can't imagine that any part of the Eclipse build would suffer an OOME with > those enormous heap parameters, unless you don't have enough available memory > for the heaps of the various Java processes to expand to those sizes. With an > -Xmx of 2048M, you'll need at least 4.75 GB (2*Xmx + 1*Xms) of free RAM when > starting the build. Yes, I thought so, too. that's why I tried with an unmodified (aka "-Xmx512M") ebuild first. But someone posted that -Xmx2048M worked for them on a laptop with 1GB RAM and 1GB swap. I have 1GB RAM and 2GB swap, so I thought I'll give it a try. Neither 3.5 nor 3.5.1 complains about running out of resources, though... It's just this wretched Exception... I'll try with setting no ANT_OPTS next, maybe the vm knows how to do it without running out of heap.
(In reply to comment #88) > I'll try with setting no ANT_OPTS next, maybe the vm knows how to do it without > running out of heap. > ...no and yes. Instead of 11 it only shows 2 OutOfMemory Exceptions and now fails with a lot: ---------------------------- [java] Caused by: java.lang.ClassNotFoundException: org.eclipse.jdt.core.JDTCompilerAdapter [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:200) [java] at java.security.AccessController.doPrivileged(Native Method) [java] at java.net.URLClassLoader.findClass(URLClassLoader.java:188) [java] at org.eclipse.ant.internal.core.AntClassLoader.findClass(AntClassLoader.java:54) [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:307) [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:252) [java] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) [java] at java.lang.Class.forName0(Native Method) [java] at java.lang.Class.forName(Class.java:247) [java] at org.apache.tools.ant.util.ClasspathUtils.newInstance(ClasspathUtils.java:266) [java] ... 39 more [java] --- Nested Exception --- --------------------------- Odd... I have 59 of those now...
I'm experiencing exactly the same issues as Sven Eden.. Does anyone have a clue about how to fix this?
(In reply to comment #90) > I'm experiencing exactly the same issues as Sven Eden.. > Does anyone have a clue about how to fix this? > I gave up trying to compile eclipse and created an ebuild for the binary package. I opened an apposite bug: http://bugs.gentoo.org/show_bug.cgi?id=290127 Hope it will be useful to someone!
*** Bug 290127 has been marked as a duplicate of this bug. ***
When using gtk+-2.18.x some mouse interactions are "strange" in the way that e.g. mouse clicks are not fully working. Symptoms are e.g. that the button in the GUI is reacting on the push but the corresponding action is not performed. Running eclipse as follows seems to fix this issue: GDK_NATIVE_WINDOWS=true eclipse-3.5 Should "GDK_NATIVE_WINDOWS=true" go into the eclipse start script? The suggestion for using the above "fix" is from the following bug: http://bugs.gentoo.org/show_bug.cgi?id=291297
(In reply to comment #93) > When using gtk+-2.18.x some mouse interactions are "strange" in the way that > e.g. mouse clicks are not fully working. > Symptoms are e.g. that the button in the GUI is reacting on the push but the > corresponding action is not performed. > > Running eclipse as follows seems to fix this issue: > GDK_NATIVE_WINDOWS=true eclipse-3.5 > > Should "GDK_NATIVE_WINDOWS=true" go into the eclipse start script? > The suggestion for using the above "fix" is from the following bug: > http://bugs.gentoo.org/show_bug.cgi?id=291297 > I've already added that environment variable to the eclipse-3.5 startup script in my local overlay. I'm intending to include the change in my next tarball release, which I plan to make once Eclipse-Build 0.4 is released.
(In reply to comment #94) > > I've already added that environment variable to the eclipse-3.5 startup script > in my local overlay. I'm intending to include the change in my next tarball > release, which I plan to make once Eclipse-Build 0.4 is released. > The Eclipse-Build project actually added the proper patch to their project and it will be applied when building eclipse using Eclipse-Build. The Startup Script modification is only necessary for binary builds.
(In reply to comment #81) (In reply to comment #93) 0.4 RC2 released today - 0.4 Final to be expected: <cite> # From: Andrew Overholt ... # Date: Tue, 3 Nov 2009 ... ... Building the Eclipse SDK: eclipse-build 0.4RC2 ... I've tagged eclipse-build 0.4RC2. Barring any major show-stoppers, I hope this can become what we ship with 0.4 final. ... </cite> ( http://dev.eclipse.org/mhonarc/lists/linuxtools-dev/msg00265.html )
(In reply to comment #94) > (In reply to comment #93) > > When using gtk+-2.18.x some mouse interactions are "strange" in the way that > > e.g. mouse clicks are not fully working. > > Symptoms are e.g. that the button in the GUI is reacting on the push but the > > corresponding action is not performed. > > > > Running eclipse as follows seems to fix this issue: > > GDK_NATIVE_WINDOWS=true eclipse-3.5 > > > > Should "GDK_NATIVE_WINDOWS=true" go into the eclipse start script? > > The suggestion for using the above "fix" is from the following bug: > > http://bugs.gentoo.org/show_bug.cgi?id=291297 > > > > I've already added that environment variable to the eclipse-3.5 startup script > in my local overlay. I'm intending to include the change in my next tarball > release, which I plan to make once Eclipse-Build 0.4 is released. > http://carroll.aset.psu.edu/pub/eclipse/technology/linuxtools/eclipse-build/ I have added your sat4j ebuilds to java-experimental. And am also attempting to look at the eclipse ebuild. Would you like to use the RC2 and produce something. Im working on it currently, but my time is very limited.
I have been able to build Eclipse-3.5.1 using the attached ebuilds, and the GDK_NATIVE_WINDOWS export fixed the problem I was having the the buttons, but I'm still having focus problems with the editor. After initially creating a file, I am able to edit it without problems. But after I switch focus away from the editor, I am no longer able to return to it. The name of the file in the editor's tab will be grayed out, and it will not respond to keyboard input. I can only edit the text by copy/pasting with the mouse. I did not experience this problem before upgrading from 3.4.
(In reply to comment #98) > I have been able to build Eclipse-3.5.1 using the attached ebuilds, and the > GDK_NATIVE_WINDOWS export fixed the problem I was having the the buttons, but > I'm still having focus problems with the editor. > After initially creating a file, I am able to edit it without problems. But > after I switch focus away from the editor, I am no longer able to return to it. > The name of the file in the editor's tab will be grayed out, and it will not > respond to keyboard input. I can only edit the text by copy/pasting with the > mouse. I did not experience this problem before upgrading from 3.4. > Never mind. This appears to be an upstream bug.
Created attachment 209835 [details] eclipse-3.5.1-ebuilds.tar.bz2 Updated tarball to use Eclipse-build 0.4RC3 for building Eclipse 3.5.1. Also, removed swt-3.5.1 and icu4j-4.0.1.1, as they are now in the main Portage tree.
Hello, I'm getting: >>> Downloading 'http://download.eclipse.org/technology/linuxtools/eclipse-build/eclipse-R3_5_1-fetched-src.tar.bz2' --2009-11-11 12:13:01-- http://download.eclipse.org/technology/linuxtools/eclipse-build/eclipse-R3_5_1-fetched-src.tar.bz2 Translacja download.eclipse.org... 206.191.52.47 Łączenie się z download.eclipse.org|206.191.52.47|:80... połączono. Żądanie HTTP wysłano, oczekiwanie na odpowiedź... 200 OK Długość: 79061683 (75M) [application/x-bzip2] Zapis do: `/var/tmp/distfiles/eclipse-R3_5_1-fetched-src.tar.bz2' 100%[==============================================================================================================================================>] 79.061.683 126K/s w 22m 42s 2009-11-11 12:35:48 (56,7 KB/s) - zapisano `/var/tmp/distfiles/eclipse-R3_5_1-fetched-src.tar.bz2' [79061683/79061683] ('Filesize does not match recorded size', 79061683, 86976475) !!! Fetched file: eclipse-R3_5_1-fetched-src.tar.bz2 VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 79061683 !!! Expected: 86976475 Refetching... File renamed to '/var/tmp/distfiles/eclipse-R3_5_1-fetched-src.tar.bz2._checksum_failure_.JXWzQW'
Created attachment 209922 [details] Crash Log I build Eclipse using your ebuilds, and after re-digesting the tarball it build flawelessly. However, when trying to start Eclipse, it immediately crashes. Crash Log is attached, it appears to be failing on SWT. I'm running the Sun JDK6 and GTK+ 2.18.3 from the gnome overlay.
(In reply to comment #102) > I build Eclipse using your ebuilds, and after re-digesting the tarball it build > flawelessly. However, when trying to start Eclipse, it immediately crashes. > > Crash Log is attached, it appears to be failing on SWT. I'm running the Sun > JDK6 and GTK+ 2.18.3 from the gnome overlay. What versions of SWT and Sat4J do you have installed? # equery list swt 'sat4j*'
I had no trouble building Eclipse (after re-digesting) on two computers. On one, it runs fine. On the other, I get the same message as Comment #102. * Searching for swt ... [IP-] [ ~] dev-java/swt-3.5.1 (3.5) * Searching for sat4j* ... [I-O] [ ~] dev-java/sat4j-core-2.1 (2) [I-O] [ ~] dev-java/sat4j-pseudo-2.1 (2)
(In reply to comment #101) > ('Filesize does not match recorded size', 79061683, 86976475) > !!! Fetched file: eclipse-R3_5_1-fetched-src.tar.bz2 VERIFY FAILED! > !!! Reason: Filesize does not match recorded size > !!! Got: 79061683 > !!! Expected: 86976475 Someone in the Linux Tools project must have replaced that file with a different version but the same name. Shame on them! I am testing with the new version now.
(In reply to comment #103) > > What versions of SWT and Sat4J do you have installed? > swt-3.5.1 sat4j-core-2.1 sat4j-pseudo-2.1 No other versions are installed.
(In reply to comment #102) > I build Eclipse using your ebuilds, and after re-digesting the tarball it build > flawelessly. However, when trying to start Eclipse, it immediately crashes. I downloaded the new eclipse-R3_5_1-fetched-src.tar.bz2, re-digested it, built and installed the new ebuild, and my Eclipse is still starting fine. (In reply to comment #104) > I had no trouble building Eclipse (after re-digesting) on two computers. On > one, it runs fine. On the other, I get the same message as Comment #102. Dustin, what is different between your two computers? Are they the same ARCH? Is the installed SWT the one from the main Portage tree? Are the installed Sat4J ebuilds the ones from my tarball?
> Dustin, what is different between your two computers? Are they the same ARCH? > Is the installed SWT the one from the main Portage tree? Are the installed > Sat4J ebuilds the ones from my tarball? > Unfortunately, the computer that works is sleeping soundly at home now, so I can't check anything on it until this evening. However, the one that doesn't is a fresh install. I just extracted the tarball into an overlay and ran `emerge -av eclipse-sdk`. It pulled in swt from the mainline tree and sat4j from the overlay. Hardware wise, the machines are the same. Both ~amd64 vmware virtual machines.
(In reply to comment #107) > (In reply to comment #102) > > I build Eclipse using your ebuilds, and after re-digesting the tarball it build > > flawelessly. However, when trying to start Eclipse, it immediately crashes. > > I downloaded the new eclipse-R3_5_1-fetched-src.tar.bz2, re-digested it, built > and installed the new ebuild, and my Eclipse is still starting fine. > > (In reply to comment #104) > > I had no trouble building Eclipse (after re-digesting) on two computers. On > > one, it runs fine. On the other, I get the same message as Comment #102. > > Dustin, what is different between your two computers? Are they the same ARCH? > Is the installed SWT the one from the main Portage tree? Are the installed > Sat4J ebuilds the ones from my tarball? > I'm getting the same run-time crash. Same versions of swt and sat4j as above. Here is my emerge --info: $ emerge --info Portage 2.1.6.13 (default/linux/x86/10.0, gcc-4.3.2, glibc-2.9_p20081201-r2, 2.6.30.5 i686) ================================================================= System uname: Linux-2.6.30.5-i686-Intel-R-_Xeon-R-_CPU_X5460_@_3.16GHz-with-gentoo-1.12.11.1 Timestamp of tree: Tue, 10 Nov 2009 23:00:21 +0000 app-shells/bash: 4.0_p28 dev-java/java-config: 2.1.9-r1 dev-lang/python: 2.6.2-r1 dev-util/cmake: 2.6.4 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.6-r2 sys-devel/autoconf: 2.13, 2.63-r1 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.2.6a virtual/os-headers: 2.6.27-r2 ACCEPT_KEYWORDS="x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=core2 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config /var/lib/hsqldb" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-O2 -march=core2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks fixpackages parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LDFLAGS="-Wl,-O1" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X acl berkdb bzip2 cli cracklib crypt cups dbus dri fontforce fortran gdbm gpm iceweasel iconv ipv6 java java6 kde kvm mng modules mudflap mysql ncurses nls nptl nptlonly nsplugin opengl openmp pam pcre perl pppd python qt3support qt4 readline reflection rss session spl sql ssl svg sysfs tcpd threads unicode vim-syntax webkit x86 xcomposite xinerama xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="nv nvidia" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, MAKEOPTS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Okay, the only difference between my working and nonworking computers is that the working computer had an existing ~/.eclipse and the nonworking did not. I verified this by renaming my ~/.eclipse on the working computer and attempting to launch. I received the aforementioned error in that case. Removing the newly created ~/.eclipse and renaming the old one back fixed the issue. Both computers are ~amd64 running dev-java/swt-3.5.1 from the mainline tree and dev-java/sat4j-*-2.1 from the tarball.
(In reply to comment #110) > Okay, the only difference between my working and nonworking computers is that > the working computer had an existing ~/.eclipse and the nonworking did not. I > verified this by renaming my ~/.eclipse on the working computer and attempting > to launch. I received the aforementioned error in that case. Removing the newly > created ~/.eclipse and renaming the old one back fixed the issue. > > Both computers are ~amd64 running dev-java/swt-3.5.1 from the mainline tree and > dev-java/sat4j-*-2.1 from the tarball. > I didn't have any luck moving my old ~/.eclipse in place of my new ~/.eclipse :(...are these the steps you took?: a) emerge =dev-util/eclipse-3.5.1 b) move ~/.eclipse ~/.eclipse.bak c) eclipse-3.5 (failed to launch) d) rm -rf ~/.eclipse e) move ~/.eclipse.bak ~/.eclipse f) eclipse-3.5 (launches successfully)
> I didn't have any luck moving my old ~/.eclipse in place of my new ~/.eclipse > :(...are these the steps you took?: Pretty much, though I also did the same to my ~/Workspace the first time, but it didn't seem to matter. I am tarring my ~/.eclipse now and shooting it over to my other (non-working) computer and I'll report on whether or not I was able to get it to run there.
Yep, copying my ~/.eclipse from the working computer to the new computer worked. I don't really understand what the contents of that directory are, though, so I don't have the slightest idea what the relationship is.
(In reply to comment #113) > Yep, copying my ~/.eclipse from the working computer to the new computer > worked. I don't really understand what the contents of that directory are, > though, so I don't have the slightest idea what the relationship is. > Hmmm...that does not work for me :(. Is there a chance you can attach your ~/.eclipse? Or email it to me personally?
Created attachment 209977 [details] eclipse-3.5.1-ebuilds.tar.bz2 I narrowed down the problem to the dependency unbundling step. Somehow it was no longer working correctly. I changed the ebuild so that it replaces the bundled JARs with symlinks to the system-installed JARs (a practice that Andrew Overholt of the Linux Tools project says "will work"), and now I am able to start Eclipse both with and without a pre-existing ~/.eclipse. Try out the new ebuild, attached.
(In reply to comment #115) > Created an attachment (id=209977) [details] > eclipse-3.5.1-ebuilds.tar.bz2 > > I narrowed down the problem to the dependency unbundling step. Somehow it was > no longer working correctly. I changed the ebuild so that it replaces the > bundled JARs with symlinks to the system-installed JARs (a practice that Andrew > Overholt of the Linux Tools project says "will work"), and now I am able to > start Eclipse both with and without a pre-existing ~/.eclipse. Try out the new > ebuild, attached. > Works great. Once again, Matt saves us all :) And I don't have to upload my 260MB ~/.eclipse
(In reply to comment #115) > Created an attachment (id=209977) [details] > eclipse-3.5.1-ebuilds.tar.bz2 > Hi Matt, could you please change the type of your last attachment from plain text (text/plain) to binary file (application/octect-stream) ? ;)
Okay, I don't know if this is a problem with the ebuild or something else, but plugins I install don't seem to work. For example I installed PDT from the Galileo update site, which went without any problems, but after restarting Eclipse, the PHP and PHP Debug perspectives are unavailable. The same thing happens with the Subclipse plugin. Anybody else experience this? * Searching for icedtea* ... [IP-] [ ~] dev-java/icedtea6-bin-1.6.1 (0) Still the same ~amd64 machine. Clean ~/.eclipse and workspace. No errors occur, and no log anywhere to indicate a problem.
(In reply to comment #118) > Okay, I don't know if this is a problem with the ebuild or something else, but > plugins I install don't seem to work. For example I installed PDT from the > Galileo update site, which went without any problems, but after restarting > Eclipse, the PHP and PHP Debug perspectives are unavailable. The same thing > happens with the Subclipse plugin. Anybody else experience this? I am also experiencing that, and I don't know why it's happening or when the problem began or if it resulted from my starting with a clean ~/.eclipse. I am in discussion with Andrew Overholt on the linuxtools-dev listserv.
Hi everybody, I emerged eclipse 3.5.1 with the new ebuild, but if I try and launch it, I get this: Failed to find executable '/usr/lib/eclipse-3.5/eclipse'
(In reply to comment #120) > Hi everybody, I emerged eclipse 3.5.1 with the new ebuild, but if I try and > launch it, I get this: > > Failed to find executable '/usr/lib/eclipse-3.5/eclipse' > Well, looking at the build log, I see these lines towards the end: >>> Install eclipse-sdk-3.5.1 into /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/image/ category dev-util install: cannot stat `/var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC3/build/eclipse-R3_5_1-fetched-src/installation/*': No such file or directory !!! doins: /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC3/build/eclipse-R3_5_1-fetched-src/installation/* does not exist chmod: cannot access `/var/tmp/portage/dev-util/eclipse-sdk-3.5.1/image//usr/lib64/eclipse-3.5/eclipse': No such file or directory rm: cannot remove `/var/tmp/portage/dev-util/eclipse-sdk-3.5.1/image//usr/lib64/eclipse-3.5/libcairo-swt.so': No such file or directory it looks like here is why the program doesn't launch.. Can anybody understand what's wrong here (or should I report more information)? Thanks!
(In reply to comment #120) > Failed to find executable '/usr/lib/eclipse-3.5/eclipse' Probably the build failed. Unfortunately, Eclipse-build's build.sh doesn't return an error code if the ant built fails, so the ebuild has no way of knowing that the build failed and so ignorantly proceeds to attempt to install it.
(In reply to comment #100) > Updated tarball ... > removed swt-3.5.1 and icu4j-4.0.1.1, as they are now in the main Portage tree. Matt, as newer versions have entered the main Portage tree, do we need any swt at all in the tarball any more? I have tested removing it completely; I'm running fine on dev-java/swt-3.5.1 (3.5) so far.
(In reply to comment #123) > Matt, as newer versions have entered the main Portage tree, > do we need any swt at all in the tarball any more? > I have tested removing it completely; > I'm running fine on dev-java/swt-3.5.1 (3.5) so far. SWT 3.4.2 is still in the tarball because it is required by Eclipse SDK 3.4.2, which is also still in the tarball (because it is not in Portage and is the last version of Eclipse that didn't require Eclipse-build to build).
(In reply to comment #121) > Well, looking at the build log, I see these lines towards the end: > > >>> Install eclipse-sdk-3.5.1 into /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/image/ category dev-util > install: cannot stat > `/var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC3/build/eclipse-R3_5_1-fetched-src/installation/*': > No such file or directory > !!! doins: > /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC3/build/eclipse-R3_5_1-fetched-src/installation/* > does not exist > chmod: cannot access > `/var/tmp/portage/dev-util/eclipse-sdk-3.5.1/image//usr/lib64/eclipse-3.5/eclipse': > No such file or directory > rm: cannot remove > `/var/tmp/portage/dev-util/eclipse-sdk-3.5.1/image//usr/lib64/eclipse-3.5/libcairo-swt.so': > No such file or directory > Someone has forgotten his '|| die' in the end of those doins-lines....
> > Someone has forgotten his '|| die' in the end of those doins-lines.... > Yeah, in fact the ant build fails somewhere, but I have no clue where.. Does anyone else have problems building eclipse with the latest ebuild?
(In reply to comment #119) > I am also experiencing that, and I don't know why it's happening or when the > problem began or if it resulted from my starting with a clean ~/.eclipse. I am > in discussion with Andrew Overholt on the linuxtools-dev listserv. I think the problem began when you changed the dependency unbundling step as stated in comment 115. By using the symlink to an external jar the plugin is missing its plugin definitions because MANIFEST.MF is missing the Bundle properties and the plugin.properties is missing completely. The jar installed by normal java ebuilds are NORMAL jars and not OSGi bundles not to mention eclipse plugins. When you enable the "Classic Update" in Preferences/General/Capabilities and go to Help/Software Updates/Manage configurations have a look at the features installed in /usr/lib/eclipse-3.5. A lot of features are marked as not working. Select one use the task "Show properties" and look at the status. There you will see the all symlinked plugins can not be found in the eclipse installation. I plead to not use jar installed somewhere in the system but install all required plugins into the eclipse plugins directory to at least have an eclipse installation that is capable to install new features and to develop OSGi bundles (comment 49).
Created attachment 210177 [details] eclipse-3.5.1-ebuilds.tar.bz2 Okay, after a few more hours of digging through Eclipse, Equinox, and P2, I've finally produced a build that can start Eclipse with no pre-existing ~/.eclipse directory *and* can successfully install and start plugins. And the ebuild is less hackish than it was before; all-around win! Marcus Klein: The build no longer uses the (sparsely supported) "external" Bundle-ClassPath references trick, so you should be able to develop OSGi bundles again. Please report on your success or failure. (In reply to comment #125) > Someone has forgotten his '|| die' in the end of those doins-lines.... I added the missing '|| die's.
Due my developer work I have many JVMs installed in the machine. I usually interchange them using 'eselect java-vm', and I realized some plugins (like XQuery DLTK ones) don't work (NoClassDefFound exceptions) when I'm using IBM JDK 1.6.0.5. And other plugins dare complaining about the JDK version being lower than 1.4! So I guess some Eclipse plugins are not so well written, because they are checking what they shouldn't. Hope this helps. (In reply to comment #118) > Okay, I don't know if this is a problem with the ebuild or something else, but > plugins I install don't seem to work. For example I installed PDT from the > Galileo update site, which went without any problems, but after restarting > Eclipse, the PHP and PHP Debug perspectives are unavailable. The same thing > happens with the Subclipse plugin. Anybody else experience this? > > * Searching for icedtea* ... > [IP-] [ ~] dev-java/icedtea6-bin-1.6.1 (0) > > Still the same ~amd64 machine. Clean ~/.eclipse and workspace. No errors occur, > and no log anywhere to indicate a problem. >
build still fails for me, I attach the complete build log, hope somebody can figure out the problem..
(In reply to comment #130) > build still fails for me, I attach the complete build log, hope somebody can > figure out the problem.. > Never mind, the complete log weighs about 16MB.. Please tell me what information could be useful to track the building problem!
(In reply to comment #131) > Never mind, the complete log weighs about 16MB.. > Please tell me what information could be useful to track the building problem! What JDK are you using, and are you merging Eclipse using 'emerge' (which will pull in all required dependencies) or 'ebuild' (which won't)? How much system RAM do you have available? Which CPU architecture are you on? You could try compressing your build log using bzip2. Since the log contains highly repetitive text, bzip2 will do an outstanding job at shrinking it.
(In reply to comment #132) > (In reply to comment #131) > > Never mind, the complete log weighs about 16MB.. > > Please tell me what information could be useful to track the building problem! > > What JDK are you using, and are you merging Eclipse using 'emerge' (which will > pull in all required dependencies) or 'ebuild' (which won't)? How much system > RAM do you have available? Which CPU architecture are you on? > > You could try compressing your build log using bzip2. Since the log contains > highly repetitive text, bzip2 will do an outstanding job at shrinking it. > bzip2 did an amazing job, thanks for the hint.. I'm using emerge, the latest virtual machine from sun (sun-jdk-1.6.0.17) and I'm on a amd64 arch. Right now I'm trying a build with blackdown-jdk-1.4.2 set as the system vm to see if something different happens..
Created attachment 210206 [details] faled build log
(In reply to comment #134) > Created an attachment (id=210206) [details] > faled build log I don't think you compressed this correctly. $ bzip2 -cd build.log.bz2 bzip2: build.log.bz2 is not a bzip2 file. 'file' says it's a gzipped stream, but when I decompress it with gzip, I get a binary file with a bunch of null bytes in it. So I don't think the log text survived whatever you put it through.
Created attachment 210207 [details] faled build log (should be compressed ok now)
(In reply to comment #136) > Created an attachment (id=210207) [details] > faled build log (should be compressed ok now) Decompresses okay now, but it seems to be incomplete. Expands to only 822,315 bytes and does not seem to include the complete build log. Perhaps we should take this discussion over to private email so we don't aggravate all the people subscribed to this bug. Please email me your complete build log (compressed if possible).
Did you try IBM JDK 1.6.0.5? I'm using it in a x86_64 machine as system-vm, so it is the one taken on eclipse-sdk builds. (In reply to comment #132) > (In reply to comment #131) > > Never mind, the complete log weighs about 16MB.. > > Please tell me what information could be useful to track the building problem! > > What JDK are you using, and are you merging Eclipse using 'emerge' (which will > pull in all required dependencies) or 'ebuild' (which won't)? How much system > RAM do you have available? Which CPU architecture are you on? > > You could try compressing your build log using bzip2. Since the log contains > highly repetitive text, bzip2 will do an outstanding job at shrinking it. >
(In reply to comment #138) > Did you try IBM JDK 1.6.0.5? I'm using it in a x86_64 machine as system-vm, so > it is the one taken on eclipse-sdk builds. Mhh, dev-java/ibm-jdk-bin-1.6.0.5 is ~amd64 keyworded in portage, while version 1.6.0.6 is marked as stable.. I'm trying with both, I'll post what happens..
(In reply to comment #128) > Created an attachment (id=210177) [details] > eclipse-3.5.1-ebuilds.tar.bz2 > > Okay, after a few more hours of digging through Eclipse, Equinox, and P2, I've > finally produced a build that can start Eclipse with no pre-existing ~/.eclipse > directory *and* can successfully install and start plugins. And the ebuild is > less hackish than it was before; all-around win! > > Marcus Klein: The build no longer uses the (sparsely supported) "external" > Bundle-ClassPath references trick, so you should be able to develop OSGi > bundles again. Please report on your success or failure. > > (In reply to comment #125) > > Someone has forgotten his '|| die' in the end of those doins-lines.... > > I added the missing '|| die's. > (In reply to comment #128) > Created an attachment (id=210177) [details] > eclipse-3.5.1-ebuilds.tar.bz2 > > Okay, after a few more hours of digging through Eclipse, Equinox, and P2, I've > finally produced a build that can start Eclipse with no pre-existing ~/.eclipse > directory *and* can successfully install and start plugins. And the ebuild is > less hackish than it was before; all-around win! > > Marcus Klein: The build no longer uses the (sparsely supported) "external" > Bundle-ClassPath references trick, so you should be able to develop OSGi > bundles again. Please report on your success or failure. > > (In reply to comment #125) > > Someone has forgotten his '|| die' in the end of those doins-lines.... > > I added the missing '|| die's. > emerged successful on x86_64, will now try to get more and more plugins running cheers
Still no luck here, even with ibm virtual machine.. I think these are the relevant lines in the build log: [java] [javac] [reading org/eclipse/jface/text/templates/DocumentTemplateContext.class] [java] [java] BUILD FAILED [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/bootstrap/plugins/org.eclipse.pde.build/scripts/build.xml:36: The following error occurred while executing this line: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/bootstrap/plugins/org.eclipse.pde.build/scripts/build.xml:105: The following error occurred while executing this line: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/build/eclipse-R3_5_1-fetched-src/buildConfigs/eclipse-build-config/customTargets.xml:18: The following error occurred while executing this line: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/build/eclipse-R3_5_1-fetched-src/buildConfigs/eclipse-build-config/allElements.xml:16: The following error occurred while executing this line: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/bootstrap/plugins/org.eclipse.pde.build_3.5.1.R35x_20090820/scripts/genericTargets.xml:114: The following error occurred while executing this line: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/bootstrap/plugins/org.eclipse.pde.build_3.5.1.R35x_20090820/scripts/genericTargets.xml:124: The following error occurred while executing this line: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/build/eclipse-R3_5_1-fetched-src/compile.eclipse-build-feature.xml:277: The following error occurred while executing this line: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/build/eclipse-R3_5_1-fetched-src/plugins/org.eclipse.jdt.ui/build.xml:392: The following error occurred while executing this line: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/build/eclipse-R3_5_1-fetched-src/plugins/org.eclipse.jdt.ui/build.xml:320: java.lang.reflect.InvocationTargetException [java]
(In reply to comment #141) > Still no luck here, even with ibm virtual machine.. > I think these are the relevant lines in the build log: That's not too helpful without the root cause of the InvocationTargetException, but my guess would be that you ran out of memory. Building Eclipse requires an enormous amount of memory. I still don't know why the ebuild works for some people and throws OutOfMemoryErrors for others.
> That's not too helpful without the root cause of the InvocationTargetException, > but my guess would be that you ran out of memory. Building Eclipse requires an > enormous amount of memory. I still don't know why the ebuild works for some > people and throws OutOfMemoryErrors for others. > Mhh, root exception.. Do you mean the following lines? [java] Root exception: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/bootstrap/plugins/org.eclipse.pde.build/scripts/build.xml:36: The following error occurred while executing this line: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/bootstrap/plugins/org.eclipse.pde.build/scripts/build.xml:105: The following error occurred while executing this line: [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/build/eclipse-R3_5_1-fetched-src/buildConfigs/eclipse-build-config/customTargets.xml:18: The following error occurred w$ [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/build/eclipse-R3_5_1-fetched-src/buildConfigs/eclipse-build-config/allElements.xml:16: The following error occurred whi$ [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/bootstrap/plugins/org.eclipse.pde.build_3.5.1.R35x_20090820/scripts/genericTargets.xml:114: The following error occurre$ [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/bootstrap/plugins/org.eclipse.pde.build_3.5.1.R35x_20090820/scripts/genericTargets.xml:124: The following error occurre$ [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/build/eclipse-R3_5_1-fetched-src/compile.eclipse-build-feature.xml:277: The following error occurred while executing th$ [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/build/eclipse-R3_5_1-fetched-src/plugins/org.eclipse.jdt.ui/build.xml:392: The following error occurred while executing$ [java] /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/build/eclipse-R3_5_1-fetched-src/plugins/org.eclipse.jdt.ui/build.xml:320: java.lang.reflect.InvocationTargetException
(In reply to comment #128) > Created an attachment (id=210177) [details] > eclipse-3.5.1-ebuilds.tar.bz2 > Hi all, I tried that ebuild and now I get: [symlink] java.io.FileNotFoundException: No such symlink: bootstrap/plugins/org.eclipse.osgi_3.5.0.jar And then a chain of 19 nested "java.lang.reflect.InvocationTargetException" I do not really understand this, because it is there: # ls -lah /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/bootstrap/plugins/org.eclipse.osgi_3.5.0.jar lrwxrwxrwx 1 portage portage 20 17. Nov 16:36 /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/bootstrap/plugins/org.eclipse.osgi_3.5.0.jar -> org.eclipse.osgi.jar # ls -lah /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/bootstrap/plugins/org.eclipse.osgi.jar -rw-r--r-- 1 portage portage 1,1M 17. Nov 16:36 /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/bootstrap/plugins/org.eclipse.osgi.jar
(In reply to comment #128) > Okay, after a few more hours of digging through Eclipse, Equinox, and P2, I've > finally produced a build that can start Eclipse with no pre-existing ~/.eclipse > directory *and* can successfully install and start plugins. And the ebuild is > less hackish than it was before; all-around win! And the eclipse installation itself has no problems anymore with missing bundles/plugins. > Marcus Klein: The build no longer uses the (sparsely supported) "external" > Bundle-ClassPath references trick, so you should be able to develop OSGi > bundles again. Please report on your success or failure. Success! Great work! Thank you very much!
The ebuild works great on my amd64. The only thing is that I get a lengthy QA message during install about dependencies which are not specified but instead pulled in indirectly. I'm attaching it. Otherwise everything works like a charm. Thank you guys!
Created attachment 210540 [details] Warnings about unspecified dependencies and misuse of --build-only
(In reply to comment #146) > The ebuild works great on my amd64. The only thing is that I get a lengthy QA > message during install about dependencies which are not specified but instead > pulled in indirectly. I'm attaching it. Otherwise everything works like a > charm. Thank you guys! I don't understand why you would get these messages. All of the packages reported in your attachment *are* specified in the DEPEND variable of the Eclipse ebuild. Did you modify the ebuild from what is in the latest tarball attached to this bug report?
It looks the ebuild works for most of whom try to emerge eclipse with it.. It still doesn't work for me though.. Is anybody else getting this exception? /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/build/eclipse-R3_5_1-fetched-src/plugins/org.eclipse.jdt.ui/build.xml:320:java.lang.reflect.InvocationTargetException
How about to put the ebuilds keyworded/masked in the main portage tree (or java-overlay, at least)? When it would happen?
(In reply to comment #149) > It looks the ebuild works for most of whom try to emerge eclipse with it.. > It still doesn't work for me though.. > Is anybody else getting this exception? > > /var/tmp/portage/dev-util/eclipse-sdk-3.5.1/work/eclipse-build-0_4_RC5/build/eclipse-R3_5_1-fetched-src/plugins/org.eclipse.jdt.ui/build.xml:320:java.lang.reflect.InvocationTargetException > Invocation target exception is rarely a root cause of exception. Cold you check your build log again for the root cause of the root causes of exception, try to grep it forsome OutOfMemoryError 's .
> Invocation target exception is rarely a root cause of exception. Cold you check > your build log again for the root cause of the root causes of exception, try to > grep it forsome OutOfMemoryError 's . You were right, I found this: [java] Caused by: java.lang.OutOfMemoryError: Java heap space Sorry for not noticing this before and polluting the thread.. My system is an amd64 laptop with 2GB ram and >2GB swap, I didn't think the vm could run short of memory.. I'll try to compile minimizing the system's memory usage.. Are there other tricks to try to avoid the exception? Thanks!
Hi again. I know from previous versions that nearly no plugin was integrated in the eclipse emerged by the ebuild. In the eclipse of the current ebuild (eclipse-3.5.1-ebuilds.tar.bz2 2009-11-13 22:01) at least the "Eclipse CVS Client" and the "Eclipse Java Development Tools" plugins are integrated (more?). Are they necessary in the basic installation? I get an error if i try to "re-install" the plugins (with the different newer?? version on the update site) and the symbol in front of the plugins is a cycle, different from all others.
(In reply to comment #153) > I know from previous versions that nearly no plugin was integrated in the > eclipse emerged by the ebuild. > In the eclipse of the current ebuild (eclipse-3.5.1-ebuilds.tar.bz2 2009-11-13 > 22:01) at least the "Eclipse CVS Client" and the "Eclipse Java Development > Tools" plugins are integrated (more?). Are they necessary in the basic > installation? The ebuild builds the "Eclipse SDK" package, which includes the CVS client and the JDT. (If you download the "classic" Eclipse SDK binary package from the Eclipse site, you get these plugins.) > I get an error if i try to "re-install" the plugins (with the different newer?? > version on the update site) and the symbol in front of the plugins is a cycle, > different from all others. Could you post your error?
(In reply to comment #154) > > Could you post your error? > ok... it is the same version, just the "random" string at the end is different, also the deps. only if a newer version is available and the error still appears i would consider this as a problem. This is from the update manager for JDT: ---------- Your original request has been modified. "Eclipse Java Development Tools" is already installed, so an update will be performed instead. Cannot complete the install because of a conflicting dependency. Software being installed: Eclipse Java Development Tools 3.5.1.r351_v20090810-0600-7r88FEoFI0WTo6Az-1qFRHm37ChJ (org.eclipse.jdt.feature.group 3.5.1.r351_v20090810-0600-7r88FEoFI0WTo6Az-1qFRHm37ChJ) Software currently installed: Eclipse SDK 3.5.1.M20090917-0800 (org.eclipse.sdk.ide 3.5.1.M20090917-0800) Only one of the following can be installed at once: org.eclipse.jdt_root 3.5.1.r351_v20090810-0600-7r88FEoFI0WTo6Az-1qFRHm37ChJ org.eclipse.jdt_root 3.5.1.r351_v20090810-0600-7k81FEnFFCKNhb4_sQDHFj27CfJL Cannot satisfy dependency: From: Eclipse Java Development Tools 3.5.1.r351_v20090810-0600-7k81FEnFFCKNhb4_sQDHFj27CfJL (org.eclipse.jdt.feature.group 3.5.1.r351_v20090810-0600-7k81FEnFFCKNhb4_sQDHFj27CfJL) To: org.eclipse.jdt_root [3.5.1.r351_v20090810-0600-7k81FEnFFCKNhb4_sQDHFj27CfJL] Cannot satisfy dependency: From: Eclipse Java Development Tools 3.5.1.r351_v20090810-0600-7r88FEoFI0WTo6Az-1qFRHm37ChJ (org.eclipse.jdt.feature.group 3.5.1.r351_v20090810-0600-7r88FEoFI0WTo6Az-1qFRHm37ChJ) To: org.eclipse.jdt_root [3.5.1.r351_v20090810-0600-7r88FEoFI0WTo6Az-1qFRHm37ChJ] Cannot satisfy dependency: From: Eclipse Project SDK 3.5.1.R35x_v20090811-7F7L8e8DXu1wk3GlfuY-ppX9XcGHXvdGdODTz019m2TlD (org.eclipse.sdk.feature.group 3.5.1.R35x_v20090811-7F7L8e8DXu1wk3GlfuY-ppX9XcGHXvdGdODTz019m2TlD) To: org.eclipse.jdt.feature.group [3.5.1.r351_v20090810-0600-7k81FEnFFCKNhb4_sQDHFj27CfJL] Cannot satisfy dependency: From: Eclipse SDK 3.5.1.M20090917-0800 (org.eclipse.sdk.ide 3.5.1.M20090917-0800) To: org.eclipse.sdk.feature.group [3.5.1.R35x_v20090811-7F7L8e8DXu1wk3GlfuY-ppX9XcGHXvdGdODTz019m2TlD]
(In reply to comment #155) > ok... it is the same version, just the "random" string at the end is different, > also the deps. only if a newer version is available and the error still appears > i would consider this as a problem. I think this is to be expected. You can't have two different copies of the same version installed at the same time. As for upgrades, theoretically, you should not be upgrading the core Eclipse SDK plugins using the Update Manager; you should upgrade using Portage. That said, upgrading using Update Manager *should* work, although I'm not sure what would happen if you then upgraded using Portage; you might run into this same error coming from the other direction.
(In reply to comment #156) > (In reply to comment #155) > > ok... it is the same version, just the "random" string at the end is different, > > also the deps. only if a newer version is available and the error still appears > > i would consider this as a problem. > > I think this is to be expected. You can't have two different copies of the > same version installed at the same time. As for upgrades, theoretically, you > should not be upgrading the core Eclipse SDK plugins using the Update Manager; > you should upgrade using Portage. That said, upgrading using Update Manager > *should* work, although I'm not sure what would happen if you then upgraded > using Portage; you might run into this same error coming from the other > direction. > Just wanted to let you know...just used the latest upgrade to install 3.5.1...worked perfectly.
> Sorry for not noticing this before and polluting the thread.. > My system is an amd64 laptop with 2GB ram and >2GB swap, I didn't think the vm > could run short of memory.. > I'll try to compile minimizing the system's memory usage.. > Are there other tricks to try to avoid the exception? > Thanks! > I Tried to emerge from plain vga console with no X or other memory hungry things running, I'm still getting OutOfMemory exceptions due to lack of heap space.. I'd like to know how much memory is needed, so I ask: How much ram do the ones who emerged succesfully have?
(In reply to comment #158) > I Tried to emerge from plain vga console with no X or other memory hungry > things running, I'm still getting OutOfMemory exceptions due to lack of heap > space.. > I'd like to know how much memory is needed, so I ask: > How much ram do the ones who emerged succesfully have? > I suppose that much less than 2GB is needed to compile eclipse. This sounds to me like a problem of setting -Xms and -Xmx parameters for java vm. Don't know whether this is configured in the ebuild?!
> How much ram do the ones who emerged succesfully have? > Machine 1: 8GB Physical, 4GB VMware virtual, 12GiB swap. Machine 2: 4GB Physical, 2GB VMware virtual, 2GiB swap. Both compile fine > I suppose that much less than 2GB is needed to compile eclipse. I would be inclined to agree
> I would be inclined to agree > I agree too, still it doesn't work! this is how Xmx is set in the ebuild by Matt Whitlock: JAVA_HOME=$(java-config --jdk-home) ANT_OPTS='-Xmx512M' ./build.sh || die Any ideas?
Created attachment 210774 [details, diff] Fix build on x86 and add gnome use flag On x86 eclipse-build-0_4_RC5 builds libgnomeproxy by default. As what i can tell this requires at least gconf as dependency. The attached patch adds a "gnome" use flag which, if not set, removes the entries with respect to libgnomeproxy from the build.xml file.
Created attachment 210776 [details, diff] eclipse-sdk/files/3.5/build.xml.patch The actual patch needed by the modified ebuild for removing the libgnomeproxy entries from build.xml.
Downloaded 'eclipse-3.5.1-ebuilds.tar.bz2' and then emerged =dev-util/eclipse-3.5 and everything was emerged nicely and eclipse seems to work again. During emerge, I did happen to get a single error/warning though, and I'm not really sure what it is. * Messages for package dev-util/eclipse-sdk-3.5: * Don't have at least 3072MBytes disk space at ${T} * Bad things may happen! You may abort the build by pressing ctrl+c in * the next 15 seconds. * >>> Auto-cleaning packages... >>> No outdated packages were found on your system. Tried to locate ${T} from the ebuild -file, but couldn't find what it was. Portage's temp dir or /usr are my best guesses.
(In reply to comment #164) > Downloaded 'eclipse-3.5.1-ebuilds.tar.bz2' and then emerged > =dev-util/eclipse-3.5 and everything was emerged nicely and eclipse seems to > work again. > > During emerge, I did happen to get a single error/warning though, and I'm not > really sure what it is. > > * Messages for package dev-util/eclipse-sdk-3.5: > > * Don't have at least 3072MBytes disk space at ${T} > * Bad things may happen! You may abort the build by pressing ctrl+c in > * the next 15 seconds. > * > >>> Auto-cleaning packages... > > >>> No outdated packages were found on your system. > > Tried to locate ${T} from the ebuild -file, but couldn't find what it was. > Portage's temp dir or /usr are my best guesses. > usually /var/tmp/portage is used to store uncompressed source file and to compile packages, so that ${T} should be /var/tmp/portage unless you have changed that.
(In reply to comment #164) > * Don't have at least 3072MBytes disk space at ${T} > * Bad things may happen! You may abort the build by pressing ctrl+c in > * the next 15 seconds. This might happen if you're using the "TMPDIR on tmpfs" trick (http://en.gentoo-wiki.com/wiki/Portage_TMPDIR_on_tmpfs) with a tmpfs size smaller than 3GB -- I had the same message because of this. You can either override it with a PORTAGE_TMPDIR override on the emerge command line pointing to a directory that is not monitored by autofs, or stop autofs and mkdir -p ${PORTAGE_TMPDIR}. When I did that, the warning went away. It's just confusing that the ${T} doesn't get expanded in the warning message.
Created attachment 211654 [details] eclipse-3.5.1-ebuilds.tar.bz2 * Updated to Eclipse-build 0.4.0 final release * Reduced disk space checkreq when USE="-doc -source" * Skip building libgnomeproxy on x86 when USE="-gnome" * Depend on gnome-base/gconf when USE="gnome x86"
(In reply to comment #167) > Created an attachment (id=211654) [details] > eclipse-3.5.1-ebuilds.tar.bz2 > > * Updated to Eclipse-build 0.4.0 final release > * Reduced disk space checkreq when USE="-doc -source" > * Skip building libgnomeproxy on x86 when USE="-gnome" > * Depend on gnome-base/gconf when USE="gnome x86" > This has fixed all focus issues I was having earlier. Everything seems to be working very nicely. Will be seeing this in portage soon?
Builds/runs fine... I wanted the Android dev tools, so added that into 'Available Software Sites', connection test worked. I go to added the ADT and get this: Cannot complete the install because one or more required items could not be found. Software being installed: Android Development Tools 0.9.4.v200910220141-17704 (com.android.ide.eclipse.adt.feature.group 0.9.4.v200910220141-17704) Missing requirement: Android Development Tools 0.9.4.v200910220141-17704 (com.android.ide.eclipse.adt.feature.group 0.9.4.v200910220141-17704) requires 'org.eclipse.wst.xml.ui 0.0.0' but it could not be found What (and how do I get it) additional information can I provide?
Ok, so I added the DDMS separately and successfully. I go to add ADT and get a variation of the same error as previous: Cannot complete the install because one or more required items could not be found. Software being installed: Android Development Tools 0.9.4.v200910220141-17704 (com.android.ide.eclipse.adt.feature.group 0.9.4.v200910220141-17704) Missing requirement: Android Development Tools 0.9.4.v200910220141-17704 (com.android.ide.eclipse.adt.feature.group 0.9.4.v200910220141-17704) requires 'org.eclipse.gef 0.0.0' but it could not be found
Ok, so ignore the Eclipse newb. I found the plugins and the byzantine craziness of installing them. Would anyone be willing to tell me if there's a method of auto-satisfying dependencies for plugins?
Ok guys. eclipse-sdk is now in the java-experimental overlay. I want to start figuring out what we need to do to get this into the main tree. Ive already suggested a few minor things to Matt but i'm sure there is more.
(In reply to comment #172) > Ok guys. eclipse-sdk is now in the java-experimental overlay. I want to start Something's wrong with the source tarball: >>> Downloading 'http://download.eclipse.org/technology/linuxtools/eclipse-build/eclipse-R3_5_1-fetched-src.tar.bz2' ... 2009-12-04 01:02:36 (53,9 KB/s) - «/usr/portage/distfiles/eclipse-R3_5_1-fetched-src.tar.bz2» saved [79061683/79061683] ('Filesize does not match recorded size', 79061683L, 86995935) !!! Fetched file: eclipse-R3_5_1-fetched-src.tar.bz2 VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 79061683 !!! Expected: 86995935
(In reply to comment #173) > Something's wrong with the source tarball: > > >>> Downloading 'http://download.eclipse.org/technology/linuxtools/eclipse-build/eclipse-R3_5_1-fetched-src.tar.bz2' > ... > 2009-12-04 01:02:36 (53,9 KB/s) - > «/usr/portage/distfiles/eclipse-R3_5_1-fetched-src.tar.bz2» saved > [79061683/79061683] > > ('Filesize does not match recorded size', 79061683L, 86995935) > !!! Fetched file: eclipse-R3_5_1-fetched-src.tar.bz2 VERIFY FAILED! > !!! Reason: Filesize does not match recorded size > !!! Got: 79061683 > !!! Expected: 86995935 Looks like Alistair committed the wrong hash to java-experimental. The Manifest file in my tarball has this: DIST eclipse-R3_5_1-fetched-src.tar.bz2 79061683 RMD160 ba04a7e9a9521f01c0c97d9f306e1fa3e5149dbb SHA1 d13b6362d007291483336bd8a8c98eb25fea9acc SHA256 3c93115e3031686dd26c94833cd21ce26244340408a435a3b9dcd29404309c60
> Looks like Alistair committed the wrong hash to java-experimental. Yeah sorry about that. not sure why the file sizes were different. maybe they replaced the file.
> > Developing of OSGi bundles is currently not possible, if one of the following > > bundles is used from the default Target Platform: > > org.apache.commons.codec > > org.apache.commons.httpclient > > org.apache.commons.logging ... > Yes, that is what the dependency unbundling step does. Look at the manifests, > and you will see a "Bundle-ClassPath" property that references the jars > installed on your system in /usr/share/commons-{codec,httpclient-3,logging}/. > > As for why your project's class path is not picking up the referenced > "external" jars, I couldn't tell you. Other plugins, like "Mylyn Task List (Required)", are not happy with org.apache.commons.{codec,httpclient,logging}: Plug-in "org.apache.commons.logging" version "1.0.4.v200904062259" referenced by this feature is missing. Plug-in "org.apache.commons.codec" version "1.3.0.v20080530-1600" referenced by this feature is missing. Plug-in "org.apache.commons.httpclient" version "3.1.0.v20080605-1935" referenced by this feature is missing. There's something really wrong with these three. I tried to keep them bundled, but that didn't help. A dumb way to reproduce: 1. Install "Mylyn Task List (Required)" from http://download.eclipse.org/releases/galileo 2. Enable the "Classic Update" capability. 3. See Help -> Software Updates -> Manage Configuration... -> Eclipse SDL -> ... -> "Mylyn Task List (Required)" -> Properties -> Status
(In reply to comment #176) > Other plugins, like "Mylyn Task List (Required)", are not happy with > org.apache.commons.{codec,httpclient,logging}: > > A dumb way to reproduce: > 1. Install "Mylyn Task List (Required)" from > http://download.eclipse.org/releases/galileo > 2. Enable the "Classic Update" capability. > 3. See Help -> Software Updates -> Manage Configuration... -> Eclipse SDL -> > ... -> "Mylyn Task List (Required)" -> Properties -> Status You probably shouldn't use Classic Update since the Eclipse install is managed by P2. I have Mylyn installed (from http://download.eclipse.org/tools/mylyn/update/e3.4) with no problems.
> You probably shouldn't use Classic Update since the Eclipse install is managed > by P2. I have Mylyn installed (from > http://download.eclipse.org/tools/mylyn/update/e3.4) with no problems. Actually, Mylyn works for me too. Sorry for being implicit about that. What I'm trying to figure out is where those problems with org.apache.commons did come from. I don't use Classic Update to install anything, I only use its Manage Configuration interface to check status of the plugins. Each one of them installed from P2 repos. I already tried http://download.eclipse.org/tools/mylyn/update/e3.4, several times with the same sad results. Could you, please, ensure that the plugins are all reported to be fine if you enable Classic Updates and check their status from the Manage Configuration interface? It seems like a minor bug, but still it caused troubles with OSGi for Marcus, and there's only a workaround available as the solution for now.
(In reply to comment #178) > Actually, Mylyn works for me too. Sorry for being implicit about that. What I'm > trying to figure out is where those problems with org.apache.commons did come > from. > > I don't use Classic Update to install anything, I only use its Manage > Configuration interface to check status of the plugins. I'm not sure if the "Classic Update" is fully compatible with P2. I wouldn't trust it to fully know what's going on. > Could you, please, ensure that the plugins are all reported to be fine if you > enable Classic Updates and check their status from the Manage Configuration > interface? If I enable Classic Update and open its Configuration Manager, I also see that the Mylyn Task List plugin is reported to be missing some dependencies. However, I am able to use Mylyn just fine, so I'm inclined to believe we're merely seeing a failure of the old (obsoleted) Configuration Manager. > It seems like a minor bug, but still it caused troubles with OSGi for Marcus, > and there's only a workaround available as the solution for now. Marcus said in comment #145 that it works for him now.
(In reply to comment #178) > > It seems like a minor bug, but still it caused troubles with OSGi for Marcus, > and there's only a workaround available as the solution for now. > Developing OSGi bundles works fine now since referencing external libraries has been removed from this eclipse build. I use Mylyn, too. And its bundles show up fine in the Configuration Manager of the Classic Update since not referencing external libraries anymore. Pavel, I am sure that you are not using the latest ebuild from this bug.
Pavel, please check one of your eclipse bundles with the following command: jar tf /usr/lib/eclipse-3.5/plugins/javax.servlet_2.5.0.v200806031605.jar And report your results.
> Pavel, please check one of your eclipse bundles with the following command: > jar tf /usr/lib/eclipse-3.5/plugins/javax.servlet_2.5.0.v200806031605.jar > And report your results. There's no javax.servlet_2.5.0.v200806031605.jar, but instead: $ jar tf /usr/lib/eclipse-3.5/plugins/javax.servlet_2.5.0.v200806031605/servlet-api.jar META-INF/ META-INF/MANIFEST.MF javax/ javax/servlet/ javax/servlet/http/ javax/servlet/jsp/ javax/servlet/resources/ javax/servlet/Filter.class javax/servlet/FilterChain.class javax/servlet/FilterConfig.class javax/servlet/GenericServlet.class javax/servlet/LocalStrings.properties javax/servlet/RequestDispatcher.class javax/servlet/Servlet.class javax/servlet/ServletConfig.class javax/servlet/ServletContext.class javax/servlet/ServletContextAttributeEvent.class javax/servlet/ServletContextAttributeListener.class javax/servlet/ServletContextEvent.class javax/servlet/ServletContextListener.class javax/servlet/ServletException.class javax/servlet/ServletInputStream.class javax/servlet/ServletOutputStream.class javax/servlet/ServletRequest.class javax/servlet/ServletRequestAttributeEvent.class javax/servlet/ServletRequestAttributeListener.class javax/servlet/ServletRequestEvent.class javax/servlet/ServletRequestListener.class javax/servlet/ServletRequestWrapper.class javax/servlet/ServletResponse.class javax/servlet/ServletResponseWrapper.class javax/servlet/SingleThreadModel.class javax/servlet/UnavailableException.class javax/servlet/http/Cookie.class javax/servlet/http/HttpServlet.class javax/servlet/http/HttpServletRequest.class javax/servlet/http/HttpServletRequestWrapper.class javax/servlet/http/HttpServletResponse.class javax/servlet/http/HttpServletResponseWrapper.class javax/servlet/http/HttpSession.class javax/servlet/http/HttpSessionActivationListener.class javax/servlet/http/HttpSessionAttributeListener.class javax/servlet/http/HttpSessionBindingEvent.class javax/servlet/http/HttpSessionBindingListener.class javax/servlet/http/HttpSessionContext.class javax/servlet/http/HttpSessionEvent.class javax/servlet/http/HttpSessionListener.class javax/servlet/http/HttpUtils.class javax/servlet/http/LocalStrings.properties javax/servlet/http/NoBodyOutputStream.class javax/servlet/http/NoBodyResponse.class javax/servlet/resources/XMLSchema.dtd javax/servlet/resources/datatypes.dtd javax/servlet/resources/j2ee_1_4.xsd javax/servlet/resources/j2ee_web_services_1_1.xsd javax/servlet/resources/j2ee_web_services_client_1_1.xsd javax/servlet/resources/web-app_2_2.dtd javax/servlet/resources/web-app_2_3.dtd javax/servlet/resources/web-app_2_4.xsd javax/servlet/resources/web-app_2_5.xsd javax/servlet/resources/xml.xsd > However, I am able to use Mylyn just fine, so I'm inclined to believe we're > merely seeing a failure of the old (obsoleted) Configuration Manager. Yes, it seems so... Thanks for checking this out.
Just committed to tree so closing this. Will be hitting trees within the next couple of hours. Please open new bugs for an issues. There is a eclipse-3.5 metabug that you can block. Thank you to all of you.
I still can't emerge eclipse, even with the ebuild 3.5.1 in the portage tree. I opened a new bug: https://bugs.gentoo.org/show_bug.cgi?id=297057 (In reply to comment #183) > Just committed to tree so closing this. Will be hitting trees within the next > couple of hours. > > Please open new bugs for an issues. There is a eclipse-3.5 metabug that you > can block. > > Thank you to all of you. >
(In reply to comment #184) > I still can't emerge eclipse, even with the ebuild 3.5.1 in the portage tree. > I opened a new bug: https://bugs.gentoo.org/show_bug.cgi?id=297057 > I have succeeded at last. Something was wrong with some java package, I have absolutely no idea what. But the following did the trick and eclipse-sdk-1.5.1 emerged at last: # emerge --unmerge eclipse-sdk `eix -I --only-names -C *java*` ; autounmask dev-util/eclipse-sdk-1.5.1 ; emerge eclipse-sdk Only thing I am wondering is, that it emerged sun-sdk-1.5, but icedtea6-bin instead of sun-jdk-1.6 although I have the appropriate license entries. But that's in order as long as eclipse is working properly now.
Fine, the thing (3.5.1 in main tree) installs and runs. HOWEVER, somehow the features.xml is crippled during install (or whatever, i'm an ecclipse n0ob) and the main update sites are not added! thus i went through liberties of inserting one plugin update site after another *manually* just to not get PDT running in the end. Adding this two URLs http://download.eclipse.org/eclipse/updates/3.5 http://download.eclipse.org/releases/galileo manually after resetting my .eclipse dir worked like a charm, but it took me two hours to find out.. Can others reproduce this? It's phenomenal PITA especially for eclipse first-timers..
(In reply to comment #186) > the main update sites are not added! This is a known upstream bug with which the Eclipse developers seem relatively unconcerned. https://bugs.eclipse.org/bugs/show_bug.cgi?id=249133
Lets leave this open. I will attempt to add some einfo lines to the ebuild explaining what is happening.
Bugger sorry I though this was a different defect. Please do not add new issues to this defect.
