From owner-freebsd-eclipse@FreeBSD.ORG Mon Aug 29 18:07:43 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92A1716A41F for ; Mon, 29 Aug 2005 18:07:43 +0000 (GMT) (envelope-from lioux@FreeBSD.org) Received: from vette.gigo.com (vette.gigo.com [216.218.228.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54D1143D46 for ; Mon, 29 Aug 2005 18:07:43 +0000 (GMT) (envelope-from lioux@FreeBSD.org) Received: from 201.24.49.97 (unknown [201.24.49.97]) by vette.gigo.com (Postfix) with ESMTP id 59C83546A for ; Mon, 29 Aug 2005 11:07:41 -0700 (PDT) Received: (qmail 68856 invoked by uid 1001); 29 Aug 2005 18:07:04 -0000 Message-ID: <20050829180704.68762.qmail@exxodus.fedaykin.here> Date: Mon, 29 Aug 2005 15:06:42 -0300 From: Mario Sergio Fujikawa Ferreira To: freebsd-eclipse@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u3/rZRmxL6MmkK24" Content-Disposition: inline User-Agent: Mutt/1.5.9i Subject: Eclipse 3.1: no swt-pi-gtk-3138 X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 18:07:43 -0000 --u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I maintain 2 ports (net/mldonkey-sancho and net/azureus) which depend on eclipse and have been broken ever since its update. I've just updated azureus yesterday and got it building just fine but I get the following error message. $ ./azureus Exception in thread "main" java.lang.UnsatisfiedLinkError: no swt-pi-gtk-31= 38 in java.library.path at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1682) at java.lang.Runtime.loadLibrary0(Runtime.java:822) at java.lang.System.loadLibrary(System.java:992) at org.eclipse.swt.internal.Library.loadLibrary(Library.java:123) at org.eclipse.swt.internal.gtk.OS.(OS.java:19) at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:63) at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:54) at org.eclipse.swt.widgets.Display.(Display.java:122) at org.gudy.azureus2.ui.swt.mainwindow.SWTThread.(Unknown Sou= rce) at org.gudy.azureus2.ui.swt.mainwindow.SWTThread.createInstance(Unk= nown Source) at org.gudy.azureus2.ui.swt.mainwindow.Initializer.(Unknown S= ource) at org.gudy.azureus2.ui.swt.Main.(Unknown Source) at org.gudy.azureus2.ui.swt.Main.main(Unknown Source) which should be fixed by using a proper -Djava.library.path=3Dsomewhere statemente. However, I am not able find the proper location to point to. Taking a look at https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D89315 I find out that there are SWT PI patches there which are not included with our java/eclipse port. Are there plans to integrate those patches now that the ports freeze is over? Regards, --=20 Mario S F Ferreira - DF - Brazil - "I guess this is a signature." feature, n: a documented bug | bug, n: an undocumented feature --u3/rZRmxL6MmkK24 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDE07IrxEiaFLzGQwRAlUSAJwO94R7n1I6lXXBYgSoBiiywc9HJACeNUPM 1R2m7/hnqKsGoI9OUTmHySk= =PRcg -----END PGP SIGNATURE----- --u3/rZRmxL6MmkK24-- From owner-freebsd-eclipse@FreeBSD.ORG Mon Aug 29 20:03:33 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C900816A41F for ; Mon, 29 Aug 2005 20:03:33 +0000 (GMT) (envelope-from sepotvin@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76A0E43D48 for ; Mon, 29 Aug 2005 20:03:33 +0000 (GMT) (envelope-from sepotvin@videotron.ca) Received: from [10.0.0.147] ([67.70.237.74]) by VL-MO-MR007.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTPA id <0IM000JNW2CWMG@VL-MO-MR007.ip.videotron.ca> for freebsd-eclipse@freebsd.org; Mon, 29 Aug 2005 16:02:57 -0400 (EDT) Date: Mon, 29 Aug 2005 16:02:56 -0400 From: "Stephane E. Potvin" To: freebsd-eclipse@freebsd.org Message-id: <431369F0.5060909@videotron.ca> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_NdwDhoLG9jXr/b97uCBXGQ)" X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050826) X-Enigmail-Version: 0.92.0.0 Subject: [Patch] Fix eclipse build after latest firefox update X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 20:03:33 -0000 This is a multi-part message in MIME format. --Boundary_(ID_NdwDhoLG9jXr/b97uCBXGQ) Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I had to apply the following patch to make eclipse build after the latest firefox update (the one who changed firefox to use the system nspr library). Steph -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDE2nvmdOXtTCX/nsRAgT8AJ971FNXEZ0zd3nvfqpJTs5m6I1r5wCfdLVP 8mHU0H+Dlt0M55cEFLh0xuA= =6bv3 -----END PGP SIGNATURE----- --Boundary_(ID_NdwDhoLG9jXr/b97uCBXGQ) Content-type: text/x-patch; name=eclipse.patch; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Content-disposition: inline; filename=eclipse.patch Index: files/manualpatch-plugins-swt-gtk-build.sh =================================================================== RCS file: /home/FreeBSD/ncvs/ports/java/eclipse/files/manualpatch-plugins-swt-gtk-build.sh,v retrieving revision 1.1 diff -u -r1.1 manualpatch-plugins-swt-gtk-build.sh --- files/manualpatch-plugins-swt-gtk-build.sh 31 Jul 2005 05:26:15 -0000 1.1 +++ files/manualpatch-plugins-swt-gtk-build.sh 29 Aug 2005 19:33:30 -0000 @@ -9,9 +9,9 @@ + LD=gcc + XTEST_LIB_PATH=$X11BASE/lib + GECKO_I=${X11BASE}/include/${BROWSER} -+ GECKO_INCLUDES="-I${GECKO_I} -I${GECKO_I}/nspr -I${GECKO_I}/xpcom -I${GECKO_I}/string -I${GECKO_I}/embed_base -I${GECKO_I}/embedstring" ++ GECKO_INCLUDES="-I${GECKO_I} -I${LOCALBASE}/include/nspr -I${GECKO_I}/xpcom -I${GECKO_I}/string -I${GECKO_I}/embed_base -I${GECKO_I}/embedstring" + GECKO_L=${X11BASE}/lib/${BROWSER} -+ GECKO_LIBS="-L${GECKO_L} -lxpcom -lnspr4 -lplds4 -lplc4 -lgtkembedmoz" ++ GECKO_LIBS="-L${GECKO_L} -lxpcom -L${LOCALBASE}/lib -lnspr4 -L${GECKO_L} -lplds4 -lplc4 -lgtkembedmoz" + case $MODEL in + "amd64") + AWT_LIB_PATH=$JAVA_HOME/jre/lib/amd64 --Boundary_(ID_NdwDhoLG9jXr/b97uCBXGQ)-- From owner-freebsd-eclipse@FreeBSD.ORG Mon Aug 29 20:09:50 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E2E916A41F; Mon, 29 Aug 2005 20:09:50 +0000 (GMT) (envelope-from sepotvin@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A41A43D45; Mon, 29 Aug 2005 20:09:50 +0000 (GMT) (envelope-from sepotvin@videotron.ca) Received: from [10.0.0.147] ([67.70.237.74]) by VL-MO-MR007.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTPA id <0IM0000VX2MXSO@VL-MO-MR007.ip.videotron.ca>; Mon, 29 Aug 2005 16:08:59 -0400 (EDT) Date: Mon, 29 Aug 2005 16:08:57 -0400 From: "Stephane E. Potvin" In-reply-to: <20050829180704.68762.qmail@exxodus.fedaykin.here> To: Mario Sergio Fujikawa Ferreira Message-id: <43136B59.7090508@videotron.ca> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050826) X-Enigmail-Version: 0.92.0.0 References: <20050829180704.68762.qmail@exxodus.fedaykin.here> Cc: freebsd-eclipse@freebsd.org Subject: Re: Eclipse 3.1: no swt-pi-gtk-3138 X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 20:09:50 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mario Sergio Fujikawa Ferreira wrote: > Hi, > > I maintain 2 ports (net/mldonkey-sancho and net/azureus) > which depend on eclipse and have been broken ever since its update. > > I've just updated azureus yesterday and got it building just > fine but I get the following error message. > > $ ./azureus > > Exception in thread "main" java.lang.UnsatisfiedLinkError: no swt-pi-gtk-3138 in java.library.path > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1682) > at java.lang.Runtime.loadLibrary0(Runtime.java:822) > at java.lang.System.loadLibrary(System.java:992) > at org.eclipse.swt.internal.Library.loadLibrary(Library.java:123) > at org.eclipse.swt.internal.gtk.OS.(OS.java:19) > at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:63) > at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:54) > at org.eclipse.swt.widgets.Display.(Display.java:122) > at org.gudy.azureus2.ui.swt.mainwindow.SWTThread.(Unknown Source) > at org.gudy.azureus2.ui.swt.mainwindow.SWTThread.createInstance(Unknown Source) > at org.gudy.azureus2.ui.swt.mainwindow.Initializer.(Unknown Source) > at org.gudy.azureus2.ui.swt.Main.(Unknown Source) > at org.gudy.azureus2.ui.swt.Main.main(Unknown Source) > > which should be fixed by using a proper -Djava.library.path=somewhere > statemente. > > However, I am not able find the proper location to point to. > Taking a look at > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=89315 > > I find out that there are SWT PI patches there which are not included > with our java/eclipse port. > > Are there plans to integrate those patches now that the > ports freeze is over? > > Regards, > You can find the libraries in the org.eclipse.swt.gtk.freebsd.x86_3.1.0.jar file in eclipse's plugin directory. You'll have to extract them somewhere and add this path to your -Djava.library.path I have no idea why they are not extracted by default anymore. Regards, Steph -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDE2tZmdOXtTCX/nsRApm1AKDFlQ02wIcAhoElKQJt12DBJ8WtZQCeNTUr DPYeRL1czYLzu1hupTXHf7A= =zppd -----END PGP SIGNATURE----- From owner-freebsd-eclipse@FreeBSD.ORG Mon Aug 29 21:49:02 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0978116A41F; Mon, 29 Aug 2005 21:49:02 +0000 (GMT) (envelope-from past@ebs.gr) Received: from fly.ebs.gr (fly.ebs.gr [62.103.84.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 044BA43D49; Mon, 29 Aug 2005 21:49:00 +0000 (GMT) (envelope-from past@ebs.gr) Received: from ebs.gr (root@hal.ebs.gr [10.1.1.2]) by fly.ebs.gr (8.12.9p1/8.12.9) with ESMTP id j7TLmwID096721; Tue, 30 Aug 2005 00:48:58 +0300 (EEST) (envelope-from past@ebs.gr) Received: from [10.1.1.200] (pptp.ebs.gr [10.1.1.200]) by ebs.gr (8.13.3/8.12.11) with ESMTP id j7TLmwDl068662; Tue, 30 Aug 2005 00:48:59 +0300 (EEST) (envelope-from past@ebs.gr) Message-ID: <431382C3.3060205@ebs.gr> Date: Tue, 30 Aug 2005 00:48:51 +0300 From: Panagiotis Astithas Organization: EBS Ltd. User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050816) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Stephane E. Potvin" References: <20050829180704.68762.qmail@exxodus.fedaykin.here> <43136B59.7090508@videotron.ca> In-Reply-To: <43136B59.7090508@videotron.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-eclipse@freebsd.org, Mario Sergio Fujikawa Ferreira Subject: Re: Eclipse 3.1: no swt-pi-gtk-3138 X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 21:49:02 -0000 Stephane E. Potvin wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Mario Sergio Fujikawa Ferreira wrote: > >>Hi, >> >> I maintain 2 ports (net/mldonkey-sancho and net/azureus) >>which depend on eclipse and have been broken ever since its update. >> >> I've just updated azureus yesterday and got it building just >>fine but I get the following error message. >> >>$ ./azureus >> >>Exception in thread "main" java.lang.UnsatisfiedLinkError: no swt-pi-gtk-3138 in java.library.path >> at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1682) >> at java.lang.Runtime.loadLibrary0(Runtime.java:822) >> at java.lang.System.loadLibrary(System.java:992) >> at org.eclipse.swt.internal.Library.loadLibrary(Library.java:123) >> at org.eclipse.swt.internal.gtk.OS.(OS.java:19) >> at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:63) >> at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:54) >> at org.eclipse.swt.widgets.Display.(Display.java:122) >> at org.gudy.azureus2.ui.swt.mainwindow.SWTThread.(Unknown Source) >> at org.gudy.azureus2.ui.swt.mainwindow.SWTThread.createInstance(Unknown Source) >> at org.gudy.azureus2.ui.swt.mainwindow.Initializer.(Unknown Source) >> at org.gudy.azureus2.ui.swt.Main.(Unknown Source) >> at org.gudy.azureus2.ui.swt.Main.main(Unknown Source) >> >>which should be fixed by using a proper -Djava.library.path=somewhere >>statemente. >> >> However, I am not able find the proper location to point to. >>Taking a look at >> >>https://bugs.eclipse.org/bugs/show_bug.cgi?id=89315 >> >>I find out that there are SWT PI patches there which are not included >>with our java/eclipse port. No way, I sent those attachments from my /usr/ports/java/eclipse/files directory :-) >> Are there plans to integrate those patches now that the >>ports freeze is over? >> >> Regards, >> > > > You can find the libraries in the > org.eclipse.swt.gtk.freebsd.x86_3.1.0.jar file in eclipse's plugin > directory. You'll have to extract them somewhere and add this path to > your -Djava.library.path > > I have no idea why they are not extracted by default anymore. > > Regards, > > Steph Exactly, eclipse now uses a simplified plugin distribution, where everything is included in a single jar. I'll take a look into what needs to be done for azureus, etc. Another option is to finish my swt31 port and make swt-based apps depend on it. What would you prefer? Cheers, Panagiotis From owner-freebsd-eclipse@FreeBSD.ORG Mon Aug 29 22:07:01 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4142016A420; Mon, 29 Aug 2005 22:07:01 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from lakecmmtao05.coxmail.com (lakecmmtao05.coxmail.com [68.99.120.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03EBF43D49; Mon, 29 Aug 2005 22:06:59 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from dns1 ([64.58.171.82]) by lakecmmtao05.coxmail.com (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20050829220659.PVLT2425.lakecmmtao05.coxmail.com@dns1>; Mon, 29 Aug 2005 18:06:59 -0400 Received: from mail.eclipse.org ([206.191.52.52]) by lakecmmtai06.coxmail.com (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20050829190424.WPAE16499.lakecmmtai06.coxmail.com@mail.eclipse.org> for ; Mon, 29 Aug 2005 15:04:24 -0400 Received: by mail.eclipse.org (Postfix, from userid 30) id 2A149EF3C; Mon, 29 Aug 2005 15:04:17 -0400 (EDT) From: Vizion To: freebsd-eclipse@freebsd.org X-Bugzilla-Reason: Voter Message-Id: <200508291502.53259.vizion@vizion.occoxmail.com> Date: Mon, 29 Aug 2005 18:02:52 -0400 User-Agent: KMail/1.8 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-java@freebsd.org Subject: Fwd: [Bug 89315] Add build files for FreeBSD (x86 and AMD64) X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 22:07:01 -0000 As the freebsd-eclipse@freebsd.org mailing list is new I forwarded a copy of this to freebsd-java@freebsd.org. If anyone wishes to discuss (or any eclipse specific issues) this will they please do so on the freebsd-eclipse mailing list Thanks ---------- Forwarded Message ---------- Subject: [Bug 89315] Add build files for FreeBSD (x86 and AMD64) Date: Monday 29 August 2005 12:04 From: bugzilla-daemon@eclipse.org To: vizion@vizion.occoxmail.com https://bugs.eclipse.org/bugs/show_bug.cgi?id=89315 ------- Additional Comments From bbiggs@ca.ibm.com 2005-08-29 15:04 ------- I intend to apply the patches to the launcher and SWT, but I have one question. I've been worried about the use of "libgtk-x11-2.0.so.0" vs "libgtk-x11-2.0.so" on *BSD vs Linux. For shared libraries, the first number is the major version number, and an unversioned .so link is supposed to point at the current development version (it's what -l uses). We can't dlopen the .so on every platform because doesn't always exist. Under many Linux distributions, the .so symbolic link only exists in the -devel package. I have heard that the library version weirdness on FreeBSD is due to a libtool bug, and is fixed by an "ltverhack" script at some point, but I have not been able to verify this. Anyway, back to the point, is there a sane #ifdef I can protect this around, or should I just use the FREEBSD one you define in the makefile? ------- You are receiving this mail because: ------- You are a voter for the bug, or are watching someone who is. ------------------------------------------------------- -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. From owner-freebsd-eclipse@FreeBSD.ORG Mon Aug 29 22:07:50 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DB2E16A41F for ; Mon, 29 Aug 2005 22:07:50 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from lakecmmtao06.coxmail.com (lakecmmtao06.coxmail.com [68.99.120.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76C9243D45 for ; Mon, 29 Aug 2005 22:07:49 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from dns1 ([64.58.171.82]) by lakecmmtao06.coxmail.com (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20050829220748.PHDW24491.lakecmmtao06.coxmail.com@dns1>; Mon, 29 Aug 2005 18:07:48 -0400 From: Vizion To: freebsd-eclipse@freebsd.org Date: Mon, 29 Aug 2005 15:03:43 -0700 User-Agent: KMail/1.8 References: <431369F0.5060909@videotron.ca> In-Reply-To: <431369F0.5060909@videotron.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508291503.43866.vizion@vizion.occoxmail.com> Cc: Subject: Re: [Patch] Fix eclipse build after latest firefox update X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 22:07:50 -0000 On Monday 29 August 2005 13:02, the author Stephane E. Potvin contributed to the dialogue on- [Patch] Fix eclipse build after latest firefox update: >I had to apply the following patch to make eclipse build after the >latest firefox update (the one who changed firefox to use the system >nspr library). > >Steph Great Thanks david -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. From owner-freebsd-eclipse@FreeBSD.ORG Tue Aug 30 11:13:36 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECF0316A41F for ; Tue, 30 Aug 2005 11:13:36 +0000 (GMT) (envelope-from past@ebs.gr) Received: from fly.ebs.gr (fly.ebs.gr [62.103.84.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3A0F43D46 for ; Tue, 30 Aug 2005 11:13:35 +0000 (GMT) (envelope-from past@ebs.gr) Received: from ebs.gr (root@hal.ebs.gr [10.1.1.2]) by fly.ebs.gr (8.12.9p1/8.12.9) with ESMTP id j7UBDXID099120 for ; Tue, 30 Aug 2005 14:13:33 +0300 (EEST) (envelope-from past@ebs.gr) Received: from [10.1.1.162] (pc162.ebs.gr [10.1.1.162]) by ebs.gr (8.13.3/8.12.11) with ESMTP id j7UBDZxb080605 for ; Tue, 30 Aug 2005 14:13:36 +0300 (EEST) (envelope-from past@ebs.gr) Message-ID: <43143F59.7090504@ebs.gr> Date: Tue, 30 Aug 2005 14:13:29 +0300 From: Panagiotis Astithas Organization: EBS Ltd. User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050816) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-eclipse@freebsd.org Content-Type: multipart/mixed; boundary="------------080500040800020006090808" Subject: Testers please! X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 11:13:37 -0000 This is a multi-part message in MIME format. --------------080500040800020006090808 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit It seems that a patch for eclipse in our files directory is not needed. I would like people to try out this patch, rebuild eclipse and let me know if everything remains the same afterwards. Thanks, Panagiotis --------------080500040800020006090808 Content-Type: text/x-patch; name="eclipse.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="eclipse.patch" diff -ruN /usr/ports/java/eclipse/Makefile eclipse/Makefile --- /usr/ports/java/eclipse/Makefile Sun Aug 28 18:29:49 2005 +++ eclipse/Makefile Tue Aug 30 13:07:54 2005 @@ -107,8 +107,6 @@ ${FILESDIR}/manualpatch-plugins-swt-gtk-make_freebsd.mak @${PATCH} ${PATCH_DIST_ARGS} "${SWTGTK}/build.sh" \ ${FILESDIR}/manualpatch-plugins-swt-gtk-build.sh - @${PATCH} ${PATCH_DIST_ARGS} "${SWTGTK}/os_custom.h" \ - ${FILESDIR}/manualpatch-plugins-swt-gtk-os_custom.h do-build: @(cd ${WRKSRC}; ${SETENV} ${MAKE_ENV} \ diff -ruN /usr/ports/java/eclipse/files/manualpatch-plugins-swt-gtk-os_custom.h eclipse/files/manualpatch-plugins-swt-gtk-os_custom.h --- /usr/ports/java/eclipse/files/manualpatch-plugins-swt-gtk-os_custom.h Sun Jul 31 08:26:15 2005 +++ eclipse/files/manualpatch-plugins-swt-gtk-os_custom.h Thu Jan 1 02:00:00 1970 @@ -1,59 +0,0 @@ ---- plugins/org.eclipse.swt/Eclipse SWT PI/gtk/library/os_custom.h.orig Mon Jun 27 21:54:10 2005 -+++ plugins/org.eclipse.swt/Eclipse SWT PI/gtk/library/os_custom.h Thu Jul 14 20:28:19 2005 -@@ -21,31 +21,31 @@ - #define PTR_sizeof() sizeof(void *) - - /* Libraries for dynamic loaded functions */ --#define gtk_file_chooser_add_filter_LIB "libgtk-x11-2.0.so.0" --#define gtk_file_chooser_dialog_new_LIB "libgtk-x11-2.0.so.0" --#define gtk_file_chooser_get_current_folder_LIB "libgtk-x11-2.0.so.0" --#define gtk_file_chooser_get_filename_LIB "libgtk-x11-2.0.so.0" --#define gtk_file_chooser_get_filenames_LIB "libgtk-x11-2.0.so.0" --#define gtk_file_chooser_set_current_folder_LIB "libgtk-x11-2.0.so.0" --#define gtk_file_chooser_set_current_name_LIB "libgtk-x11-2.0.so.0" --#define gtk_file_chooser_set_extra_widget_LIB "libgtk-x11-2.0.so.0" --#define gtk_file_chooser_set_filename_LIB "libgtk-x11-2.0.so.0" --#define gtk_file_chooser_set_select_multiple_LIB "libgtk-x11-2.0.so.0" --#define gtk_file_filter_add_pattern_LIB "libgtk-x11-2.0.so.0" --#define gtk_file_filter_new_LIB "libgtk-x11-2.0.so.0" --#define gtk_file_filter_set_name_LIB "libgtk-x11-2.0.so.0" --#define gtk_tree_selection_get_selected_rows_LIB "libgtk-x11-2.0.so.0" --#define gtk_tree_view_column_cell_get_position_LIB "libgtk-x11-2.0.so.0" --#define gtk_entry_set_alignment_LIB "libgtk-x11-2.0.so.0" --#define gdk_draw_pixbuf_LIB "libgdk-x11-2.0.so.0" --#define gdk_screen_get_default_LIB "libgdk-x11-2.0.so.0" --#define gdk_screen_get_monitor_at_window_LIB "libgdk-x11-2.0.so.0" --#define gdk_screen_get_monitor_geometry_LIB "libgdk-x11-2.0.so.0" --#define gdk_screen_get_n_monitors_LIB "libgdk-x11-2.0.so.0" --#define gdk_screen_get_number_LIB "libgdk-x11-2.0.so.0" --#define gdk_window_set_keep_above_LIB "libgdk-x11-2.0.so.0" --#define gdk_window_set_accept_focus_LIB "libgdk-x11-2.0.so.0" --#define gdk_x11_screen_get_window_manager_name_LIB "libgdk-x11-2.0.so.0" -+#define gtk_file_chooser_add_filter_LIB "libgtk-x11-2.0.so" -+#define gtk_file_chooser_dialog_new_LIB "libgtk-x11-2.0.so" -+#define gtk_file_chooser_get_current_folder_LIB "libgtk-x11-2.0.so" -+#define gtk_file_chooser_get_filename_LIB "libgtk-x11-2.0.so" -+#define gtk_file_chooser_get_filenames_LIB "libgtk-x11-2.0.so" -+#define gtk_file_chooser_set_current_folder_LIB "libgtk-x11-2.0.so" -+#define gtk_file_chooser_set_current_name_LIB "libgtk-x11-2.0.so" -+#define gtk_file_chooser_set_extra_widget_LIB "libgtk-x11-2.0.so" -+#define gtk_file_chooser_set_filename_LIB "libgtk-x11-2.0.so" -+#define gtk_file_chooser_set_select_multiple_LIB "libgtk-x11-2.0.so" -+#define gtk_file_filter_add_pattern_LIB "libgtk-x11-2.0.so" -+#define gtk_file_filter_new_LIB "libgtk-x11-2.0.so" -+#define gtk_file_filter_set_name_LIB "libgtk-x11-2.0.so" -+#define gtk_tree_selection_get_selected_rows_LIB "libgtk-x11-2.0.so" -+#define gtk_tree_view_column_cell_get_position_LIB "libgtk-x11-2.0.so" -+#define gtk_entry_set_alignment_LIB "libgtk-x11-2.0.so" -+#define gdk_draw_pixbuf_LIB "libgdk-x11-2.0.so" -+#define gdk_screen_get_default_LIB "libgdk-x11-2.0.so" -+#define gdk_screen_get_monitor_at_window_LIB "libgdk-x11-2.0.so" -+#define gdk_screen_get_monitor_geometry_LIB "libgdk-x11-2.0.so" -+#define gdk_screen_get_n_monitors_LIB "libgdk-x11-2.0.so" -+#define gdk_screen_get_number_LIB "libgdk-x11-2.0.so" -+#define gdk_window_set_keep_above_LIB "libgdk-x11-2.0.so" -+#define gdk_window_set_accept_focus_LIB "libgdk-x11-2.0.so" -+#define gdk_x11_screen_get_window_manager_name_LIB "libgdk-x11-2.0.so" - - /* Field accessors */ - #define GTK_ACCEL_LABEL_SET_ACCEL_STRING(arg0, arg1) (arg0)->accel_string = arg1 --------------080500040800020006090808-- From owner-freebsd-eclipse@FreeBSD.ORG Tue Aug 30 12:15:51 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F17CC16A41F; Tue, 30 Aug 2005 12:15:50 +0000 (GMT) (envelope-from sepotvin@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9466043D46; Tue, 30 Aug 2005 12:15:50 +0000 (GMT) (envelope-from sepotvin@videotron.ca) Received: from [10.0.0.147] ([67.70.237.74]) by VL-MO-MR002.ip.videotron.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTPA id <0IM100G0VBECUCI0@VL-MO-MR002.ip.videotron.ca>; Tue, 30 Aug 2005 08:15:49 -0400 (EDT) Date: Tue, 30 Aug 2005 08:15:47 -0400 From: "Stephane E. Potvin" In-reply-to: <431382C3.3060205@ebs.gr> To: Panagiotis Astithas Message-id: <43144DF3.4020706@videotron.ca> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-Enigmail-Version: 0.92.0.0 References: <20050829180704.68762.qmail@exxodus.fedaykin.here> <43136B59.7090508@videotron.ca> <431382C3.3060205@ebs.gr> User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050826) Cc: freebsd-eclipse@freebsd.org, Mario Sergio Fujikawa Ferreira Subject: Re: Eclipse 3.1: no swt-pi-gtk-3138 X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 12:15:51 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Panagiotis Astithas wrote: > Stephane E. Potvin wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Mario Sergio Fujikawa Ferreira wrote: >> >>> Hi, >>> >>> I maintain 2 ports (net/mldonkey-sancho and net/azureus) >>> which depend on eclipse and have been broken ever since its update. >>> >>> I've just updated azureus yesterday and got it building just >>> fine but I get the following error message. >>> >>> $ ./azureus >>> >>> Exception in thread "main" java.lang.UnsatisfiedLinkError: no >>> swt-pi-gtk-3138 in java.library.path >>> at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1682) >>> at java.lang.Runtime.loadLibrary0(Runtime.java:822) >>> at java.lang.System.loadLibrary(System.java:992) >>> at org.eclipse.swt.internal.Library.loadLibrary(Library.java:123) >>> at org.eclipse.swt.internal.gtk.OS.(OS.java:19) >>> at >>> org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:63) >>> at >>> org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:54) >>> at org.eclipse.swt.widgets.Display.(Display.java:122) >>> at >>> org.gudy.azureus2.ui.swt.mainwindow.SWTThread.(Unknown Source) >>> at >>> org.gudy.azureus2.ui.swt.mainwindow.SWTThread.createInstance(Unknown >>> Source) >>> at >>> org.gudy.azureus2.ui.swt.mainwindow.Initializer.(Unknown Source) >>> at org.gudy.azureus2.ui.swt.Main.(Unknown Source) >>> at org.gudy.azureus2.ui.swt.Main.main(Unknown Source) >>> >>> which should be fixed by using a proper -Djava.library.path=somewhere >>> statemente. >>> >>> However, I am not able find the proper location to point to. >>> Taking a look at >>> >>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=89315 >>> >>> I find out that there are SWT PI patches there which are not included >>> with our java/eclipse port. > > > No way, I sent those attachments from my /usr/ports/java/eclipse/files > directory :-) > >>> Are there plans to integrate those patches now that the >>> ports freeze is over? >>> >>> Regards, >>> >> >> >> You can find the libraries in the >> org.eclipse.swt.gtk.freebsd.x86_3.1.0.jar file in eclipse's plugin >> directory. You'll have to extract them somewhere and add this path to >> your -Djava.library.path >> >> I have no idea why they are not extracted by default anymore. >> >> Regards, >> >> Steph > > > Exactly, eclipse now uses a simplified plugin distribution, where > everything is included in a single jar. I'll take a look into what needs > to be done for azureus, etc. Another option is to finish my swt31 port > and make swt-based apps depend on it. What would you prefer? > > Cheers, > > Panagiotis For what it's worth, if we go that road (having a separate swt port) I would like to have an option to have swt based ports depends on eclipse. As I'm using eclipse for development on my box, I would prefer to have only one instance of the swt library lying around. Steph -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDFE3zmdOXtTCX/nsRAtchAKD880AQccbihOFxiyVYDF7pRNebxwCfUGeU Xg277gnPtU1APh6ceEh1xpk= =iVAI -----END PGP SIGNATURE----- From owner-freebsd-eclipse@FreeBSD.ORG Tue Aug 30 16:03:04 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C4D416A41F for ; Tue, 30 Aug 2005 16:03:04 +0000 (GMT) (envelope-from lioux@FreeBSD.org) Received: from vette.gigo.com (vette.gigo.com [216.218.228.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id F30D743D45 for ; Tue, 30 Aug 2005 16:03:03 +0000 (GMT) (envelope-from lioux@FreeBSD.org) Received: from 201.24.49.97 (unknown [201.24.49.97]) by vette.gigo.com (Postfix) with ESMTP id 89B09575A for ; Tue, 30 Aug 2005 09:03:02 -0700 (PDT) Received: (qmail 50370 invoked by uid 1001); 30 Aug 2005 16:00:42 -0000 Message-ID: <20050830160042.50317.qmail@exxodus.fedaykin.here> Date: Tue, 30 Aug 2005 13:00:20 -0300 From: Mario Sergio Fujikawa Ferreira To: "Stephane E. Potvin" References: <20050829180704.68762.qmail@exxodus.fedaykin.here> <43136B59.7090508@videotron.ca> <431382C3.3060205@ebs.gr> <43144DF3.4020706@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43144DF3.4020706@videotron.ca> User-Agent: Mutt/1.5.9i Cc: freebsd-eclipse@freebsd.org Subject: Re: Eclipse 3.1: no swt-pi-gtk-3138 X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 16:03:04 -0000 Hi, Well, I agree that only one instance of swt should be ever lying around. Or, at least, that they not CONFLICT with one another since I need eclipse to build azureus but only swt to run it which means I would have a hell of a dependency problem otherwise. Well, for those wondering about an example. I did a crude hack to azureus to get it going. The port still needs polishing but it is good enough so that you can try any of the mentioned solutions. I, for one, would prefer that the eclipse port would extract the .so files somewhere rather than incarnating yet another port since I also need the swt*jar files which are part of eclipse. We wouldn't gain much from another port (saving run time dependencies I mean), we would require both in the end. Port sample, http://people.FreeBSD.org/~lioux/azureus.tgz Regards, -- Mario S F Ferreira - DF - Brazil - "I guess this is a signature." feature, n: a documented bug | bug, n: an undocumented feature From owner-freebsd-eclipse@FreeBSD.ORG Tue Aug 30 17:23:29 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A665F16A41F; Tue, 30 Aug 2005 17:23:29 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from lakecmmtao06.coxmail.com (lakecmmtao06.coxmail.com [68.99.120.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FAC743D48; Tue, 30 Aug 2005 17:23:28 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from dns1 ([64.58.171.82]) by lakecmmtao06.coxmail.com (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20050830172327.OLGD24491.lakecmmtao06.coxmail.com@dns1>; Tue, 30 Aug 2005 13:23:27 -0400 From: Vizion To: freebsd-eclipse@freebsd.org Date: Tue, 30 Aug 2005 10:19:27 -0700 User-Agent: KMail/1.8 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508301019.28780.vizion@vizion.occoxmail.com> Cc: Greg Lewis , Herve Quiroz , David Wolfskill Subject: How should eclipse be organized in the ports tree? X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 17:23:29 -0000 On Tuesday 30 August 2005 08:26, the author Herve Quiroz contributed to the dialogue on- Re: Eclipse as part of the ports/java tree? [Was freebsd eclipse plugins & mailing list]: This is my reaction to part of Herv's original contribution (I will post the rest later) to a debate about how eclipse plugins would be best organized in the freebsd ports tree. I have no fixed ideas about this but am aware there are now almost 300 plugins which, I believe, should be in our ports tree. The question is how to organize them. ------------------------------------------ Herv has said he will not subscribe to freebsd-eclipse so I am copying this here. >David, > >I pretty much agree with all that Greg already said but still there are >some facts I think you should be aware of if you actually wish to >improve eclipse support in the ports tree... I am replying to part of your response because I think you have a great musunderstanding. >I don't think you will get much attention from other commiters if you >introduce things as "the one true approach" compared to the "suboptimal >fashion" that is, by your word, the current state of the ports system. > Please do NOT put words the words of others in my mouth. "suboptimal" was not my description but a description given by Greg to the current state of affairs. I happen to agree with him but it is a committer who believes that to be the case. So please do not cast me in the role of an outsider decrying the work of vituous committers. I very much appreciate what you guys do which is done very well (even if I do hold to the view that the freebsd policies (which determine what should be done) are fast becoming out of date and in consequence freebsd is in danger of losing its pre-eminent place to linux. To my mind that would be a great loss). >Let's rather discuss the real motive here: improve Eclipse plugin >support in the ports tree. It is not justabout improving the support it is about improving convenience and accessibility. Perhaps it could be solved by writing an eclipse plugin for freebsd users which accessed the freebsd ports tree and pulled the plugins directly from the tree and installed them? In that way the freebsd ports tree would then have only to store the plugins themselves. This might be the way to go. In fact taking it one stage further such a plugin would mean that eclipse could be used to develop a global freebsd port access and installation tool. Now that is something worth thinking about! My general question is would there be real benefits from seperating the data storage and its internal structures (the ports tree itself), from the gui (which could use metadata to present information in the form required by the user about the data and assist the end user to select manage, select, upfate and install ports) and processes which implement user instructions. I sometimes wonder the excellent ports tree system appears, by comparison with some recent approaches, not to have benefited from an access makeover. However good the product I wonder whether we need to give more consideration to useability. An all bells and whistles web/database driven front end interface which enables the end user to organize information about the content is an ideal dream. Getting someone to give the time to do the work would be the challenge. >Again, it has nothing to do with the >greatness of Eclipse nor the personal feelings of commiters towards >Eclipse. In the later case, I would probably already have done some "cvs >remove" on /usr/ports/java/eclipse a long time ago. :-) Perhaps freebsd committers have had too much on their plate to be other than reactive. Certainly we are behind the curve on this one by comparison with Linux and that is worrying. Especially as the eclipse team only took the initiative to work with linux and ignored freebsd. That is starting to change thanks to the efforts of a few freebsd eclipse users and committers. > >Together with the freebsd-java community we have been working on >refactoring the Java subsystem for years so that it would provide *us* >the support *we* needed (that is, not only to attract more developpers >to FreeBSD from Linux). It took quite some time and some lengthy >dicsussions to get our bsd.java.mk subsystem added to the tree and we >are speaking of more than 300 Java ports here. So unless we manage to >use a similar apporach for Eclipse as for jdictionary, you will probably >end up battling a long time, advocating for a rework of the whole ports >tree when 20 plugins ports are indeed concerned. I do not know where you get the idea of 20 plugin ports from. There are currently twenty categories of eclipse plugins and 291 plugins. The estimate is that will be around 600 plugins within a year from now. Are you not sure that the scale of takeup, the volume of development in eclipse (and possibly its significance), and its potential to contribute to the advancement of freebsd has been underestimated within the freebsd "meritocracy". Will you please refrain from suggesting that I am advocating a rework of the ports tree? I have no way of knowing if or why any reworking is needed. It seems to me that that is matter for those who control the ports tree to decide. I fo not know how it works. My concern is to ensure that freebsd benefits from developments in the wider community and builds upon is assets. This discussion has taken me froma position of believing that freebsd has the tools we need to one where I have started to worry whether our assets (including the ports tree) have been engineered in a that has made data so inextricably interwoven with process that resource adaptability is now severely compromised. Fo you not agree that worry is reinforced when members of the committer community argue against such the simple concept I have proposed to deal with almost 300 eclipse plugins on the grounds that it implies a reworking of the ports tree? To be fair Greg has suggested that my proposal could be adopted by using what he labelled as a "virtual" solution that has been used elsewhere. From the way he put it forward I drew the implication that there would be a knee jerk reaction against the idea. I am now faced with the question is the ports tree as inflexible as some people suggest or are some members of our meritocracy more inflexible than the freebsd assets? -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. From owner-freebsd-eclipse@FreeBSD.ORG Tue Aug 30 18:37:54 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21CF516A41F for ; Tue, 30 Aug 2005 18:37:54 +0000 (GMT) (envelope-from ddurham@vailsys.com) Received: from dfrobd01.vailsys.com (chrobd01.vailsys.com [63.210.102.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A6A543DB3 for ; Tue, 30 Aug 2005 18:36:25 +0000 (GMT) (envelope-from ddurham@vailsys.com) Received: from dfsfbd06.vail (dfsfbd06.vail [192.168.129.190]) by dfrobd01.vailsys.com (Postfix) with ESMTP id 1876CFF2C for ; Tue, 30 Aug 2005 13:09:14 -0500 (CDT) Received: from [192.168.129.86] (dfwddurham.vail [192.168.129.86]) by dfsfbd06.vail (Postfix) with ESMTP id 036D552A6 for ; Tue, 30 Aug 2005 13:08:36 -0500 (CDT) Message-ID: <4314A091.5030700@vailsys.com> Date: Tue, 30 Aug 2005 13:08:17 -0500 From: David Durham User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-eclipse@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: eclipse 3.1 on freebsd 5.4 X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 18:37:54 -0000 I'm a BSD newb. Actually, I'm pretty much a *NIX newb. Anyway, I'm trying to setup eclipse 3.1 on freebsd 5.4. I'm able to setup 3.0.1 using pkg_add -r eclipse, but I'm not sure about running 3.1M# or nightly versions for that matter. I tried building from source, but received compiler errors, which I didn't track down, but could investigate further. I tried running the linux binaries, but I received an error: error while loading shared libraries: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory I'm actually hoping there is some kind of installation guide for 3.1 on FreeBSD or perhaps a port that I can download. Thanks in advance. - Dave From owner-freebsd-eclipse@FreeBSD.ORG Tue Aug 30 18:44:13 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EE7016A41F for ; Tue, 30 Aug 2005 18:44:13 +0000 (GMT) (envelope-from frank@fstaals.net) Received: from smtp1.versatel.nl (smtp1.versatel.nl [62.58.50.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5162443D46 for ; Tue, 30 Aug 2005 18:44:11 +0000 (GMT) (envelope-from frank@fstaals.net) Received: (qmail 16305 invoked by uid 0); 30 Aug 2005 18:44:11 -0000 Received: from unknown (HELO [192.168.2.5]) ([62.59.173.176]) (envelope-sender ) by smtp1.versatel.nl (qmail-ldap-1.03) with SMTP for < >; 30 Aug 2005 18:44:11 -0000 Message-ID: <4314A913.9040406@fstaals.net> Date: Tue, 30 Aug 2005 20:44:35 +0200 From: Frank Staals User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050521) X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Durham References: <4314A091.5030700@vailsys.com> In-Reply-To: <4314A091.5030700@vailsys.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-eclipse@freebsd.org Subject: Re: eclipse 3.1 on freebsd 5.4 X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 18:44:13 -0000 David Durham wrote: > I'm a BSD newb. Actually, I'm pretty much a *NIX newb. Anyway, I'm > trying to setup eclipse 3.1 on freebsd 5.4. I'm able to setup 3.0.1 > using pkg_add -r eclipse, but I'm not sure about running 3.1M# or > nightly versions for that matter. I tried building from source, but > received compiler errors, which I didn't track down, but could > investigate further. I tried running the linux binaries, but I > received an error: > > error while loading shared libraries: libgtk-x11-2.0.so.0: cannot > open shared object file: No such file or directory > > I'm actually hoping there is some kind of installation guide for 3.1 > on FreeBSD or perhaps a port that I can download. Thanks in advance. > > > - Dave > > _______________________________________________ > freebsd-eclipse@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-eclipse > To unsubscribe, send any mail to > "freebsd-eclipse-unsubscribe@freebsd.org" Hey, You could/should just build the newest port in the portstree, so cvsup it, here quick what you should do if that isn't set up yet: pkg_add -r cvsup-without-gui make a cvsup file with your favourite text editor, it should look like this ( choose a mirror which is close to you, for me that is in the Netherlands ) : *default tag=. *default host=cvsup2.nl.freebsd.org *default prefix=/usr *default base=/var/db *default release=cvs delete use-rel-suffix compress ports-all release=cvs cvsup -L 2 -g /path/to/cvsupfile after it is finished: cd /usr/ports/java/eclipse && make install distclean That's all good luck -- -Frank Staals From owner-freebsd-eclipse@FreeBSD.ORG Tue Aug 30 18:53:28 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6C2116A41F; Tue, 30 Aug 2005 18:53:28 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from lakecmmtao04.coxmail.com (lakecmmtao04.coxmail.com [68.99.120.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 691CB43D48; Tue, 30 Aug 2005 18:53:28 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from dns1 ([64.58.171.82]) by lakecmmtao04.coxmail.com (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20050830185328.XANN3947.lakecmmtao04.coxmail.com@dns1>; Tue, 30 Aug 2005 14:53:28 -0400 From: Vizion To: freebsd-eclipse@freebsd.org Date: Tue, 30 Aug 2005 11:49:28 -0700 User-Agent: KMail/1.8 References: <200508301019.28780.vizion@vizion.occoxmail.com> In-Reply-To: <200508301019.28780.vizion@vizion.occoxmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508301149.28769.vizion@vizion.occoxmail.com> Cc: Greg Lewis , Herve Quiroz Subject: Re: How should eclipse be organized in the ports tree? X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 18:53:29 -0000 On Tuesday 30 August 2005 08:26, the author Herve Quiroz contributed to the dialogue on- Re: How should eclipse be organized in the ports tree? Here is the second part >David, > >I pretty much agree with all that Greg already said but still there are >some facts I think you should be aware of if you actually wish to >improve eclipse support in the ports tree... > >On Fri, Aug 26, 2005 at 05:20:38PM -0700, Vizion wrote: >> >I'm not sure how thats an argument for creating a non-virtual eclipse >> >category. Would you care to explain? >> >> To hell with the pedantic label -- call it what you like - virtual or >> non-virtual what matters is the reality of access and support to the >> freebsd community that comes from the way in which we organize our files >> and install the client rich applications and tools. >> >> here is what I think would work: >> ports/eclipse/eclipse.v.x.xxx >> .................../eclipse.v.x.nnn >> ports/eclipse/plugins/puginlabel1 >> ports/eclipse/plugins/pluginlabel2 >> ................................/pluginlabelN >> ports/eclipse/misc/file1 >> ports/eclipse/misc/file2 >> ............................/fileN >> >> Scattering eclipse modules and plugins over the whole of the ports tree >> would, I believe, be both counterintuitive, counterproductive and >> confusing.ports/eclipse > >No tool, whatever its "usefulness", deserves to have its own ports tree >in the ports tree. That's indeed what you suggest in your message. The >way the ports tree currently works is somewhat well defined in many >locations (the Porter's Handbook mainly) and we, as commiters, tend to >ensure that the current ports system provides enough flexibility so that >no port would need some special treatment to fit in the ports tree. Does not flexibilty mean the system being able to meet the special needs of any individual port -- rather than the port having to adapted to meet the inevitably limited preconceptions of the system at the time of its conception? If the system was flexible then there would be no problem! Let see what we need and take it from there. Eclipse is a client rich application with nearly 300 plugin modules which is likely to have over 600 plugin modules within a year. Each plugin, in combination with the core, can (and often does) combine multiple functionalities (e.g it may combine the functionalities of a database, a browser, a language development environment and a network service). Modules may be dependent upon one another. Eclipse has its own internal mechanisms for handling those interdependencies. Is not the Freebsd ports hierarchy designed, from the base up, by seperating software on the assumption that the software can be categorized by functionalities? Is not the question how do we deal with archiving ports which conceptually conflict with the assumptions behind the original design. Or to put it the other way round, my question is how can we use the existing ports hierarchy to meet the needs of the new generation of client rich applications which eclipse represents? Eclipse represents a type of software development which did not exist at the time freebsd (or the ports) were being designed. How do we store 300 -600 plugins in the short term and make them easily accessible? How do we do that in a simple way? Eclipse has an inbuilt plugin import system. If all the plugins were organized in one directory then it would be possible to build a generic system which could use eclipse to load the plugins and reduce the amount of work needed to keep the eclipse hierarchy up to date. The only thing needed to make this work would be that only eclipse plugins should reside in the directory. Hence my suggestion /usr/ports/eclipse This directory would hold the eclipse core identified by version number and possibly a freebsd specific plugin which manages the loading of all remaining eclipse plugins /usr/ports/eclipse/plugins /usr/ports/eclipse/misc there is no reasomn why this hierarchy should not be: /usr/ports/xxxx/eclipse /usr/ports/xxxx/eclipse/plugins /usr/ports/xxxx/eclipse/misc I see practicle reasons for keep all eclipseplugins in a single directory hierarchy. david -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. From owner-freebsd-eclipse@FreeBSD.ORG Tue Aug 30 23:19:55 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 131F816A41F; Tue, 30 Aug 2005 23:19:55 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from lakecmmtao06.coxmail.com (lakecmmtao06.coxmail.com [68.99.120.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8598843D48; Tue, 30 Aug 2005 23:19:54 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from dns1 ([64.58.171.82]) by lakecmmtao06.coxmail.com (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20050830231953.GYNB24491.lakecmmtao06.coxmail.com@dns1>; Tue, 30 Aug 2005 19:19:53 -0400 From: Vizion To: Mark Linimon Date: Tue, 30 Aug 2005 16:15:52 -0700 User-Agent: KMail/1.8 References: <200508251303.59453.vizion@vizion.occoxmail.com> <200508301010.27373.vizion@vizion.occoxmail.com> <20050830212342.GA32240@soaustin.net> In-Reply-To: <20050830212342.GA32240@soaustin.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508301615.53251.vizion@vizion.occoxmail.com> Cc: Herve Quiroz , freebsd-eclipse@freebsd.org Subject: Re: How should eclipse be organized in the ports tree? X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 23:19:55 -0000 On Tuesday 30 August 2005 14:23, the author Mark Linimon contributed to the dialogue on- Re: Eclipse as part of the ports/java tree? [Was freebsd eclipse plugins & mailing list]: BTW I have switched subject to the thread for the freebsd-eclipse maillist and cc'd you and Herve. I want to respect those who are on the official freebsd-eclipse mailing list. I could also cc the text to freebsd-java if you want. >On Tue, Aug 30, 2005 at 10:10:26AM -0700, Vizion wrote: >> I am now faced with the question is the ports tree as inflexible as some >> people suggest or are some members of our meritocracy more inflexible than >> the freebsd assets? > >This is a complete oversimplification of the situation. > >There are some hard-coded assumptions in the ports tree -- one of which is >that there are two levels, categories and ports -- and these assumptions >are mirrored in the repositories of tens of thousands if not hundreds of >thousands of users, and thousands of lines of shell scripts and database >programs that create the binary packages and monitor the results of those >build processes. > >So when you suggest that the only way that Eclipse can be supported is >to have a multilevel ports tree -- as you are seeming to -- you are clearly >totally misunderestimating the amount of effort involved. > >In your most recent email I think you are finally getting a lot closer to >what I consider 'real' problem. IMHO the interesting problems you want to >solve are the 'search' and 'browse' problems. Directory names controlled >by CVS structures in an unbranched tree, which are then mirrored all around >the world, are really poor paradigms for these problems. Herve has >suggested some better tools for these which are better ways to think >about these problems and you should look at those. We certainly need more. > >The meta-plugin idea is also worth considering. > >But restructuring the entire tree, even to add a few hundred ports, is >simply not feasible with the level of volunteer effort we have and the >number of people that depend on the current structure worldwide. > >mcl Ok - building on your comments would my original suggestion, as modified below, and leaving aside for one moment the arguments as to whether or not committers might desire it,be capable of implementation without a restructuring of code? This proposal mean that /usr/ports/plugins/*.jar is a repository for files which are accessed solely via the meta-eclipsevx.xxx ports. I think this might shoehorn the necessary structure into the existing system. What do you think? /usr/ports/eclipse/eclipsemainv[x.xxx] Holds the main eclipse ports /usr/ports/eclipse/meta-eclipse[v.xxx] Holds eclipse plugins loader /usr/ports/eclipse/plugins/ Holds the *.jar files /usr/ports/eclipse/misc1 self contained eclipse ports /usr/ports/eclipse/misc2 /usr/ports/eclipse/miscN /usr/ports/eclipse/plugins would, in effect, be a set of files which would be downloaded under control of the meta-eclipse loader If so why not use it - that would make eclipse a category which could enclose a number of ports for eclipse versions, a number of /usr/ports/eclipse/meta_eclipseplugin ports and each plugin would then (in effect) be a *.jar file file held within the /usr/eclipse/plugins directory. The meta_eclipse plugin could build the library of available plugins on the fly and use the standard system for registering the plugins on the local machine. In that way could the need be integrated into the existing system? Whatis your reaction? david -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 01:03:09 2005 Return-Path: X-Original-To: freebsd-eclipse@hub.freebsd.org Delivered-To: freebsd-eclipse@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F09BE16A420; Wed, 31 Aug 2005 01:03:09 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACE0543D55; Wed, 31 Aug 2005 01:03:09 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7V1396t028726; Wed, 31 Aug 2005 01:03:09 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7V139B8028722; Wed, 31 Aug 2005 01:03:09 GMT (envelope-from linimon) Date: Wed, 31 Aug 2005 01:03:09 GMT From: Mark Linimon Message-Id: <200508310103.j7V139B8028722@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, freebsd-eclipse@FreeBSD.org Cc: Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 01:03:10 -0000 Synopsis: upgrade of the CDT plugin for eclipse Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-eclipse Responsible-Changed-By: linimon Responsible-Changed-When: Wed Aug 31 01:02:58 GMT 2005 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=85501 From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 02:31:34 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFB3F16A421; Wed, 31 Aug 2005 02:31:33 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from lakecmmtao04.coxmail.com (lakecmmtao04.coxmail.com [68.99.120.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A21443D55; Wed, 31 Aug 2005 02:31:32 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from dns1 ([64.58.171.82]) by lakecmmtao04.coxmail.com (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20050831023132.SMFK3947.lakecmmtao04.coxmail.com@dns1>; Tue, 30 Aug 2005 22:31:32 -0400 From: Vizion To: Mark Linimon Date: Tue, 30 Aug 2005 19:27:30 -0700 User-Agent: KMail/1.8 References: <200508251303.59453.vizion@vizion.occoxmail.com> <20050830212342.GA32240@soaustin.net> <200508301615.53251.vizion@vizion.occoxmail.com> In-Reply-To: <200508301615.53251.vizion@vizion.occoxmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508301927.31549.vizion@vizion.occoxmail.com> Cc: Herve Quiroz , freebsd-eclipse@freebsd.org Subject: Re: How should eclipse be organized in the ports tree? X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 02:31:34 -0000 On Tuesday 30 August 2005 16:15, the author Vizion contributed to the dialogue on- Re: How should eclipse be organized in the ports tree?: >On Tuesday 30 August 2005 14:23, the author Mark Linimon contributed to the >dialogue on- > Re: Eclipse as part of the ports/java tree? [Was freebsd eclipse plugins & >mailing list]: >BTW I have switched subject to the thread for the freebsd-eclipse maillist > and cc'd you and Herve. I want to respect those who are on the official > freebsd-eclipse mailing list. I could also cc the text to freebsd-java if > you want. > >>On Tue, Aug 30, 2005 at 10:10:26AM -0700, Vizion wrote: >>> I am now faced with the question is the ports tree as inflexible as some >>> people suggest or are some members of our meritocracy more inflexible >>> than the freebsd assets? >> >>This is a complete oversimplification of the situation. >> >>There are some hard-coded assumptions in the ports tree -- one of which is >>that there are two levels, categories and ports -- and these assumptions >>are mirrored in the repositories of tens of thousands if not hundreds of >>thousands of users, and thousands of lines of shell scripts and database >>programs that create the binary packages and monitor the results of those >>build processes. >> >>So when you suggest that the only way that Eclipse can be supported is >>to have a multilevel ports tree -- as you are seeming to -- you are clearly >>totally misunderestimating the amount of effort involved. >> >>In your most recent email I think you are finally getting a lot closer to >>what I consider 'real' problem. IMHO the interesting problems you want to >>solve are the 'search' and 'browse' problems. Directory names controlled >>by CVS structures in an unbranched tree, which are then mirrored all around >>the world, are really poor paradigms for these problems. Herve has >>suggested some better tools for these which are better ways to think >>about these problems and you should look at those. We certainly need more. >> >>The meta-plugin idea is also worth considering. >> >>But restructuring the entire tree, even to add a few hundred ports, is >>simply not feasible with the level of volunteer effort we have and the >>number of people that depend on the current structure worldwide. >> >>mcl > >Ok - building on your comments would my original suggestion, as modified >below, and leaving aside for one moment the arguments as to whether or not >committers might desire it,be capable of implementation without a >restructuring of code? > >This proposal mean that /usr/ports/plugins/*.jar is a repository for files >which are accessed solely via the meta-eclipsevx.xxx ports. > >I think this might shoehorn the necessary structure into the existing > system. What do you think? > >/usr/ports/eclipse/eclipsemainv[x.xxx] Holds the main eclipse ports >/usr/ports/eclipse/meta-eclipse[v.xxx] Holds eclipse plugins loader Just for sake of clarity the above are intended to be straight forward ports >/usr/ports/eclipse/plugins/ Holds the *.jar files >/usr/ports/eclipse/misc1 self contained eclipse ports > /usr/ports/eclipse/misc2 >/usr/ports/eclipse/miscN > >/usr/ports/eclipse/plugins would, in effect, be a set of files which would > be downloaded under control of the meta-eclipse loader > > If so why not use it - that would make eclipse a category which could > enclose a number of ports for eclipse versions, a number >of /usr/ports/eclipse/meta_eclipseplugin ports and each plugin would then >(in effect) be a *.jar file file held within the /usr/eclipse/plugins >directory. >The meta_eclipse plugin could build the library of available plugins on the >fly and use the standard system for registering the plugins on the local >machine. In that way could the need be integrated into the existing system? > >Whatis your reaction? > >david -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 07:20:19 2005 Return-Path: X-Original-To: freebsd-eclipse@hub.freebsd.org Delivered-To: freebsd-eclipse@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 718DA16A41F for ; Wed, 31 Aug 2005 07:20:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E6D543D45 for ; Wed, 31 Aug 2005 07:20:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7V7KJXs083926 for ; Wed, 31 Aug 2005 07:20:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7V7KIcM083925; Wed, 31 Aug 2005 07:20:18 GMT (envelope-from gnats) Date: Wed, 31 Aug 2005 07:20:18 GMT Message-Id: <200508310720.j7V7KIcM083925@freefall.freebsd.org> To: freebsd-eclipse@FreeBSD.org From: Panagiotis Astithas Cc: Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Panagiotis Astithas List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 07:20:19 -0000 The following reply was made to PR ports/85501; it has been noted by GNATS. From: Panagiotis Astithas To: bug-followup@FreeBSD.org, jgutie11@eafit.edu.co Cc: Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse Date: Wed, 31 Aug 2005 10:17:47 +0300 This is similar to my patch at PR ports/85300. You might consider keeping the automatically generated pkg-plist from my version. From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 07:27:51 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEFB716A41F; Wed, 31 Aug 2005 07:27:51 +0000 (GMT) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (glewis.dsl.xmission.com [166.70.56.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AD4443D45; Wed, 31 Aug 2005 07:27:50 +0000 (GMT) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (localhost.eyesbeyond.com [127.0.0.1]) by misty.eyesbeyond.com (8.13.3/8.13.3) with ESMTP id j7V7RmNF073078; Wed, 31 Aug 2005 01:27:49 -0600 (MDT) (envelope-from glewis@eyesbeyond.com) Received: (from glewis@localhost) by misty.eyesbeyond.com (8.13.3/8.13.3/Submit) id j7V7Rl5n073077; Wed, 31 Aug 2005 01:27:47 -0600 (MDT) (envelope-from glewis@eyesbeyond.com) X-Authentication-Warning: misty.eyesbeyond.com: glewis set sender to glewis@eyesbeyond.com using -f Date: Wed, 31 Aug 2005 01:27:47 -0600 From: Greg Lewis To: Vizion Message-ID: <20050831072747.GC72699@misty.eyesbeyond.com> References: <200508301019.28780.vizion@vizion.occoxmail.com> <200508301149.28769.vizion@vizion.occoxmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200508301149.28769.vizion@vizion.occoxmail.com> User-Agent: Mutt/1.4.2.1i Cc: Herve Quiroz , freebsd-eclipse@freebsd.org Subject: Re: How should eclipse be organized in the ports tree? X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 07:27:51 -0000 David, On Tue, Aug 30, 2005 at 11:49:28AM -0700, Vizion wrote: > Does not flexibilty mean the system being able to meet the special needs of > any individual port -- rather than the port having to adapted to meet the > inevitably limited preconceptions of the system at the time of its > conception? If the system was flexible then there would be no problem! > > Let see what we need and take it from there. > Eclipse is a client rich application with nearly 300 plugin modules which is > likely to have over 600 plugin modules within a year. > > Each plugin, in combination with the core, can (and often does) combine > multiple functionalities (e.g it may combine the functionalities of a > database, a browser, a language development environment and a network > service). > > Modules may be dependent upon one another. > > Eclipse has its own internal mechanisms for handling those interdependencies. > > Is not the Freebsd ports hierarchy designed, from the base up, by seperating > software on the assumption that the software can be categorized by > functionalities? > > Is not the question how do we deal with archiving ports which conceptually > conflict with the assumptions behind the original design. Or to put it the > other way round, my question is how can we use the existing ports hierarchy > to meet the needs of the new generation of client rich applications which > eclipse represents? > > Eclipse represents a type of software development which did not exist at the > time freebsd (or the ports) were being designed. > > How do we store 300 -600 plugins in the short term and make them easily > accessible? > > How do we do that in a simple way? > > Eclipse has an inbuilt plugin import system. If all the plugins were organized > in one directory then it would be possible to build a generic system which > could use eclipse to load the plugins and reduce the amount of work needed to > keep the eclipse hierarchy up to date. > > The only thing needed to make this work would be that only eclipse plugins > should reside in the directory. > > Hence my suggestion > > /usr/ports/eclipse > This directory would hold the eclipse core > identified by version number and possibly a freebsd specific plugin which > manages the loading of all remaining eclipse plugins > /usr/ports/eclipse/plugins > /usr/ports/eclipse/misc > > there is no reasomn why this hierarchy should not be: > /usr/ports/xxxx/eclipse > /usr/ports/xxxx/eclipse/plugins > /usr/ports/xxxx/eclipse/misc > > I see practicle reasons for keep all eclipseplugins in a single directory > hierarchy. I wholeheartedly support the notion of greater eclipse support in the ports tree. I'm even happy to commit additional eclipse support as time permits. However, this is my last e-mail about this subject for the forseeable future as, to be blunt, e-mails on this subject don't seem to be productive. I'd much rather spend my time releasing patchset 2 of 1.5.0, but, since I would like to see Eclipse support get better I thought I'd try and offer some constructive criticism of your proposals. However, it seems to be falling on deaf ears, so I'm going to be as frank as I can in this e-mail. 1. You keep claiming that your proposal of adding an extra directory level to the ports tree, ports/eclipse/plugins/ has no impact. It does. As I've noted before, this has been discussed previously on freebsd-ports and there are currently _technical reasons_ why it won't work. I'm not going to look up all the references, please see the archives for those, but here is one from last October: http://lists.freebsd.org/pipermail/freebsd-ports/2004-October/017195.html 2. You clearly don't understand virtual categories. When I suggested one for eclipse you alternatively dismissed it or attacked me about it rather than either reading the Porters Handbook or admitting you didn't know what a virtual category was and asking about it. Please take the time to at least get familiar with things like this. 3. For some reason when Herve and I talk about the 20 or so Eclipse plugins that are _actually in the ports tree right now_, you take immediate offense and insist that there are 300+ Eclipse plugins. Yes there are many, many Eclipse plugins. But we're not talking about that, we're talking about how many are actually in the tree right now, and that is what people are going to see when you propose a big reorganisation (which you are, see point 1). Also, please don't insult our intelligence by insisting that the fairies will magically commit all 300+ plugins as ports overnight if we would only rearrange the ports tree how you think we need to. 4. You're proposing a radical departure for the ports tree. There are _no other applications_ which have their own non-virtual category. The bigger the change you propose, the more compelling and weighty your reasoning must be for it to be accepted. I would suggest that "Its got a lot of plugins that fall into different categories" isn't going to cut it. No, its not my call to make, I'm merely suggesting that I don't believe that people will find your current reasoning compelling enough. If I'm wrong, great, go ahead. If I'm not then perhaps you may want to spend some time coming up with answers to questions like "Perl has 1700+ modules already in the ports tree and it doesn't have its own non-virtual category, why should eclipse have one?". Maybe thats as simple as giving some reasons why that comparison is invalid, but whatever the case I'm merely suggesting you might want to give your argument some thought. 5. Please don't claim that you can't start working on improving Eclipse support because you have to fight a huge political battle at the same time. This isn't a political discussion and never has been. You've put forward a proposal, you must be willing to clarify or modify it when people raise technical and resource concerns regarding it. When you either dismiss these concerns or answer them with clearly incorrect technical data while crying political martydom all it does is piss people off. Finally, its great that you want to improve Eclipse support. I wish you success with that endeavour if you choose to pursue it and hopefully I can be of some assistance. Its not easy building a community within the FreeBSD community, so best of luck. -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 07:58:35 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BD2A16A41F; Wed, 31 Aug 2005 07:58:35 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5531E43D46; Wed, 31 Aug 2005 07:58:35 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 236472A74; Wed, 31 Aug 2005 02:58:34 -0500 (CDT) Date: Wed, 31 Aug 2005 02:58:34 -0500 To: Vizion Message-ID: <20050831075834.GA21200@soaustin.net> References: <200508251303.59453.vizion@vizion.occoxmail.com> <200508301010.27373.vizion@vizion.occoxmail.com> <20050830212342.GA32240@soaustin.net> <200508301615.53251.vizion@vizion.occoxmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200508301615.53251.vizion@vizion.occoxmail.com> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: Mark Linimon , Herve Quiroz , freebsd-eclipse@freebsd.org Subject: Re: How should eclipse be organized in the ports tree? X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 07:58:35 -0000 On Tue, Aug 30, 2005 at 04:15:52PM -0700, Vizion wrote: > /usr/ports/eclipse/eclipsemainv[x.xxx] Holds the main eclipse ports > /usr/ports/eclipse/meta-eclipse[v.xxx] Holds eclipse plugins loader > /usr/ports/eclipse/plugins/ Holds the *.jar files > /usr/ports/eclipse/misc1 self contained eclipse ports > /usr/ports/eclipse/misc2 > /usr/ports/eclipse/miscN This is certainly much closer to what is in the existing system (given that the jar files would probably better be in plugins/files/*.jar). The name 'meta-eclipse' would probably be less confusing to me personally as 'eclipse-plugins-loader' or something, 'meta' is a term that can mean everything or nothing. And if you change 'eclipsemainv' to just 'eclipseY.Z' and 'plugins' to 'eclipse-plugins' then that's very similar to what we have now. Then there's the matter of whether all this needs to be its own category but I don't think I am going to try to talk you out of that idea. I'm not too fond of it, personally. mcl From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 08:16:59 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8869C16A41F; Wed, 31 Aug 2005 08:16:59 +0000 (GMT) (envelope-from past@ebs.gr) Received: from fly.ebs.gr (fly.ebs.gr [62.103.84.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E0BF43D45; Wed, 31 Aug 2005 08:16:58 +0000 (GMT) (envelope-from past@ebs.gr) Received: from ebs.gr (root@hal.ebs.gr [10.1.1.2]) by fly.ebs.gr (8.12.9p1/8.12.9) with ESMTP id j7V8GuID003173; Wed, 31 Aug 2005 11:16:56 +0300 (EEST) (envelope-from past@ebs.gr) Received: from [10.1.1.161] (pc161.ebs.gr [10.1.1.161]) by ebs.gr (8.13.3/8.12.11) with ESMTP id j7V8GwJd097034; Wed, 31 Aug 2005 11:16:58 +0300 (EEST) (envelope-from past@ebs.gr) Message-ID: <43156772.7070808@ebs.gr> Date: Wed, 31 Aug 2005 11:16:50 +0300 From: Panagiotis Astithas Organization: EBS Ltd. User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050830) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vizion References: <200508251303.59453.vizion@vizion.occoxmail.com> <20050830212342.GA32240@soaustin.net> <200508301615.53251.vizion@vizion.occoxmail.com> <200508301927.31549.vizion@vizion.occoxmail.com> In-Reply-To: <200508301927.31549.vizion@vizion.occoxmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mark Linimon , Herve Quiroz , freebsd-eclipse@freebsd.org Subject: Re: How should eclipse be organized in the ports tree? X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 08:16:59 -0000 Vizion wrote: > On Tuesday 30 August 2005 16:15, the author Vizion contributed to the > dialogue on- > Re: How should eclipse be organized in the ports tree?: > > >>On Tuesday 30 August 2005 14:23, the author Mark Linimon contributed to the >>dialogue on- >>Re: Eclipse as part of the ports/java tree? [Was freebsd eclipse plugins & >>mailing list]: >>>On Tue, Aug 30, 2005 at 10:10:26AM -0700, Vizion wrote: >>> >>>>I am now faced with the question is the ports tree as inflexible as some >>>>people suggest or are some members of our meritocracy more inflexible >>>>than the freebsd assets? >>> >>>This is a complete oversimplification of the situation. >>> >>>There are some hard-coded assumptions in the ports tree -- one of which is >>>that there are two levels, categories and ports -- and these assumptions >>>are mirrored in the repositories of tens of thousands if not hundreds of >>>thousands of users, and thousands of lines of shell scripts and database >>>programs that create the binary packages and monitor the results of those >>>build processes. >>> >>>So when you suggest that the only way that Eclipse can be supported is >>>to have a multilevel ports tree -- as you are seeming to -- you are clearly >>>totally misunderestimating the amount of effort involved. >>> >>>In your most recent email I think you are finally getting a lot closer to >>>what I consider 'real' problem. IMHO the interesting problems you want to >>>solve are the 'search' and 'browse' problems. Directory names controlled >>>by CVS structures in an unbranched tree, which are then mirrored all around >>>the world, are really poor paradigms for these problems. Herve has >>>suggested some better tools for these which are better ways to think >>>about these problems and you should look at those. We certainly need more. >>> >>>The meta-plugin idea is also worth considering. >>> >>>But restructuring the entire tree, even to add a few hundred ports, is >>>simply not feasible with the level of volunteer effort we have and the >>>number of people that depend on the current structure worldwide. >>> >>>mcl >> >>Ok - building on your comments would my original suggestion, as modified >>below, and leaving aside for one moment the arguments as to whether or not >>committers might desire it,be capable of implementation without a >>restructuring of code? >> >>This proposal mean that /usr/ports/plugins/*.jar is a repository for files >>which are accessed solely via the meta-eclipsevx.xxx ports. >> >>I think this might shoehorn the necessary structure into the existing >>system. What do you think? >> >>/usr/ports/eclipse/eclipsemainv[x.xxx] Holds the main eclipse ports >>/usr/ports/eclipse/meta-eclipse[v.xxx] Holds eclipse plugins loader > > Just for sake of clarity the above are intended to be straight forward ports > > >>/usr/ports/eclipse/plugins/ Holds the *.jar files > > >>/usr/ports/eclipse/misc1 self contained eclipse > > ports > >>/usr/ports/eclipse/misc2 >>/usr/ports/eclipse/miscN >> >>/usr/ports/eclipse/plugins would, in effect, be a set of files which would >>be downloaded under control of the meta-eclipse loader >> >>If so why not use it - that would make eclipse a category which could >>enclose a number of ports for eclipse versions, a number >>of /usr/ports/eclipse/meta_eclipseplugin ports and each plugin would then >>(in effect) be a *.jar file file held within the /usr/eclipse/plugins >>directory. >>The meta_eclipse plugin could build the library of available plugins on the >>fly and use the standard system for registering the plugins on the local >>machine. In that way could the need be integrated into the existing system? >> >>Whatis your reaction? >> >>david I see various problems with your approach, let me try to identify a few. First of all, a plugin's jar file is essentially its distfile, currently downloaded by the ports system in ports/distfiles or its subdirectories. Storing it in the ports CVS repository (in ports/eclipse/plugins), as you seem to imply, would in some cases be problematic because of licensing/redistribution issues (not to mention bloat). Another thing is that many eclipse plugins have to be traditional ports since they require the ports infrastructure for their dependencies (see java/eclipseme for an example). Therefore they do not fit in the ports/eclipse/plugins case. Also, what is the point of treating plugins differently, with ports/eclipse/plugins and ports/eclipse/miscX? What do you gain by losing uniformity? Furthermore, you describe the need to create an eclipse plugin that lists the available plugins as FreeBSD ports and lets the user install one and register it as a regular system package. How is this better than eclipse's own plugin management method? I would go even further and ask why do you need FreeBSD-specific ports for most plugins? Why not simply install it via the internal GUI and be done with it? That way you get the usual Eclipse experience you see in other platforms. I am actually doing this myself and quite like it, to be honest. The tradeoff is that you get files under $PREFIX/eclipse that are not recorded in some package, but I'm OK with that. But consider this: you propose to create a new FreeBSD-specific plugin for eclipse, reorganize the ports tree, and change every existing eclipse plugin (to fit in the new scheme) in exchange for what? The registration in packages of every plugin _and_ a GUI plugin manager? When you could get either of those with the current system? Does the amount of effort needed, justify the gain? Let me state this once more, there is no eclipse-supported platform currently that provides what you propose. Therefore it cannot be considered a disadvantage for FreeBSD, either. Our forefathers said, that you should learn to walk, before running. Let's do that, shall we? Let's bring those 300+ plugins you mentioned into the ports system and see where we go from there. Let's get our system officially supported by eclipse.org so that FreeBSD gets more visibility and credibility. Let's work out the swt dependencies of various applications and be the first eclipse platform that does not contain swt libraries all over the place. What do you say? Cheers, Panagiotis From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 10:10:25 2005 Return-Path: X-Original-To: freebsd-eclipse@hub.freebsd.org Delivered-To: freebsd-eclipse@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A524316A41F for ; Wed, 31 Aug 2005 10:10:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 557FF43D48 for ; Wed, 31 Aug 2005 10:10:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7VAAOKm012045 for ; Wed, 31 Aug 2005 10:10:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7VAAOTH012044; Wed, 31 Aug 2005 10:10:24 GMT (envelope-from gnats) Date: Wed, 31 Aug 2005 10:10:24 GMT Message-Id: <200508311010.j7VAAOTH012044@freefall.freebsd.org> To: freebsd-eclipse@FreeBSD.org From: Vladimir Grebenschikov Cc: Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vladimir Grebenschikov List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 10:10:25 -0000 The following reply was made to PR ports/85501; it has been noted by GNATS. From: Vladimir Grebenschikov To: jgutie11@eafit.edu.co, bug-followup@FreeBSD.org Cc: Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse Date: Wed, 31 Aug 2005 14:00:35 +0400 Hi It is incomplete patch in bug, package can't be built with this patch: ===> Checking if java/eclipse-cdt already installed ===> Registering installation for eclipse-cdt-3.0.0 ===> Building package for eclipse-cdt-3.0.0 Creating package /usr/ports/packages/All/eclipse-cdt-3.0.0.tbz Registering depends: eclipse-3.1_1 libgnomeui-2.10.1_1 gnomekeyring-0.4.3_1 cairo-0.4.0 libbonoboui-2.10.1 libgnome-2.10.1 scrollkeeper-0.3.14_1,1 docbook-xsl-1.68.1 gnomevfs2-2.10.1 esound-0.2.36 gnome-icon-theme-2.10.1_1 fam-2.6.9_6 gnomemimedata-2.4.2 libgnomecanvas-2.10.2_1 gconf2-2.10.1 libbonobo-2.10.1 ORBit2-2.12.3 gnomehier-2.0_7 libglade2-2.5.1_2 gtk-2.6.10 jdk-1.4.2p7_1 libIDL-0.8.6 intltool-0.34.1 pango-1.8.2 howl-1.0.0 xorg-fonts-truetype-6.8.2 javavmwrapper-2.0_5 hicolor-icon-theme-0.5 tiff-3. 7.3 atk-1.9.1 libXft-2.1.7 libart_lgpl2-2.3.17 libaudiofile-0.2.6 libgcrypt-1.2.1_1 cdparanoia-3.9.8_7 linc-1.0.3_3 libgpg-error-1.0_1 startup-notification-0.8_1 p5-XML-Parser-2.34_1 docbook-sk-4.1.2_3 shared-mime-info-0.16_1 libxslt-1.1.14 libpixman-0.1.6 libxml2-2.6.20_1 popt-1.7 glib-2.6.6 openldap-client-2.2.27 openssl-0.9.7g urwfonts-1.0 bitstream-vera-1.10_1 perl-5.8.7 xorg-libraries-6.8.2 png-1.2.8_2 samba-libsmbclient-3.0.14a_2 python-2.4.1_3 gettext-0.14.5 docbook -x ml-4.2_1 sdocbook-xml-4.1.2.5_2 libiconv-1.9.2_1 fontconfig-2.2.3,1 jpeg-6b_3 freetype2-2.1.10_1 xmlcatmgr-2.2 xorg-fonts-encodings-6.8.2 pkgconfig-0.17.2 expat-1.95.8_3. Creating bzip'd tar ball in '/usr/ports/packages/All/eclipse-cdt-3.0.0.tbz' tar: eclipse/features/org.eclipse.cdt_3.0.0/cpl-v10.html: Cannot stat: No such file or directory tar: eclipse/plugins/org.eclipse.cdt.core.linux_3.0.0/os/linux/ia64/libpty.so: Cannot stat: No such file or directory tar: eclipse/plugins/org.eclipse.cdt.core.linux_3.0.0/os/linux/ia64/libspawner.so: Cannot stat: No such file or directory tar: eclipse/plugins/org.eclipse.cdt.core.linux_3.0.0/os/linux/ppc/libpty.so: Cannot stat: No such file or directory tar: eclipse/plugins/org.eclipse.cdt.core.linux_3.0.0/os/linux/ppc/libspawner.so: Cannot stat: No such file or directory tar: eclipse/plugins/org.eclipse.cdt.core.linux_3.0.0/os/linux/x86/libpty.so: Cannot stat: No such file or directory ... I guess pkg-plist should be updated also. -- Vladimir B. Grebenschikov SWsoft Inc. vova@sw-soft.com From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 11:40:20 2005 Return-Path: X-Original-To: freebsd-eclipse@hub.freebsd.org Delivered-To: freebsd-eclipse@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA3B416A41F for ; Wed, 31 Aug 2005 11:40:20 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57FA143D48 for ; Wed, 31 Aug 2005 11:40:20 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7VBeK2o026745 for ; Wed, 31 Aug 2005 11:40:20 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7VBeKjL026744; Wed, 31 Aug 2005 11:40:20 GMT (envelope-from gnats) Date: Wed, 31 Aug 2005 11:40:20 GMT Message-Id: <200508311140.j7VBeKjL026744@freefall.freebsd.org> To: freebsd-eclipse@FreeBSD.org From: Vladimir Grebenschikov Cc: Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vladimir Grebenschikov List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 11:40:20 -0000 The following reply was made to PR ports/85501; it has been noted by GNATS. From: Vladimir Grebenschikov To: jgutie11@eafit.edu.co, bug-followup@FreeBSD.org Cc: Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse Date: Wed, 31 Aug 2005 15:35:16 +0400 Also new cdt plug-in crash eclipse while indexing C++ project: % gdb /usr/local/jdk1.5.0/bin/java java.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"...(no debugging symbols found)... Core was generated by `java'. Program terminated with signal 6, Aborted. Reading symbols from /usr/lib/libpthread.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libpthread.so.2 Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so Reading symbols from /lib/libm.so.4...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.4 Reading symbols from /usr/local/jdk1.5.0/jre/lib/i386/native_threads/libhpi.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/jdk1.5.0/jre/lib/i386/native_threads/libhpi.so Reading symbols from /usr/local/jdk1.5.0/jre/lib/i386/libverify.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/jdk1.5.0/jre/lib/i386/libverify.so Reading symbols from /usr/local/jdk1.5.0/jre/lib/i386/libjava.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/jdk1.5.0/jre/lib/i386/libjava.so Reading symbols from /usr/local/jdk1.5.0/jre/lib/i386/libzip.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/jdk1.5.0/jre/lib/i386/libzip.so Reading symbols from /usr/local/jdk1.5.0/jre/lib/i386/libnet.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/jdk1.5.0/jre/lib/i386/libnet.so Reading symbols from /usr/local/jdk1.5.0/jre/lib/i386/libnio.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/jdk1.5.0/jre/lib/i386/libnio.so Reading symbols from /usr/home/vova/.eclipse/org.eclipse.platform_3.1.0/configuration/org.eclipse.osgi/bundles/81/1/.cp/libswt-pi-gtk-3138.so...(no debugging symbols found)...done. Loaded symbols for /usr/home/vova/.eclipse/org.eclipse.platform_3.1.0/configuration/org.eclipse.osgi/bundles/81/1/.cp/libswt-pi-gtk-3138.so Reading symbols from /usr/X11R6/lib/libgtk-x11-2.0.so.600...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libgtk-x11-2.0.so.600 Reading symbols from /usr/local/lib/libgthread-2.0.so.600...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libgthread-2.0.so.600 Reading symbols from /usr/X11R6/lib/libXtst.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libXtst.so.6 Reading symbols from /usr/X11R6/lib/libgdk_pixbuf-2.0.so.600...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libgdk_pixbuf-2.0.so.600 Reading symbols from /usr/X11R6/lib/libgdk-x11-2.0.so.600...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libgdk-x11-2.0.so.600 Reading symbols from /usr/X11R6/lib/libXrandr.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libXrandr.so.2 Reading symbols from /usr/X11R6/lib/libXi.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libXi.so.6 Reading symbols from /usr/X11R6/lib/libXinerama.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libXinerama.so.1 Reading symbols from /usr/X11R6/lib/libXfixes.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libXfixes.so.3 Reading symbols from /usr/X11R6/lib/libXcursor.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libXcursor.so.1 Reading symbols from /usr/local/lib/libgmodule-2.0.so.600...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libgmodule-2.0.so.600 Reading symbols from /usr/local/lib/libgobject-2.0.so.600...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libgobject-2.0.so.600 Reading symbols from /usr/X11R6/lib/libpangoxft-1.0.so.800...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libpangoxft-1.0.so.800 Reading symbols from /usr/X11R6/lib/libXft.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libXft.so.2 Reading symbols from /usr/local/lib/libfreetype.so.9...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libfreetype.so.9 Reading symbols from /lib/libz.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.3 Reading symbols from /usr/X11R6/lib/libXrender.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libXrender.so.1 Reading symbols from /usr/X11R6/lib/libXext.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libXext.so.6 Reading symbols from /usr/X11R6/lib/libpangox-1.0.so.800...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libpangox-1.0.so.800 Reading symbols from /usr/X11R6/lib/libX11.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libX11.so.6 Reading symbols from /usr/local/lib/libatk-1.0.so.901...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libatk-1.0.so.901 Reading symbols from /usr/local/lib/libintl.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libintl.so.6 Reading symbols from /usr/local/lib/libglib-2.0.so.600...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libglib-2.0.so.600 Reading symbols from /usr/X11R6/lib/libpangoft2-1.0.so.800...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libpangoft2-1.0.so.800 Reading symbols from /usr/X11R6/lib/libpango-1.0.so.800...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libpango-1.0.so.800 Reading symbols from /usr/local/lib/libiconv.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libiconv.so.3 Reading symbols from /usr/X11R6/lib/libfontconfig.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libfontconfig.so.1 Reading symbols from /lib/libz.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.2 Reading symbols from /usr/local/lib/libexpat.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libexpat.so.5 Reading symbols from /usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2 Reading symbols from /usr/home/vova/.eclipse/org.eclipse.platform_3.1.0/configuration/org.eclipse.osgi/bundles/81/1/.cp/libswt-gtk-3138.so...(no debugging symbols found)...done. Loaded symbols for /usr/home/vova/.eclipse/org.eclipse.platform_3.1.0/configuration/org.eclipse.osgi/bundles/81/1/.cp/libswt-gtk-3138.so Reading symbols from /usr/X11R6/lib/gtk-2.0/2.4.0/engines/libpixmap.so...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/gtk-2.0/2.4.0/engines/libpixmap.so Reading symbols from /usr/X11R6/lib/gtk-2.0/2.4.0/loaders/libpixbufloader-png.so...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/gtk-2.0/2.4.0/loaders/libpixbufloader-png.so Reading symbols from /usr/local/lib/libpng.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libpng.so.5 Reading symbols from /lib/libm.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.3 Reading symbols from /usr/home/vova/.eclipse/org.eclipse.platform_3.1.0/configuration/org.eclipse.osgi/bundles/25/1/.cp/os/freebsd/x86/libcore_3_1_0.so...(no debugging symbols found)...done. Loaded symbols for /usr/home/vova/.eclipse/org.eclipse.platform_3.1.0/configuration/org.eclipse.osgi/bundles/25/1/.cp/os/freebsd/x86/libcore_3_1_0.so Reading symbols from /usr/X11R6/lib/pango/1.4.0/modules/pango-basic-fc.so...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/pango/1.4.0/modules/pango-basic-fc.so Reading symbols from /usr/home/vova/.eclipse/org.eclipse.platform_3.1.0/configuration/org.eclipse.osgi/bundles/81/1/.cp/libswt-gnome-gtk-3138.so...(no debugging symbols found)...done. Loaded symbols for /usr/home/vova/.eclipse/org.eclipse.platform_3.1.0/configuration/org.eclipse.osgi/bundles/81/1/.cp/libswt-gnome-gtk-3138.so Reading symbols from /usr/X11R6/lib/libgnomevfs-2.so.1000...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libgnomevfs-2.so.1000 Reading symbols from /usr/X11R6/lib/libgnome-2.so.1000...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libgnome-2.so.1000 Reading symbols from /usr/X11R6/lib/libgnomeui-2.so.1000...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libgnomeui-2.so.1000 Reading symbols from /usr/X11R6/lib/libgconf-2.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libgconf-2.so.5 Reading symbols from /usr/local/lib/libbonobo-activation.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libbonobo-activation.so.4 Reading symbols from /usr/local/lib/libbonobo-2.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libbonobo-2.so.0 Reading symbols from /usr/local/lib/libORBit-2.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libORBit-2.so.0 Reading symbols from /usr/local/lib/libxml2.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libxml2.so.5 Reading symbols from /usr/lib/libssl.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libssl.so.3 Reading symbols from /lib/libcrypto.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypto.so.3 Reading symbols from /usr/local/lib/libhowl.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libhowl.so.0 Reading symbols from /usr/local/lib/libesd.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libesd.so.2 Reading symbols from /usr/local/lib/libaudiofile.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libaudiofile.so.0 Reading symbols from /usr/local/lib/libpopt.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libpopt.so.0 Reading symbols from /usr/X11R6/lib/libgnomecanvas-2.so.1000...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libgnomecanvas-2.so.1000 Reading symbols from /usr/X11R6/lib/libbonoboui-2.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libbonoboui-2.so.0 Reading symbols from /usr/X11R6/lib/libgnome-keyring.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libgnome-keyring.so.0 Reading symbols from /usr/local/lib/libjpeg.so.9...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libjpeg.so.9 Reading symbols from /usr/X11R6/lib/libSM.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libSM.so.6 Reading symbols from /usr/X11R6/lib/libICE.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/libICE.so.6 Reading symbols from /usr/local/lib/libORBitCosNaming-2.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libORBitCosNaming-2.so.0 Reading symbols from /usr/local/lib/libart_lgpl_2.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libart_lgpl_2.so.5 Reading symbols from /usr/X11R6/lib/gnome-vfs-2.0/modules/libfile.so...(no debugging symbols found)...done. Loaded symbols for /usr/X11R6/lib/gnome-vfs-2.0/modules/libfile.so Reading symbols from /usr/local/lib/libfam.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libfam.so.0 Reading symbols from /usr/lib/libstdc++.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libstdc++.so.4 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x2809d1ef in pthread_testcancel () from /usr/lib/libpthread.so.2 [New Thread 0x8c20a00 (sleeping)] [New Thread 0x8368e00 (sleeping)] [New Thread 0x9115400 (sleeping)] [New Thread 0x822dc00 (sleeping)] [New Thread 0x8e91400 (sleeping)] [New Thread 0x910a600 (sleeping)] [New Thread 0x81e1400 (sleeping)] [New Thread 0x910ae00 (sleeping)] [New Thread 0x910aa00 (sleeping)] [New Thread 0x8d23a00 (sleeping)] [New Thread 0x8d22000 (LWP 100221)] [New Thread 0x848e000 (sleeping)] [New Thread 0x847ea00 (sleeping)] [New Thread 0x847e200 (sleeping)] [New Thread 0x815f200 (sleeping)] [New Thread 0x813fe00 (sleeping)] [New Thread 0x813fa00 (sleeping)] [New Thread 0x813f600 (sleeping)] [New Thread 0x813f200 (sleeping)] [New Thread 0x806be00 (sleeping)] [New Thread 0x806ba00 (sleeping)] [New Thread 0x806b800 (LWP 100182)] [New Thread 0x8060000 (runnable)] (gdb) (gdb) bt #0 0x2809d1ef in pthread_testcancel () from /usr/lib/libpthread.so.2 #1 0x2808c646 in sigaction () from /usr/lib/libpthread.so.2 #2 0x280866c5 in pthread_kill () from /usr/lib/libpthread.so.2 #3 0x280860d2 in raise () from /usr/lib/libpthread.so.2 #4 0x28154630 in abort () from /lib/libc.so.6 #5 0x284d2193 in os::abort () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so #6 0x2855d5ed in VMError::report_and_die () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so #7 0x28395fcb in report_fatal () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so #8 0x284d0575 in ThreadLocalStorage::get_thread_via_cache_slowly () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so #9 0x282a22b9 in ThreadLocalStorage::thread () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so #10 0x28493b8d in JvmtiEventCollector::unset_jvmti_thread_state () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so #11 0x2849436e in JvmtiVMObjectAllocEventCollector::~JvmtiVMObjectAllocEventCollector () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so #12 0x2843926b in JVM_NewArray () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so #13 0x2861c0f9 in Java_java_lang_reflect_Array_newArray () from /usr/local/jdk1.5.0/jre/lib/i386/libjava.so #14 0x2b40821c in ?? () #15 0x08d236bc in ?? () #16 0xbf570f5c in ?? () #17 0xbf570f6c in ?? () #18 0x00000002 in ?? () #19 0x2d1534c8 in ?? () #20 0x58efafe0 in ?? () #21 0xbf570f98 in ?? () #22 0x2b3e205d in ?? () #23 0x00000002 in ?? () #24 0x5a62b2d8 in ?? () #25 0x00000000 in ?? () #26 0x0000000a in ?? () #27 0x00000000 in ?? () #28 0x31a51b78 in ?? () #29 0x2d1534c8 in ?? () #30 0x5a67b2a8 in ?? () #31 0x00000002 in ?? () #32 0x5a62b2d8 in ?? () #33 0x00000000 in ?? () #34 0x2b6bef41 in ?? () #35 0xbf571010 in ?? () #36 0x2b6bf13f in ?? () #37 0x2d153480 in ?? () #38 0x00000000 in ?? () #39 0x5a62b2d8 in ?? () #40 0x2d1534c8 in ?? () #41 0x2d161334 in ?? () #42 0x5a67c1e0 in ?? () #43 0x00000006 in ?? () #44 0x5a5f63b0 in ?? () #45 0x324fce48 in ?? () #46 0x28089c02 in pthread_getspecific () from /usr/lib/libpthread.so.2 Previous frame inner to this frame (corrupt stack?) (gdb) -- Vladimir B. Grebenschikov SWsoft Inc. vova@sw-soft.com From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 15:20:10 2005 Return-Path: X-Original-To: freebsd-eclipse@hub.freebsd.org Delivered-To: freebsd-eclipse@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17B3A16A41F for ; Wed, 31 Aug 2005 15:20:10 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65AF143D48 for ; Wed, 31 Aug 2005 15:20:09 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7VFK9F6058570 for ; Wed, 31 Aug 2005 15:20:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7VFK8ve058569; Wed, 31 Aug 2005 15:20:08 GMT (envelope-from gnats) Date: Wed, 31 Aug 2005 15:20:08 GMT Message-Id: <200508311520.j7VFK8ve058569@freefall.freebsd.org> To: freebsd-eclipse@FreeBSD.org From: Jorge Mario Mazo Cc: Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jorge Mario Mazo List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 15:20:10 -0000 The following reply was made to PR ports/85501; it has been noted by GNATS. From: Jorge Mario Mazo To: Vladimir Grebenschikov Cc: past@ebs.gr, bug-followup@FreeBSD.org Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse Date: Wed, 31 Aug 2005 10:16:21 -0500 On Wed, 2005-08-31 at 15:35 +0400, Vladimir Grebenschikov wrote: > Also new cdt plug-in crash eclipse while indexing C++ project: > > % gdb /usr/local/jdk1.5.0/bin/java java.core > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-marcel-freebsd"...(no debugging symbols found)... > Core was generated by `java'. > Program terminated with signal 6, Aborted. > Reading symbols from /usr/lib/libpthread.so.2...(no debugging symbols found)...done. > Loaded symbols for /usr/lib/libpthread.so.2 > Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done. > Loaded symbols for /lib/libc.so.6 > Reading symbols from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so...(no debugging symbols found)...done. > Loaded symbols for /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so > Reading symbols from /lib/libm.so.4...(no debugging symbols found)...done. > Loaded symbols for /lib/libm.so.4 > Reading symbols from /usr/local/jdk1.5.0/jre/lib/i386/native_threads/libhpi.so...(no debugging symbols found)...done. > Loaded symbols for /usr/local/jdk1.5.0/jre/lib/i386/native_threads/libhpi.so > Reading symbols from /usr/local/jdk1.5.0/jre/lib/i386/libverify.so...(no debugging symbols found)...done. > Loaded symbols for /usr/local/jdk1.5.0/jre/lib/i386/libverify.so > Reading symbols from /usr/local/jdk1.5.0/jre/lib/i386/libjava.so...(no debugging symbols found)...done. > Loaded symbols for /usr/local/jdk1.5.0/jre/lib/i386/libjava.so > Reading symbols from /usr/local/jdk1.5.0/jre/lib/i386/libzip.so...(no debugging symbols found)...done. > Loaded symbols for /usr/local/jdk1.5.0/jre/lib/i386/libzip.so > Reading symbols from /usr/local/jdk1.5.0/jre/lib/i386/libnet.so...(no debugging symbols found)...done. > Loaded symbols for /usr/local/jdk1.5.0/jre/lib/i386/libnet.so > Reading symbols from /usr/local/jdk1.5.0/jre/lib/i386/libnio.so...(no debugging symbols found)...done. > Loaded symbols for /usr/local/jdk1.5.0/jre/lib/i386/libnio.so > Reading symbols from /usr/home/vova/.eclipse/org.eclipse.platform_3.1.0/configuration/org.eclipse.osgi/bundles/81/1/.cp/libswt-pi-gtk-3138.so...(no debugging symbols found)...done. > Loaded symbols for /usr/home/vova/.eclipse/org.eclipse.platform_3.1.0/configuration/org.eclipse.osgi/bundles/81/1/.cp/libswt-pi-gtk-3138.so > Reading symbols from /usr/X11R6/lib/libgtk-x11-2.0.so.600...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libgtk-x11-2.0.so.600 > Reading symbols from /usr/local/lib/libgthread-2.0.so.600...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libgthread-2.0.so.600 > Reading symbols from /usr/X11R6/lib/libXtst.so.6...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libXtst.so.6 > Reading symbols from /usr/X11R6/lib/libgdk_pixbuf-2.0.so.600...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libgdk_pixbuf-2.0.so.600 > Reading symbols from /usr/X11R6/lib/libgdk-x11-2.0.so.600...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libgdk-x11-2.0.so.600 > Reading symbols from /usr/X11R6/lib/libXrandr.so.2...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libXrandr.so.2 > Reading symbols from /usr/X11R6/lib/libXi.so.6...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libXi.so.6 > Reading symbols from /usr/X11R6/lib/libXinerama.so.1...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libXinerama.so.1 > Reading symbols from /usr/X11R6/lib/libXfixes.so.3...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libXfixes.so.3 > Reading symbols from /usr/X11R6/lib/libXcursor.so.1...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libXcursor.so.1 > Reading symbols from /usr/local/lib/libgmodule-2.0.so.600...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libgmodule-2.0.so.600 > Reading symbols from /usr/local/lib/libgobject-2.0.so.600...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libgobject-2.0.so.600 > Reading symbols from /usr/X11R6/lib/libpangoxft-1.0.so.800...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libpangoxft-1.0.so.800 > Reading symbols from /usr/X11R6/lib/libXft.so.2...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libXft.so.2 > Reading symbols from /usr/local/lib/libfreetype.so.9...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libfreetype.so.9 > Reading symbols from /lib/libz.so.3...(no debugging symbols found)...done. > Loaded symbols for /lib/libz.so.3 > Reading symbols from /usr/X11R6/lib/libXrender.so.1...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libXrender.so.1 > Reading symbols from /usr/X11R6/lib/libXext.so.6...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libXext.so.6 > Reading symbols from /usr/X11R6/lib/libpangox-1.0.so.800...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libpangox-1.0.so.800 > Reading symbols from /usr/X11R6/lib/libX11.so.6...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libX11.so.6 > Reading symbols from /usr/local/lib/libatk-1.0.so.901...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libatk-1.0.so.901 > Reading symbols from /usr/local/lib/libintl.so.6...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libintl.so.6 > Reading symbols from /usr/local/lib/libglib-2.0.so.600...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libglib-2.0.so.600 > Reading symbols from /usr/X11R6/lib/libpangoft2-1.0.so.800...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libpangoft2-1.0.so.800 > Reading symbols from /usr/X11R6/lib/libpango-1.0.so.800...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libpango-1.0.so.800 > Reading symbols from /usr/local/lib/libiconv.so.3...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libiconv.so.3 > Reading symbols from /usr/X11R6/lib/libfontconfig.so.1...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libfontconfig.so.1 > Reading symbols from /lib/libz.so.2...(no debugging symbols found)...done. > Loaded symbols for /lib/libz.so.2 > Reading symbols from /usr/local/lib/libexpat.so.5...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libexpat.so.5 > Reading symbols from /usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2 > Reading symbols from /usr/home/vova/.eclipse/org.eclipse.platform_3.1.0/configuration/org.eclipse.osgi/bundles/81/1/.cp/libswt-gtk-3138.so...(no debugging symbols found)...done. > Loaded symbols for /usr/home/vova/.eclipse/org.eclipse.platform_3.1.0/configuration/org.eclipse.osgi/bundles/81/1/.cp/libswt-gtk-3138.so > Reading symbols from /usr/X11R6/lib/gtk-2.0/2.4.0/engines/libpixmap.so...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/gtk-2.0/2.4.0/engines/libpixmap.so > Reading symbols from /usr/X11R6/lib/gtk-2.0/2.4.0/loaders/libpixbufloader-png.so...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/gtk-2.0/2.4.0/loaders/libpixbufloader-png.so > Reading symbols from /usr/local/lib/libpng.so.5...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libpng.so.5 > Reading symbols from /lib/libm.so.3...(no debugging symbols found)...done. > Loaded symbols for /lib/libm.so.3 > Reading symbols from /usr/home/vova/.eclipse/org.eclipse.platform_3.1.0/configuration/org.eclipse.osgi/bundles/25/1/.cp/os/freebsd/x86/libcore_3_1_0.so...(no debugging symbols found)...done. > Loaded symbols for /usr/home/vova/.eclipse/org.eclipse.platform_3.1.0/configuration/org.eclipse.osgi/bundles/25/1/.cp/os/freebsd/x86/libcore_3_1_0.so > Reading symbols from /usr/X11R6/lib/pango/1.4.0/modules/pango-basic-fc.so...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/pango/1.4.0/modules/pango-basic-fc.so > Reading symbols from /usr/home/vova/.eclipse/org.eclipse.platform_3.1.0/configuration/org.eclipse.osgi/bundles/81/1/.cp/libswt-gnome-gtk-3138.so...(no debugging symbols found)...done. > Loaded symbols for /usr/home/vova/.eclipse/org.eclipse.platform_3.1.0/configuration/org.eclipse.osgi/bundles/81/1/.cp/libswt-gnome-gtk-3138.so > Reading symbols from /usr/X11R6/lib/libgnomevfs-2.so.1000...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libgnomevfs-2.so.1000 > Reading symbols from /usr/X11R6/lib/libgnome-2.so.1000...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libgnome-2.so.1000 > Reading symbols from /usr/X11R6/lib/libgnomeui-2.so.1000...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libgnomeui-2.so.1000 > Reading symbols from /usr/X11R6/lib/libgconf-2.so.5...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libgconf-2.so.5 > Reading symbols from /usr/local/lib/libbonobo-activation.so.4...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libbonobo-activation.so.4 > Reading symbols from /usr/local/lib/libbonobo-2.so.0...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libbonobo-2.so.0 > Reading symbols from /usr/local/lib/libORBit-2.so.0...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libORBit-2.so.0 > Reading symbols from /usr/local/lib/libxml2.so.5...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libxml2.so.5 > Reading symbols from /usr/lib/libssl.so.3...(no debugging symbols found)...done. > Loaded symbols for /usr/lib/libssl.so.3 > Reading symbols from /lib/libcrypto.so.3...(no debugging symbols found)...done. > Loaded symbols for /lib/libcrypto.so.3 > Reading symbols from /usr/local/lib/libhowl.so.0...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libhowl.so.0 > Reading symbols from /usr/local/lib/libesd.so.2...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libesd.so.2 > Reading symbols from /usr/local/lib/libaudiofile.so.0...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libaudiofile.so.0 > Reading symbols from /usr/local/lib/libpopt.so.0...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libpopt.so.0 > Reading symbols from /usr/X11R6/lib/libgnomecanvas-2.so.1000...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libgnomecanvas-2.so.1000 > Reading symbols from /usr/X11R6/lib/libbonoboui-2.so.0...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libbonoboui-2.so.0 > Reading symbols from /usr/X11R6/lib/libgnome-keyring.so.0...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libgnome-keyring.so.0 > Reading symbols from /usr/local/lib/libjpeg.so.9...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libjpeg.so.9 > Reading symbols from /usr/X11R6/lib/libSM.so.6...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libSM.so.6 > Reading symbols from /usr/X11R6/lib/libICE.so.6...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/libICE.so.6 > Reading symbols from /usr/local/lib/libORBitCosNaming-2.so.0...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libORBitCosNaming-2.so.0 > Reading symbols from /usr/local/lib/libart_lgpl_2.so.5...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libart_lgpl_2.so.5 > Reading symbols from /usr/X11R6/lib/gnome-vfs-2.0/modules/libfile.so...(no debugging symbols found)...done. > Loaded symbols for /usr/X11R6/lib/gnome-vfs-2.0/modules/libfile.so > Reading symbols from /usr/local/lib/libfam.so.0...(no debugging symbols found)...done. > Loaded symbols for /usr/local/lib/libfam.so.0 > Reading symbols from /usr/lib/libstdc++.so.4...(no debugging symbols found)...done. > Loaded symbols for /usr/lib/libstdc++.so.4 > Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. > Loaded symbols for /libexec/ld-elf.so.1 > #0 0x2809d1ef in pthread_testcancel () from /usr/lib/libpthread.so.2 > [New Thread 0x8c20a00 (sleeping)] > [New Thread 0x8368e00 (sleeping)] > [New Thread 0x9115400 (sleeping)] > [New Thread 0x822dc00 (sleeping)] > [New Thread 0x8e91400 (sleeping)] > [New Thread 0x910a600 (sleeping)] > [New Thread 0x81e1400 (sleeping)] > [New Thread 0x910ae00 (sleeping)] > [New Thread 0x910aa00 (sleeping)] > [New Thread 0x8d23a00 (sleeping)] > [New Thread 0x8d22000 (LWP 100221)] > [New Thread 0x848e000 (sleeping)] > [New Thread 0x847ea00 (sleeping)] > [New Thread 0x847e200 (sleeping)] > [New Thread 0x815f200 (sleeping)] > [New Thread 0x813fe00 (sleeping)] > [New Thread 0x813fa00 (sleeping)] > [New Thread 0x813f600 (sleeping)] > [New Thread 0x813f200 (sleeping)] > [New Thread 0x806be00 (sleeping)] > [New Thread 0x806ba00 (sleeping)] > [New Thread 0x806b800 (LWP 100182)] > [New Thread 0x8060000 (runnable)] > (gdb) (gdb) bt > #0 0x2809d1ef in pthread_testcancel () from /usr/lib/libpthread.so.2 > #1 0x2808c646 in sigaction () from /usr/lib/libpthread.so.2 > #2 0x280866c5 in pthread_kill () from /usr/lib/libpthread.so.2 > #3 0x280860d2 in raise () from /usr/lib/libpthread.so.2 > #4 0x28154630 in abort () from /lib/libc.so.6 > #5 0x284d2193 in os::abort () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so > #6 0x2855d5ed in VMError::report_and_die () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so > #7 0x28395fcb in report_fatal () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so > #8 0x284d0575 in ThreadLocalStorage::get_thread_via_cache_slowly () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so > #9 0x282a22b9 in ThreadLocalStorage::thread () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so > #10 0x28493b8d in JvmtiEventCollector::unset_jvmti_thread_state () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so > #11 0x2849436e in JvmtiVMObjectAllocEventCollector::~JvmtiVMObjectAllocEventCollector () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so > #12 0x2843926b in JVM_NewArray () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so > #13 0x2861c0f9 in Java_java_lang_reflect_Array_newArray () from /usr/local/jdk1.5.0/jre/lib/i386/libjava.so > #14 0x2b40821c in ?? () > #15 0x08d236bc in ?? () > #16 0xbf570f5c in ?? () > #17 0xbf570f6c in ?? () > #18 0x00000002 in ?? () > #19 0x2d1534c8 in ?? () > #20 0x58efafe0 in ?? () > #21 0xbf570f98 in ?? () > #22 0x2b3e205d in ?? () > #23 0x00000002 in ?? () > #24 0x5a62b2d8 in ?? () > #25 0x00000000 in ?? () > #26 0x0000000a in ?? () > #27 0x00000000 in ?? () > #28 0x31a51b78 in ?? () > #29 0x2d1534c8 in ?? () > #30 0x5a67b2a8 in ?? () > #31 0x00000002 in ?? () > #32 0x5a62b2d8 in ?? () > #33 0x00000000 in ?? () > #34 0x2b6bef41 in ?? () > #35 0xbf571010 in ?? () > #36 0x2b6bf13f in ?? () > #37 0x2d153480 in ?? () > #38 0x00000000 in ?? () > #39 0x5a62b2d8 in ?? () > #40 0x2d1534c8 in ?? () > #41 0x2d161334 in ?? () > #42 0x5a67c1e0 in ?? () > #43 0x00000006 in ?? () > #44 0x5a5f63b0 in ?? () > #45 0x324fce48 in ?? () > #46 0x28089c02 in pthread_getspecific () from /usr/lib/libpthread.so.2 > Previous frame inner to this frame (corrupt stack?) > (gdb) Hi there there seems to be a better patch for upgrade! check PR ports/85300 . About the bug, that bug it's been there for ages! I have reported it (on mailing lists and such) and noone seems to care. By the way it hapens with java projects for me as well "We" would really like to see this fixed since there is no "professional" IDE for FreeBSD (eclipse works half-assed, anjuta is too old and the new version does not compile, and Kdevelop it's not an option for us) and boss it's starting to bitch and talking about switching to Linux :( Is there other site where we could move this thread? I can send debuggin information try patches and such. -- [jorge@verde:/usr/home/jorge]$ java -version java version "1.4.2-p7" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-p7-root_27_mar_2005_14_22) Java HotSpot(TM) Client VM (build 1.4.2-p7-root_27_mar_2005_14_22, mixed mode) [jorge@verde:/usr/home/jorge]$ From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 15:33:07 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BE9A16A41F; Wed, 31 Aug 2005 15:33:07 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from lakecmmtao04.coxmail.com (lakecmmtao04.coxmail.com [68.99.120.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87EC643D48; Wed, 31 Aug 2005 15:33:06 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from dns1 ([64.58.171.82]) by lakecmmtao04.coxmail.com (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20050831153306.ZTQN3947.lakecmmtao04.coxmail.com@dns1>; Wed, 31 Aug 2005 11:33:06 -0400 From: Vizion To: Panagiotis Astithas Date: Wed, 31 Aug 2005 08:29:02 -0700 User-Agent: KMail/1.8 References: <200508251303.59453.vizion@vizion.occoxmail.com> <200508301927.31549.vizion@vizion.occoxmail.com> <43156772.7070808@ebs.gr> In-Reply-To: <43156772.7070808@ebs.gr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508310829.03121.vizion@vizion.occoxmail.com> Cc: Mark Linimon , Herve Quiroz , freebsd-eclipse@freebsd.org Subject: Re: How should eclipse be organized in the ports tree? X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 15:33:07 -0000 On Wednesday 31 August 2005 01:16, the author Panagiotis Astithas contributed to the dialogue on- Re: How should eclipse be organized in the ports tree?: >Vizion wrote: >> On Tuesday 30 August 2005 16:15, the author Vizion contributed to the >> dialogue on- >> >> Re: How should eclipse be organized in the ports tree?: >>>On Tuesday 30 August 2005 14:23, the author Mark Linimon contributed to >>> the dialogue on- >>>Re: Eclipse as part of the ports/java tree? [Was freebsd eclipse plugins & >>> >>>mailing list]: >>>>On Tue, Aug 30, 2005 at 10:10:26AM -0700, Vizion wrote: >>>>>I am now faced with the question is the ports tree as inflexible as some >>>>>people suggest or are some members of our meritocracy more inflexible >>>>>than the freebsd assets? >>>> >>>>This is a complete oversimplification of the situation. >>>> >>>>There are some hard-coded assumptions in the ports tree -- one of which >>>> is that there are two levels, categories and ports -- and these >>>> assumptions are mirrored in the repositories of tens of thousands if not >>>> hundreds of thousands of users, and thousands of lines of shell scripts >>>> and database programs that create the binary packages and monitor the >>>> results of those build processes. >>>> >>>>So when you suggest that the only way that Eclipse can be supported is >>>>to have a multilevel ports tree -- as you are seeming to -- you are >>>> clearly totally misunderestimating the amount of effort involved. >>>> >>>>In your most recent email I think you are finally getting a lot closer to >>>>what I consider 'real' problem. IMHO the interesting problems you want >>>> to solve are the 'search' and 'browse' problems. Directory names >>>> controlled by CVS structures in an unbranched tree, which are then >>>> mirrored all around the world, are really poor paradigms for these >>>> problems. Herve has suggested some better tools for these which are >>>> better ways to think about these problems and you should look at those. >>>> We certainly need more. >>>> >>>>The meta-plugin idea is also worth considering. >>>> >>>>But restructuring the entire tree, even to add a few hundred ports, is >>>>simply not feasible with the level of volunteer effort we have and the >>>>number of people that depend on the current structure worldwide. >>>> >>>>mcl >>> >>>Ok - building on your comments would my original suggestion, as modified >>>below, and leaving aside for one moment the arguments as to whether or not >>>committers might desire it,be capable of implementation without a >>>restructuring of code? >>> >>>This proposal mean that /usr/ports/plugins/*.jar is a repository for files >>>which are accessed solely via the meta-eclipsevx.xxx ports. >>> >>>I think this might shoehorn the necessary structure into the existing >>>system. What do you think? >>> >>>/usr/ports/eclipse/eclipsemainv[x.xxx] Holds the main eclipse ports >>>/usr/ports/eclipse/meta-eclipse[v.xxx] Holds eclipse plugins loader >> >> Just for sake of clarity the above are intended to be straight forward >> ports >> >>>/usr/ports/eclipse/plugins/ Holds the *.jar files >>> >>> >>>/usr/ports/eclipse/misc1 self contained eclipse >> >> ports >> >>>/usr/ports/eclipse/misc2 >>>/usr/ports/eclipse/miscN >>> >>>/usr/ports/eclipse/plugins would, in effect, be a set of files which would >>>be downloaded under control of the meta-eclipse loader >>> >>>If so why not use it - that would make eclipse a category which could >>>enclose a number of ports for eclipse versions, a number >>>of /usr/ports/eclipse/meta_eclipseplugin ports and each plugin would >>> then (in effect) be a *.jar file file held within the >>> /usr/eclipse/plugins directory. >>>The meta_eclipse plugin could build the library of available plugins on >>> the fly and use the standard system for registering the plugins on the >>> local machine. In that way could the need be integrated into the existing >>> system? >>> >>>Whatis your reaction? >>> >>>david > >I see various problems with your approach, let me try to identify a few. > >First of all, a plugin's jar file is essentially its distfile, currently >downloaded by the ports system in ports/distfiles or its subdirectories. >Storing it in the ports CVS repository (in ports/eclipse/plugins), as >you seem to imply, would in some cases be problematic because of >licensing/redistribution issues (not to mention bloat). > >Another thing is that many eclipse plugins have to be traditional ports >since they require the ports infrastructure for their dependencies (see >java/eclipseme for an example). Therefore they do not fit in the >ports/eclipse/plugins case. Also, what is the point of treating plugins >differently, with ports/eclipse/plugins and ports/eclipse/miscX? What do >you gain by losing uniformity? The ability dramatically reduce the amount of work necessary to bring ALL available opensource eclipse plugins into the ports tree. By getting the plugins into their own directory we can take advantage of eclipse's inbuilt mechanism for importing plugins. By taking this approach all necessary moodifications can be contained within a pluginloader module and the *.jarcould, in the majority of cases, be the standard eclipse .jar file with little modification. > >Furthermore, you describe the need to create an eclipse plugin that >lists the available plugins as FreeBSD ports and lets the user install >one and register it as a regular system package. How is this better than >eclipse's own plugin management method? Currently plugins are scattered on different internet sites. The majority are open source with no restrictions on redistribution if they are unmodified. By bringing them together in one place we provide not only >I would go even further and ask >why do you need FreeBSD-specific ports for most plugins? Why not simply >install it via the internal GUI and be done with it? That way you get >the usual Eclipse experience you see in other platforms. I am actually >doing this myself and quite like it, to be honest. The tradeoff is that >you get files under $PREFIX/eclipse that are not recorded in some >package, but I'm OK with that. That is fine for single user but where you have multiple users you need to be able to have a single system to ensure the whole team are using the same plugin version. Freebsd offers a huge advantage in the its ports mechanism for update and control of ports. I see the pluginloader provider another gui into the package system. >But consider this: you propose to create >a new FreeBSD-specific plugin for eclipse, reorganize the ports tree, I see no reason to reorganize the ports tree. The only drawback seems to be a quasi-religious objection to making eclipse a category in the ports tree. >and change every existing eclipse plugin (to fit in the new scheme) I have read what is available and as far as I can see there is the potential to do this without changing the vast majority of plugins that have not yet been incorprated in the ports tree. >in >exchange for what? The registration in packages of every plugin _and_ a >GUI plugin manager? When you could get either of those with the current >system? Does the amount of effort needed, justify the gain? Yes we get a rapid integration into the ports tree of all the eclipse plugins. > >Let me state this once more, there is no eclipse-supported platform >currently that provides what you propose. Therefore it cannot be >considered a disadvantage for FreeBSD, either. Our forefathers said, >that you should learn to walk, before running. Let's do that, shall we? >Let's bring those 300+ plugins you mentioned into the ports system and >see where we go from there. We could do that but the amount of work needed going that route is far greater than the work involved in developing a generic eclipse loader by adding additonal plugin feature to eclipse's own loader... think about it. >Let's get our system officially supported by >eclipse.org so that FreeBSD gets more visibility and credibility. Let's >work out the swt dependencies of various applications and be the first >eclipse platform that does not contain swt libraries all over the place. > >What do you say? > > >Cheers, > >Panagiotis -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 15:41:43 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A69316A41F; Wed, 31 Aug 2005 15:41:43 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from lakecmmtao05.coxmail.com (lakecmmtao05.coxmail.com [68.99.120.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0D6143D48; Wed, 31 Aug 2005 15:41:40 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from dns1 ([64.58.171.82]) by lakecmmtao05.coxmail.com (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20050831154140.XFPR2425.lakecmmtao05.coxmail.com@dns1>; Wed, 31 Aug 2005 11:41:40 -0400 From: Vizion To: freebsd-java@freebsd.org, freebsd-eclipse@freebsd.org Date: Wed, 31 Aug 2005 08:37:36 -0700 User-Agent: KMail/1.8 References: <20050831120023.56A8916A44A@hub.freebsd.org> <20050831072640.R83235@roble.com> <200508310832.43657.vizion@vizion.occoxmail.com> In-Reply-To: <200508310832.43657.vizion@vizion.occoxmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508310837.37530.vizion@vizion.occoxmail.com> Cc: Roger Marquis Subject: Re: How should eclipse be organized in the ports tree? X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 15:41:43 -0000 On Wednesday 31 August 2005 08:32, the author Vizion contributed to the dialogue on- Re: Eclipse as part of the ports/java tree?: -- thread in freebsd-eclipse >On Wednesday 31 August 2005 07:48, the author Roger Marquis contributed to >the dialogue on- > > Re: Eclipse as part of the ports/java tree?: >>Vizion wrote: >>> I am now faced with the question is the ports tree as inflexible as some >>> people suggest or are some members of our meritocracy more inflexible >>> than the freebsd assets? >> >>What you see as inflexibility the rest of us see as structure. Sure >>it would be nice to insert a goto on occasion but, from a long-term >>perspective, the existing structure is better. >> >>Mark Linimon wrote: >>> In your most recent email I think you are finally getting a lot closer to >>> what I consider 'real' problem. IMHO the interesting problems you want >>> to solve are the 'search' and 'browse' problems. >> >>This is a good point, and a legitimate issue. One solution might be >>to move or symlink portsearch from /usr/ports/Tools/scripts to >>/usr/local/bin. >> >>If consolidation is in order why not follow the p5- example/standard >>and use the devel directory but rename the ports themselves to use an >>appropriate prefix (ports/devel/eclipse{,_plugin}-$plugin)? > >The main problem is that to harness eclipse's own plugin loaderwe need to > have plugins in their own directory. If we can achieve that then we use the > standard eclipse *.jar files wiothiout modification and speed up the > process of getting the plugins into the port tree. It is the sole directory > issue that is the problem. -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 15:55:55 2005 Return-Path: X-Original-To: freebsd-eclipse@hub.freebsd.org Delivered-To: freebsd-eclipse@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03D9A16A41F; Wed, 31 Aug 2005 15:55:55 +0000 (GMT) (envelope-from hq@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B482C43D45; Wed, 31 Aug 2005 15:55:54 +0000 (GMT) (envelope-from hq@FreeBSD.org) Received: from freefall.freebsd.org (hq@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7VFtsYr061974; Wed, 31 Aug 2005 15:55:54 GMT (envelope-from hq@freefall.freebsd.org) Received: (from hq@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7VFtsgD061970; Wed, 31 Aug 2005 15:55:54 GMT (envelope-from hq) Date: Wed, 31 Aug 2005 15:55:54 GMT From: Herve Quiroz Message-Id: <200508311555.j7VFtsgD061970@freefall.freebsd.org> To: hq@FreeBSD.org, freebsd-java@FreeBSD.org, freebsd-eclipse@FreeBSD.org Cc: Subject: Re: ports/85300: [update] Update java/eclipse-cdt to version 3.0.0 X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 15:55:55 -0000 Synopsis: [update] Update java/eclipse-cdt to version 3.0.0 Responsible-Changed-From-To: freebsd-java->freebsd-eclipse Responsible-Changed-By: hq Responsible-Changed-When: Wed Aug 31 15:55:19 GMT 2005 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=85300 From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 15:57:25 2005 Return-Path: X-Original-To: freebsd-eclipse@hub.freebsd.org Delivered-To: freebsd-eclipse@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4813B16A41F; Wed, 31 Aug 2005 15:57:25 +0000 (GMT) (envelope-from hq@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 029EE43D45; Wed, 31 Aug 2005 15:57:25 +0000 (GMT) (envelope-from hq@FreeBSD.org) Received: from freefall.freebsd.org (hq@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7VFvO62062027; Wed, 31 Aug 2005 15:57:24 GMT (envelope-from hq@freefall.freebsd.org) Received: (from hq@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7VFvOIh062023; Wed, 31 Aug 2005 15:57:24 GMT (envelope-from hq) Date: Wed, 31 Aug 2005 15:57:24 GMT From: Herve Quiroz Message-Id: <200508311557.j7VFvOIh062023@freefall.freebsd.org> To: hq@FreeBSD.org, freebsd-java@FreeBSD.org, freebsd-eclipse@FreeBSD.org Cc: Subject: Re: ports/72014: Eclipse doesn't work (SigBus 10) if it has been built with GTK X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 15:57:25 -0000 Synopsis: Eclipse doesn't work (SigBus 10) if it has been built with GTK Responsible-Changed-From-To: freebsd-java->freebsd-eclipse Responsible-Changed-By: hq Responsible-Changed-When: Wed Aug 31 15:56:33 GMT 2005 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=72014 From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 20:05:17 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA18C16A41F; Wed, 31 Aug 2005 20:05:17 +0000 (GMT) (envelope-from past@ebs.gr) Received: from fly.ebs.gr (fly.ebs.gr [62.103.84.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id B615043D75; Wed, 31 Aug 2005 20:05:03 +0000 (GMT) (envelope-from past@ebs.gr) Received: from ebs.gr (root@hal.ebs.gr [10.1.1.2]) by fly.ebs.gr (8.12.9p1/8.12.9) with ESMTP id j7VK51ID005209; Wed, 31 Aug 2005 23:05:01 +0300 (EEST) (envelope-from past@ebs.gr) Received: from [10.1.1.200] (pptp.ebs.gr [10.1.1.200]) by ebs.gr (8.13.3/8.12.11) with ESMTP id j7VK50AX006408; Wed, 31 Aug 2005 23:05:01 +0300 (EEST) (envelope-from past@ebs.gr) Message-ID: <43160D67.6040605@ebs.gr> Date: Wed, 31 Aug 2005 23:04:55 +0300 From: Panagiotis Astithas Organization: EBS Ltd. User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050830) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vizion References: <200508251303.59453.vizion@vizion.occoxmail.com> <200508301927.31549.vizion@vizion.occoxmail.com> <43156772.7070808@ebs.gr> <200508310829.03121.vizion@vizion.occoxmail.com> In-Reply-To: <200508310829.03121.vizion@vizion.occoxmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mark Linimon , Herve Quiroz , freebsd-eclipse@freebsd.org Subject: Re: How should eclipse be organized in the ports tree? X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 20:05:17 -0000 Vizion wrote: > On Wednesday 31 August 2005 01:16, the author Panagiotis Astithas contributed > to the dialogue on- > Re: How should eclipse be organized in the ports tree?: > > >>Vizion wrote: >> >>>On Tuesday 30 August 2005 16:15, the author Vizion contributed to the >>>dialogue on- >>> >>> Re: How should eclipse be organized in the ports tree?: >>> >>>>On Tuesday 30 August 2005 14:23, the author Mark Linimon contributed to >>>>the dialogue on- >>>>Re: Eclipse as part of the ports/java tree? [Was freebsd eclipse plugins & >>>> >>>>mailing list]: >>>> >>>>>On Tue, Aug 30, 2005 at 10:10:26AM -0700, Vizion wrote: >>>>> >>>>>>I am now faced with the question is the ports tree as inflexible as some >>>>>>people suggest or are some members of our meritocracy more inflexible >>>>>>than the freebsd assets? >>>>> >>>>>This is a complete oversimplification of the situation. >>>>> >>>>>There are some hard-coded assumptions in the ports tree -- one of which >>>>>is that there are two levels, categories and ports -- and these >>>>>assumptions are mirrored in the repositories of tens of thousands if not >>>>>hundreds of thousands of users, and thousands of lines of shell scripts >>>>>and database programs that create the binary packages and monitor the >>>>>results of those build processes. >>>>> >>>>>So when you suggest that the only way that Eclipse can be supported is >>>>>to have a multilevel ports tree -- as you are seeming to -- you are >>>>>clearly totally misunderestimating the amount of effort involved. >>>>> >>>>>In your most recent email I think you are finally getting a lot closer to >>>>>what I consider 'real' problem. IMHO the interesting problems you want >>>>>to solve are the 'search' and 'browse' problems. Directory names >>>>>controlled by CVS structures in an unbranched tree, which are then >>>>>mirrored all around the world, are really poor paradigms for these >>>>>problems. Herve has suggested some better tools for these which are >>>>>better ways to think about these problems and you should look at those. >>>>>We certainly need more. >>>>> >>>>>The meta-plugin idea is also worth considering. >>>>> >>>>>But restructuring the entire tree, even to add a few hundred ports, is >>>>>simply not feasible with the level of volunteer effort we have and the >>>>>number of people that depend on the current structure worldwide. >>>>> >>>>>mcl >>>> >>>>Ok - building on your comments would my original suggestion, as modified >>>>below, and leaving aside for one moment the arguments as to whether or not >>>>committers might desire it,be capable of implementation without a >>>>restructuring of code? >>>> >>>>This proposal mean that /usr/ports/plugins/*.jar is a repository for files >>>>which are accessed solely via the meta-eclipsevx.xxx ports. >>>> >>>>I think this might shoehorn the necessary structure into the existing >>>>system. What do you think? >>>> >>>>/usr/ports/eclipse/eclipsemainv[x.xxx] Holds the main eclipse ports >>>>/usr/ports/eclipse/meta-eclipse[v.xxx] Holds eclipse plugins loader >>> >>>Just for sake of clarity the above are intended to be straight forward >>>ports >>> >>> >>>>/usr/ports/eclipse/plugins/ Holds the *.jar files >>>> >>>> >>>>/usr/ports/eclipse/misc1 self contained eclipse >>> >>>ports >>> >>> >>>>/usr/ports/eclipse/misc2 >>>>/usr/ports/eclipse/miscN >>>> >>>>/usr/ports/eclipse/plugins would, in effect, be a set of files which would >>>>be downloaded under control of the meta-eclipse loader >>>> >>>>If so why not use it - that would make eclipse a category which could >>>>enclose a number of ports for eclipse versions, a number >>>>of /usr/ports/eclipse/meta_eclipseplugin ports and each plugin would >>>>then (in effect) be a *.jar file file held within the >>>>/usr/eclipse/plugins directory. >>>>The meta_eclipse plugin could build the library of available plugins on >>>>the fly and use the standard system for registering the plugins on the >>>>local machine. In that way could the need be integrated into the existing >>>>system? >>>> >>>>Whatis your reaction? >>>> >>>>david >> >>I see various problems with your approach, let me try to identify a few. >> >>First of all, a plugin's jar file is essentially its distfile, currently >>downloaded by the ports system in ports/distfiles or its subdirectories. >>Storing it in the ports CVS repository (in ports/eclipse/plugins), as >>you seem to imply, would in some cases be problematic because of >>licensing/redistribution issues (not to mention bloat). > > > > >>Another thing is that many eclipse plugins have to be traditional ports >>since they require the ports infrastructure for their dependencies (see >>java/eclipseme for an example). Therefore they do not fit in the >>ports/eclipse/plugins case. Also, what is the point of treating plugins >>differently, with ports/eclipse/plugins and ports/eclipse/miscX? What do >>you gain by losing uniformity? > > > The ability dramatically reduce the amount of work necessary to bring ALL > available opensource eclipse plugins into the ports tree. By getting the > plugins into their own directory we can take advantage of eclipse's inbuilt > mechanism for importing plugins. By taking this approach all necessary > moodifications can be contained within a pluginloader module and the > *.jarcould, in the majority of cases, be the standard eclipse .jar file with > little modification. Wait a minute... you mean do something like symlink /usr/local/eclipse/plugins to /usr/ports/eclipse/plugins? And instead of downloading the plugin artifacts as usual (make fetch), get portsnap/cvsup to do it for you? I hope you don't really mean that, since that would just impose the bloat of eclipse jar files on everyone, everywhere with a ports collection ("You want eclipse-foo-plugin? No? Tough, you _will_ get it anyway on your next portsnap/cvsup!") >>Furthermore, you describe the need to create an eclipse plugin that >>lists the available plugins as FreeBSD ports and lets the user install >>one and register it as a regular system package. How is this better than >>eclipse's own plugin management method? > > > Currently plugins are scattered on different internet sites. The majority are > open source with no restrictions on redistribution if they are unmodified. By > bringing them together in one place we provide not only > > >>I would go even further and ask >>why do you need FreeBSD-specific ports for most plugins? Why not simply >>install it via the internal GUI and be done with it? That way you get >>the usual Eclipse experience you see in other platforms. I am actually >>doing this myself and quite like it, to be honest. The tradeoff is that >>you get files under $PREFIX/eclipse that are not recorded in some >>package, but I'm OK with that. > > > That is fine for single user but where you have multiple users you need to be > able to have a single system to ensure the whole team are using the same > plugin version. Freebsd offers a huge advantage in the its ports mechanism > for update and control of ports. I see the pluginloader provider another gui > into the package system. > > >>But consider this: you propose to create >>a new FreeBSD-specific plugin for eclipse, reorganize the ports tree, > > > I see no reason to reorganize the ports tree. The only drawback seems to be a > quasi-religious objection to making eclipse a category in the ports tree. > > >>and change every existing eclipse plugin (to fit in the new scheme) > > > I have read what is available and as far as I can see there is the potential > to do this without changing the vast majority of plugins that have not yet > been incorprated in the ports tree. > > >>in >>exchange for what? The registration in packages of every plugin _and_ a >>GUI plugin manager? When you could get either of those with the current >>system? Does the amount of effort needed, justify the gain? > > > Yes we get a rapid integration into the ports tree of all the eclipse > plugins. > > >>Let me state this once more, there is no eclipse-supported platform >>currently that provides what you propose. Therefore it cannot be >>considered a disadvantage for FreeBSD, either. Our forefathers said, >>that you should learn to walk, before running. Let's do that, shall we? >>Let's bring those 300+ plugins you mentioned into the ports system and >>see where we go from there. > > We could do that but the amount of work needed going that route is far greater > than the work involved in developing a generic eclipse loader by adding > additonal plugin feature to eclipse's own loader... think about it. Now, this seems a bit different from the above. You seem to suggest that we shall modify eclipse's internals to load plugins in our own particular way and that this will be easier than traditional porting work. Do you have any proof for that? Have you got any WIP code to discuss? Do you even know which classes in eclipse should be modified? Or is this just a "it sounds like a good idea"? >>Let's get our system officially supported by >>eclipse.org so that FreeBSD gets more visibility and credibility. Let's >>work out the swt dependencies of various applications and be the first >>eclipse platform that does not contain swt libraries all over the place. >> >>What do you say? > > > > >> >>Cheers, >> >>Panagiotis Panagiotis From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 20:40:06 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92FAA16A41F; Wed, 31 Aug 2005 20:40:06 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56AFD43D5A; Wed, 31 Aug 2005 20:40:01 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 3B536278D; Wed, 31 Aug 2005 15:40:00 -0500 (CDT) Date: Wed, 31 Aug 2005 15:40:00 -0500 To: Vizion Message-ID: <20050831204000.GA10673@soaustin.net> References: <200508251303.59453.vizion@vizion.occoxmail.com> <200508301927.31549.vizion@vizion.occoxmail.com> <43156772.7070808@ebs.gr> <200508310829.03121.vizion@vizion.occoxmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200508310829.03121.vizion@vizion.occoxmail.com> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: Mark Linimon , Herve Quiroz , freebsd-eclipse@freebsd.org Subject: Re: How should eclipse be organized in the ports tree? X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 20:40:06 -0000 > >First of all, a plugin's jar file is essentially its distfile, currently > >downloaded by the ports system in ports/distfiles or its subdirectories. > >Storing it in the ports CVS repository (in ports/eclipse/plugins), as > >you seem to imply, would in some cases be problematic because of > >licensing/redistribution issues (not to mention bloat). OK, I missed this part the first time around. I thought that you were talking about having a way to _fetch_ all the jarfiles in the subport -- not the jarfiles themselves. The problem is that the jarfiles are large, and everyone who has a copy of the ports collection would have to have them -- even people who do not use eclipse. There is also the fact that, being binaries, every time they change they would essentially be a complete new copy in the CVS repository. We currently do not have many (any?) binaries in the CVS repository and it probably ought to stay that way. CVS is much more efficient for text files. I would instead rather see a port that, when you update it, goes though the latest list of jarfiles and fetches them into a single subdirectory of ports/distfiles (e.g. ports/distfiles/eclipse-plugins/). That unifies the search function without penalizing anyone who does not wish to install the eclipse ports. This also disentangles us from licensing problems. mcl From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 20:40:28 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB3EC16A41F; Wed, 31 Aug 2005 20:40:28 +0000 (GMT) (envelope-from past@ebs.gr) Received: from fly.ebs.gr (fly.ebs.gr [62.103.84.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1276243D67; Wed, 31 Aug 2005 20:40:23 +0000 (GMT) (envelope-from past@ebs.gr) Received: from ebs.gr (root@hal.ebs.gr [10.1.1.2]) by fly.ebs.gr (8.12.9p1/8.12.9) with ESMTP id j7VKeCID005313; Wed, 31 Aug 2005 23:40:12 +0300 (EEST) (envelope-from past@ebs.gr) Received: from [10.1.1.200] (pptp.ebs.gr [10.1.1.200]) by ebs.gr (8.13.3/8.12.11) with ESMTP id j7VKeDf8006727; Wed, 31 Aug 2005 23:40:14 +0300 (EEST) (envelope-from past@ebs.gr) Message-ID: <431615A8.7010209@ebs.gr> Date: Wed, 31 Aug 2005 23:40:08 +0300 From: Panagiotis Astithas Organization: EBS Ltd. User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050830) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jorge Mario Mazo References: <200508311520.j7VFK8ve058569@freefall.freebsd.org> In-Reply-To: <200508311520.j7VFK8ve058569@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: bug-followup@freebsd.org, freebsd-eclipse@freebsd.org Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 20:40:28 -0000 Jorge Mario Mazo wrote: > The following reply was made to PR ports/85501; it has been noted by GNATS. > > From: Jorge Mario Mazo [...] > On Wed, 2005-08-31 at 15:35 +0400, Vladimir Grebenschikov wrote: > > Also new cdt plug-in crash eclipse while indexing C++ project: > > > > % gdb /usr/local/jdk1.5.0/bin/java java.core [...] > > Hi there > there seems to be a better patch for upgrade! check PR ports/85300 . The only thing better in it must be the auto plist generation :-) > About the bug, that bug it's been there for ages! I have reported it (on > mailing lists and such) and noone seems to care. By the way it hapens > with java projects for me as well > > "We" would really like to see this fixed since there is no > "professional" IDE for FreeBSD (eclipse works half-assed, anjuta is too > old and the new version does not compile, and Kdevelop it's not an > option for us) and boss it's starting to bitch and talking about > switching to Linux :( > > Is there other site where we could move this thread? I can send debuggin > information try patches and such. > > -- > [jorge@verde:/usr/home/jorge]$ java -version > java version "1.4.2-p7" > Java(TM) 2 Runtime Environment, Standard Edition (build > 1.4.2-p7-root_27_mar_2005_14_22) > Java HotSpot(TM) Client VM (build 1.4.2-p7-root_27_mar_2005_14_22, mixed > mode) > [jorge@verde:/usr/home/jorge]$ The current CDT port, as well as these new updates to 3.0.0 do not deal with the native libraries that it contains. I sent this update as a quick way for people to continue running cdt on eclipse 3.1. I am working for a complete port of CDT, but it will take some time and I am not very confident that it will deal with the mentioned crash. Does the crash happen on a system where swt or gtk were built with compiler optimization, by the way? Panagiotis From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 20:50:25 2005 Return-Path: X-Original-To: freebsd-eclipse@hub.freebsd.org Delivered-To: freebsd-eclipse@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90C4216A41F for ; Wed, 31 Aug 2005 20:50:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 440E543D45 for ; Wed, 31 Aug 2005 20:50:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7VKoPJb098693 for ; Wed, 31 Aug 2005 20:50:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7VKoOm4098688; Wed, 31 Aug 2005 20:50:24 GMT (envelope-from gnats) Date: Wed, 31 Aug 2005 20:50:24 GMT Message-Id: <200508312050.j7VKoOm4098688@freefall.freebsd.org> To: freebsd-eclipse@FreeBSD.org From: Panagiotis Astithas Cc: Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Panagiotis Astithas List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 20:50:25 -0000 The following reply was made to PR ports/85501; it has been noted by GNATS. From: Panagiotis Astithas To: Jorge Mario Mazo Cc: freebsd-eclipse@freebsd.org, bug-followup@freebsd.org Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse Date: Wed, 31 Aug 2005 23:40:08 +0300 Jorge Mario Mazo wrote: > The following reply was made to PR ports/85501; it has been noted by GNATS. > > From: Jorge Mario Mazo [...] > On Wed, 2005-08-31 at 15:35 +0400, Vladimir Grebenschikov wrote: > > Also new cdt plug-in crash eclipse while indexing C++ project: > > > > % gdb /usr/local/jdk1.5.0/bin/java java.core [...] > > Hi there > there seems to be a better patch for upgrade! check PR ports/85300 . The only thing better in it must be the auto plist generation :-) > About the bug, that bug it's been there for ages! I have reported it (on > mailing lists and such) and noone seems to care. By the way it hapens > with java projects for me as well > > "We" would really like to see this fixed since there is no > "professional" IDE for FreeBSD (eclipse works half-assed, anjuta is too > old and the new version does not compile, and Kdevelop it's not an > option for us) and boss it's starting to bitch and talking about > switching to Linux :( > > Is there other site where we could move this thread? I can send debuggin > information try patches and such. > > -- > [jorge@verde:/usr/home/jorge]$ java -version > java version "1.4.2-p7" > Java(TM) 2 Runtime Environment, Standard Edition (build > 1.4.2-p7-root_27_mar_2005_14_22) > Java HotSpot(TM) Client VM (build 1.4.2-p7-root_27_mar_2005_14_22, mixed > mode) > [jorge@verde:/usr/home/jorge]$ The current CDT port, as well as these new updates to 3.0.0 do not deal with the native libraries that it contains. I sent this update as a quick way for people to continue running cdt on eclipse 3.1. I am working for a complete port of CDT, but it will take some time and I am not very confident that it will deal with the mentioned crash. Does the crash happen on a system where swt or gtk were built with compiler optimization, by the way? Panagiotis From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 21:17:34 2005 Return-Path: X-Original-To: freebsd-eclipse@FreeBSD.org Delivered-To: freebsd-eclipse@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35EE116A41F; Wed, 31 Aug 2005 21:17:34 +0000 (GMT) (envelope-from past@ebs.gr) Received: from fly.ebs.gr (fly.ebs.gr [62.103.84.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2642D43D45; Wed, 31 Aug 2005 21:17:32 +0000 (GMT) (envelope-from past@ebs.gr) Received: from ebs.gr (root@hal.ebs.gr [10.1.1.2]) by fly.ebs.gr (8.12.9p1/8.12.9) with ESMTP id j7VLHUID005422; Thu, 1 Sep 2005 00:17:30 +0300 (EEST) (envelope-from past@ebs.gr) Received: from [10.1.1.200] (pptp.ebs.gr [10.1.1.200]) by ebs.gr (8.13.3/8.12.11) with ESMTP id j7VLHVpT007073; Thu, 1 Sep 2005 00:17:32 +0300 (EEST) (envelope-from past@ebs.gr) Message-ID: <43161E66.4060204@ebs.gr> Date: Thu, 01 Sep 2005 00:17:26 +0300 From: Panagiotis Astithas Organization: EBS Ltd. User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050830) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mario Sergio Fujikawa Ferreira References: <20050829180704.68762.qmail@exxodus.fedaykin.here> <43136B59.7090508@videotron.ca> <431382C3.3060205@ebs.gr> <43144DF3.4020706@videotron.ca> <20050830160042.50317.qmail@exxodus.fedaykin.here> In-Reply-To: <20050830160042.50317.qmail@exxodus.fedaykin.here> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-eclipse@FreeBSD.org Subject: Re: Eclipse 3.1: no swt-pi-gtk-3138 X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 21:17:34 -0000 Mario Sergio Fujikawa Ferreira wrote: > Hi, > > Well, I agree that only one instance of swt > should be ever lying around. Or, at least, that they not CONFLICT > with one another since I need eclipse to build azureus but only swt > to run it which means I would have a hell of a dependency problem > otherwise. > > Well, for those wondering about an example. I did a crude > hack to azureus to get it going. The port still needs polishing > but it is good enough so that you can try any of the mentioned > solutions. > > I, for one, would prefer that the eclipse port > would extract the .so files somewhere rather than incarnating yet > another port since I also need the swt*jar files which are part of > eclipse. We wouldn't gain much from another port (saving run time > dependencies I mean), we would require both in the end. > > Port sample, > > http://people.FreeBSD.org/~lioux/azureus.tgz > > Regards, > Just to clear this one up, an swt port would contain every swt*.jar and every libswt*.so you see in eclipse. I see that the linux distribution of azureus bundles swt along. That means that they are not concerned with the assorted bloat. That is to be expected, I guess. Let me try to make an evaluation of the problem. The use cases I can think of are these: 1. users who need eclipse and not azureus and friends 2. users who need azureus, etc but not eclipse 3. users who need both eclipse and swt-based apps These are the solutions I see thus far: a. have a swt port besides the eclipse port b. keep only the eclipse port but tweak its swt jars c. keep only the eclipse port but tweak with azureus/etc. build process Solution a satisfies use cases 1 and 2. Use case 3 would be completely satisfied only if we avoid keeping two copies of swt. Solution b satisfies use cases 1 and 3. Use case 2 would have unnecessary bloat. Solution c satisfies use cases 1 and 3. Use case 2 would have unnecessary bloat. It seems that solution a would be ideal, provided that we can solve the eclipse/swt dependency issues. I would really like to avoid undoing the new standard eclipse plugin structure (single jars), since that would make it different from the package people would get from eclipse.org (in the not-too-distant future). I'm trying to invent some extra logic in the ports Makefiles, like "if we have eclipse, depend on it instead of swt", or "if eclipse exists mark swt as IGNORE", etc. If anyone has any ideas, I'm all ears. Alternatively, if you know how to specify the location of a native library to be in an archive, please speak up! Cheers, Panagiotis From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 21:36:15 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8855316A41F; Wed, 31 Aug 2005 21:36:15 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from lakecmmtao05.coxmail.com (lakecmmtao05.coxmail.com [68.99.120.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id D074143D46; Wed, 31 Aug 2005 21:36:14 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from dns1 ([64.58.171.82]) by lakecmmtao05.coxmail.com (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20050831213614.QVQN2425.lakecmmtao05.coxmail.com@dns1>; Wed, 31 Aug 2005 17:36:14 -0400 From: Vizion To: Mark Linimon Date: Wed, 31 Aug 2005 14:32:09 -0700 User-Agent: KMail/1.8 References: <200508251303.59453.vizion@vizion.occoxmail.com> <200508310829.03121.vizion@vizion.occoxmail.com> <20050831204000.GA10673@soaustin.net> In-Reply-To: <20050831204000.GA10673@soaustin.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508311432.10822.vizion@vizion.occoxmail.com> Cc: Herve Quiroz , freebsd-eclipse@freebsd.org Subject: Re: How should eclipse be organized in the ports tree? X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 21:36:15 -0000 On Wednesday 31 August 2005 13:40, the author Mark Linimon contributed to the dialogue on- Re: How should eclipse be organized in the ports tree?: >> >First of all, a plugin's jar file is essentially its distfile, currently >> >downloaded by the ports system in ports/distfiles or its subdirectories. >> >Storing it in the ports CVS repository (in ports/eclipse/plugins), as >> >you seem to imply, would in some cases be problematic because of >> >licensing/redistribution issues (not to mention bloat). > >OK, I missed this part the first time around. I thought that you >were talking about having a way to _fetch_ all the jarfiles in the >subport -- not the jarfiles themselves. I shortcircuited that one - I was thinking of a *.jar file (call this a *collect.jar )to load the correct plugineclipse jar file which presumably would then be ports/distfiles > >The problem is that the jarfiles are large, and everyone who has a >copy of the ports collection would have to have them -- even people >who do not use eclipse. There is also the fact that, being binaries, >every time they change they would essentially be a complete new copy >in the CVS repository. Agreed that would be far too messy > >We currently do not have many (any?) binaries in the CVS repository >and it probably ought to stay that way. CVS is much more efficient >for text files. > >I would instead rather see a port that, when you update it, goes >though the latest list of jarfiles and fetches them into a single >subdirectory of ports/distfiles (e.g. ports/distfiles/eclipse-plugins/). Yep that would work >That unifies the search function without penalizing anyone who does not >wish to install the eclipse ports. This also disentangles us from >licensing problems. makes sense the key to doing it this way is to get what I have called *collect.jar files in a single directory in the ports tree! > >mcl -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. From owner-freebsd-eclipse@FreeBSD.ORG Wed Aug 31 22:05:11 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1AC216A422; Wed, 31 Aug 2005 22:05:11 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from lakecmmtao06.coxmail.com (lakecmmtao06.coxmail.com [68.99.120.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0838A43D48; Wed, 31 Aug 2005 22:05:10 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from dns1 ([64.58.171.82]) by lakecmmtao06.coxmail.com (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20050831220510.SHHW24491.lakecmmtao06.coxmail.com@dns1>; Wed, 31 Aug 2005 18:05:10 -0400 From: Vizion To: Panagiotis Astithas Date: Wed, 31 Aug 2005 15:01:06 -0700 User-Agent: KMail/1.8 References: <200508251303.59453.vizion@vizion.occoxmail.com> <200508310829.03121.vizion@vizion.occoxmail.com> <43160D67.6040605@ebs.gr> In-Reply-To: <43160D67.6040605@ebs.gr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508311501.07026.vizion@vizion.occoxmail.com> Cc: Mark Linimon , Herve Quiroz , freebsd-eclipse@freebsd.org Subject: Re: How should eclipse be organized in the ports tree? X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 22:05:13 -0000 On Wednesday 31 August 2005 13:04, the author Panagiotis Astithas contributed to the dialogue on- Re: How should eclipse be organized in the ports tree?: >Vizion wrote: >> On Wednesday 31 August 2005 01:16, the author Panagiotis Astithas . > >Wait a minute... you mean do something like symlink >/usr/local/eclipse/plugins to /usr/ports/eclipse/plugins? And instead of >downloading the plugin artifacts as usual (make fetch), get >portsnap/cvsup to do it for you? I hope you don't really mean that, >since that would just impose the bloat of eclipse jar files on everyone, >everywhere with a ports collection ("You want eclipse-foo-plugin? No? >Tough, you _will_ get it anyway on your next portsnap/cvsup!") No that would crazy -- I am suggeestuing we have a *.jar files in the /usr/ports/eclipseplugins that gets the files from somewhere in ports/fidtfiles (sorry I thought that had been made clear much earlier in this dialogue. > >>>Furthermore, you describe the need to create an eclipse plugin that >>>lists the available plugins as FreeBSD ports and lets the user install >>>one and register it as a regular system package. How is this better than >>>eclipse's own plugin management method? >> >> Currently plugins are scattered on different internet sites. The majority >> are open source with no restrictions on redistribution if they are >> unmodified. By bringing them together in one place we provide not only >> >>>I would go even further and ask >>>why do you need FreeBSD-specific ports for most plugins? Why not simply >>>install it via the internal GUI and be done with it? That way you get >>>the usual Eclipse experience you see in other platforms. I am actually >>>doing this myself and quite like it, to be honest. The tradeoff is that >>>you get files under $PREFIX/eclipse that are not recorded in some >>>package, but I'm OK with that. >> >> That is fine for single user but where you have multiple users you need to >> be able to have a single system to ensure the whole team are using the >> same plugin version. Freebsd offers a huge advantage in the its ports >> mechanism for update and control of ports. I see the pluginloader provider >> another gui into the package system. >> >>>But consider this: you propose to create >>>a new FreeBSD-specific plugin for eclipse, reorganize the ports tree, >> >> I see no reason to reorganize the ports tree. The only drawback seems to >> be a quasi-religious objection to making eclipse a category in the ports >> tree. >> >>>and change every existing eclipse plugin (to fit in the new scheme) >> >> I have read what is available and as far as I can see there is the >> potential to do this without changing the vast majority of plugins that >> have not yet been incorprated in the ports tree. >> >>>in >>>exchange for what? The registration in packages of every plugin _and_ a >>>GUI plugin manager? When you could get either of those with the current >>>system? Does the amount of effort needed, justify the gain? >> >> Yes we get a rapid integration into the ports tree of all the eclipse >> plugins. >> >>>Let me state this once more, there is no eclipse-supported platform >>>currently that provides what you propose. Therefore it cannot be >>>considered a disadvantage for FreeBSD, either. >>>Our forefathers said, >>>that you should learn to walk, before running. Let's do that, shall we? >>>Let's bring those 300+ plugins you mentioned into the ports system and >>>see where we go from there. >> >> We could do that but the amount of work needed going that route is far >> greater than the work involved in developing a generic eclipse loader by >> adding additonal plugin feature to eclipse's own loader... think about it. > >Now, this seems a bit different from the above. You seem to suggest that >we shall modify eclipse's internals to load plugins in our own >particular way and that this will be easier than traditional porting >work. It is not so much modifying eclipse internals as writing a plugin that extends the functionality of existing plugins. >Do you have any proof for that? Have you got any WIP code to >discuss? >Do you even know which classes in eclipse should be modified? >Or is this just a "it sounds like a good idea"? It is more than "it soundslike a good idea but not as far as WIP (Ill explain why). The "How to write an Eclipse installerin the eclipse help" is as far as I have gone in researching a start point. On the face of it the concept appears to be do-able. (I am wondering about whether *collect.jar files could be used to update an available eclipse plugins database on the local computer to be used by the freebsdloader plugin to create a li9nk to the standard eclipse install mechanism. I think it is eminently doable by building on eclipse's existing assets, but if the collect.jarfiles were not in a single directory we would not be able the files to comply with eclipse system requirements for update sites - and we could not use those assets!. So I suppose I have started from the premise if there is no hope in getting the *collect.jar in a single directory then the concept is a non-starter unless we were willing to undertake an awful lot of work. >>>Panagiotis > >Panagiotis -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. From owner-freebsd-eclipse@FreeBSD.ORG Thu Sep 1 01:32:30 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F1AA16A41F; Thu, 1 Sep 2005 01:32:30 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from lakecmmtao06.coxmail.com (lakecmmtao06.coxmail.com [68.99.120.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id E99F443D45; Thu, 1 Sep 2005 01:32:29 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from dns1 ([64.58.171.82]) by lakecmmtao06.coxmail.com (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20050901013229.BJCB24491.lakecmmtao06.coxmail.com@dns1>; Wed, 31 Aug 2005 21:32:29 -0400 From: Vizion To: freebsd-eclipse@freebsd.org Date: Wed, 31 Aug 2005 18:28:24 -0700 User-Agent: KMail/1.8 References: <200508251303.59453.vizion@vizion.occoxmail.com> <43160D67.6040605@ebs.gr> <200508311501.07026.vizion@vizion.occoxmail.com> In-Reply-To: <200508311501.07026.vizion@vizion.occoxmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508311828.25624.vizion@vizion.occoxmail.com> Cc: Mark Linimon , Herve Quiroz Subject: Re: How should eclipse be organized in the ports tree? X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 01:32:30 -0000 On Wednesday 31 August 2005 15:01, the author Vizion contributed to the dialogue on- Re: How should eclipse be organized in the ports tree?: Additional comment >On Wednesday 31 August 2005 13:04, the author Panagiotis Astithas > contributed to the dialogue on- >>> We could do that but the amount of work needed going that route is far >>> greater than the work involved in developing a generic eclipse loader by >>> adding additonal plugin feature to eclipse's own loader... think about >>> it. >> >>Now, this seems a bit different from the above. You seem to suggest that >>we shall modify eclipse's internals to load plugins in our own >>particular way and that this will be easier than traditional porting >>work. > >It is not so much modifying eclipse internals as writing a plugin that > extends the functionality of existing plugins. > >>Do you have any proof for that? Have you got any WIP code to >>discuss? >>Do you even know which classes in eclipse should be modified? >>Or is this just a "it sounds like a good idea"? > >It is more than "it soundslike a good idea but not as far as WIP (Ill > explain why). >The "How to write an Eclipse installerin the eclipse help" is as far as I > have gone in researching a start point. >On the face of it the concept appears to be do-able. (I am wondering about >whether *collect.jar files could be used to update an available eclipse >plugins database on the local computer to be used by the freebsdloader > plugin to create a li9nk to the standard eclipse install mechanism. > >I think it is eminently doable by building on eclipse's existing assets, but >if the collect.jarfiles were not in a single directory we would not be able >the files to comply with eclipse system requirements for update sites - and >we could not use those assets!. > >So I suppose I have started from the premise if there is no hope in getting >the *collect.jar in a single directory then the concept is a non-starter >unless we were willing to undertake an awful lot of work. What I see here is the potential to have all the local installation processes contained in a standard eclipsepluginloader. This approach can cut out a lot of the work needed to bring plugins into the freebsd port tree. It is also means that each *collect.jar could include an xml file which could be used to define properties for its plugin. > >>>>Panagiotis >> >>Panagiotis -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit. From owner-freebsd-eclipse@FreeBSD.ORG Thu Sep 1 07:10:21 2005 Return-Path: X-Original-To: freebsd-eclipse@hub.freebsd.org Delivered-To: freebsd-eclipse@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69B1016A41F for ; Thu, 1 Sep 2005 07:10:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3770343D45 for ; Thu, 1 Sep 2005 07:10:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j817ALE4083378 for ; Thu, 1 Sep 2005 07:10:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j817AKjr083377; Thu, 1 Sep 2005 07:10:20 GMT (envelope-from gnats) Date: Thu, 1 Sep 2005 07:10:20 GMT Message-Id: <200509010710.j817AKjr083377@freefall.freebsd.org> To: freebsd-eclipse@FreeBSD.org From: Vladimir Grebenschikov Cc: Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vladimir Grebenschikov List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 07:10:21 -0000 The following reply was made to PR ports/85501; it has been noted by GNATS. From: Vladimir Grebenschikov To: Jorge Mario Mazo Cc: past@ebs.gr, bug-followup@FreeBSD.org Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse Date: Thu, 01 Sep 2005 11:06:00 +0400 =F7 =D3=D2, 31/08/2005 =D7 10:16 -0500, Jorge Mario Mazo =D0=C9=DB=C5=D4: > On Wed, 2005-08-31 at 15:35 +0400, Vladimir Grebenschikov wrote: > > Also new cdt plug-in crash eclipse while indexing C++ project: > Hi there > there seems to be a better patch for upgrade! check PR ports/85300 . Yes, I've already found that, it makes package ok. > About the bug, that bug it's been there for ages! I have reported it (on > mailing lists and such) and noone seems to care. By the way it hapens > with java projects for me as well Hm, 2.x CDT did not crash before for me, but it does not index things well also. Most of classes was not indexed > "We" would really like to see this fixed since there is no > "professional" IDE for FreeBSD (eclipse works half-assed, anjuta is too > old and the new version does not compile, and Kdevelop it's not an > option for us) and boss it's starting to bitch and talking about > switching to Linux :( Agree. Probably eclipse in linux emulation (with linux java) will work better ? > Is there other site where we could move this thread? I can send debugging > information try patches and such. >=20 > -- > [jorge@verde:/usr/home/jorge]$ java -version > java version "1.4.2-p7" > Java(TM) 2 Runtime Environment, Standard Edition (build > 1.4.2-p7-root_27_mar_2005_14_22) > Java HotSpot(TM) Client VM (build 1.4.2-p7-root_27_mar_2005_14_22, mixed > mode) > [jorge@verde:/usr/home/jorge]$ >=20 >=20 --=20 Vladimir B. Grebenschikov SWsoft Inc. vova@sw-soft.com From owner-freebsd-eclipse@FreeBSD.ORG Thu Sep 1 08:40:07 2005 Return-Path: X-Original-To: freebsd-eclipse@hub.freebsd.org Delivered-To: freebsd-eclipse@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D04FD16A41F for ; Thu, 1 Sep 2005 08:40:07 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99F7243D45 for ; Thu, 1 Sep 2005 08:40:07 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j818e7bL093271 for ; Thu, 1 Sep 2005 08:40:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j818e7ri093270; Thu, 1 Sep 2005 08:40:07 GMT (envelope-from gnats) Date: Thu, 1 Sep 2005 08:40:07 GMT Message-Id: <200509010840.j818e7ri093270@freefall.freebsd.org> To: freebsd-eclipse@FreeBSD.org From: Panagiotis Astithas Cc: Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Panagiotis Astithas List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 08:40:07 -0000 The following reply was made to PR ports/85501; it has been noted by GNATS. From: Panagiotis Astithas To: Vladimir Grebenschikov Cc: Jorge Mario Mazo , bug-followup@FreeBSD.org Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse Date: Thu, 01 Sep 2005 11:35:44 +0300 Vladimir Grebenschikov wrote: > В ср, 31/08/2005 в 10:16 -0500, Jorge Mario Mazo пишет: > >>On Wed, 2005-08-31 at 15:35 +0400, Vladimir Grebenschikov wrote: >> >>>Also new cdt plug-in crash eclipse while indexing C++ project: >>About the bug, that bug it's been there for ages! I have reported it (on >>mailing lists and such) and noone seems to care. By the way it hapens >>with java projects for me as well > > > Hm, 2.x CDT did not crash before for me, but it does not index things > well also. Most of classes was not indexed Note that CDT 3 supports internal indexing, as well as ctags indexing. Which one causes the trouble in this case? Does it work if you select the other method? Panagiotis From owner-freebsd-eclipse@FreeBSD.ORG Thu Sep 1 09:20:21 2005 Return-Path: X-Original-To: freebsd-eclipse@hub.freebsd.org Delivered-To: freebsd-eclipse@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1725A16A41F for ; Thu, 1 Sep 2005 09:20:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CBBA43D69 for ; Thu, 1 Sep 2005 09:20:18 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j819KHQE098632 for ; Thu, 1 Sep 2005 09:20:17 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j819KHJQ098631; Thu, 1 Sep 2005 09:20:17 GMT (envelope-from gnats) Date: Thu, 1 Sep 2005 09:20:17 GMT Message-Id: <200509010920.j819KHJQ098631@freefall.freebsd.org> To: freebsd-eclipse@FreeBSD.org From: Vladimir Grebenschikov Cc: Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vladimir Grebenschikov List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 09:20:21 -0000 The following reply was made to PR ports/85501; it has been noted by GNATS. From: Vladimir Grebenschikov To: Panagiotis Astithas Cc: Jorge Mario Mazo , bug-followup@FreeBSD.org Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse Date: Thu, 01 Sep 2005 13:15:26 +0400 =F7 =DE=D4, 01/09/2005 =D7 11:35 +0300, Panagiotis Astithas =D0=C9=DB=C5=D4= : > Vladimir Grebenschikov wrote: > > =F7 =D3=D2, 31/08/2005 =D7 10:16 -0500, Jorge Mario Mazo =D0=C9=DB=C5= =D4: > >=20 > >>On Wed, 2005-08-31 at 15:35 +0400, Vladimir Grebenschikov wrote: > >> > >>>Also new cdt plug-in crash eclipse while indexing C++ project: > >>About the bug, that bug it's been there for ages! I have reported it (o= n > >>mailing lists and such) and noone seems to care. By the way it hapens > >>with java projects for me as well > >=20 > >=20 > > Hm, 2.x CDT did not crash before for me, but it does not index things > > well also. Most of classes was not indexed >=20 > Note that CDT 3 supports internal indexing, as well as ctags indexing.=20 > Which one causes the trouble in this case?=20 internal > Does it work if you select the other method? No, actually, If I'd liked ctags I'd still used xemacs, not eclipse. > Panagiotis --=20 Vladimir B. Grebenschikov SWsoft Inc. vova@sw-soft.com From owner-freebsd-eclipse@FreeBSD.ORG Thu Sep 1 09:49:10 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A39716A41F; Thu, 1 Sep 2005 09:49:10 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vbook.fbsd.ru (swsoft-mipt-nat.sw.ru [195.214.233.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id B53E243D45; Thu, 1 Sep 2005 09:49:09 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.52 (FreeBSD)) id 1EAlgw-0000dw-2q; Thu, 01 Sep 2005 13:49:06 +0400 From: Vladimir Grebenschikov To: Panagiotis Astithas In-Reply-To: <431615A8.7010209@ebs.gr> References: <200508311520.j7VFK8ve058569@freefall.freebsd.org> <431615A8.7010209@ebs.gr> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Thu, 01 Sep 2005 13:49:05 +0400 Message-Id: <1125568145.1079.14.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: Jorge Mario Mazo , bug-followup@freebsd.org, freebsd-eclipse@freebsd.org Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 09:49:10 -0000 =F7 =D3=D2, 31/08/2005 =D7 23:40 +0300, Panagiotis Astithas =D0=C9=DB=C5=D4= : > The current CDT port, as well as these new updates to 3.0.0 do not deal=20 > with the native libraries that it contains. I sent this update as a=20 > quick way for people to continue running cdt on eclipse 3.1. I am=20 > working for a complete port of CDT, but it will take some time and I am=20 > not very confident that it will deal with the mentioned crash. Does the=20 > crash happen on a system where swt or gtk were built with compiler=20 > optimization, by the way? gtk, with default compilation options. I am ready to test any patches with this crash. > Panagiotis --=20 Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-eclipse@FreeBSD.ORG Thu Sep 1 09:50:15 2005 Return-Path: X-Original-To: freebsd-eclipse@hub.freebsd.org Delivered-To: freebsd-eclipse@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 57E5416A41F for ; Thu, 1 Sep 2005 09:50:15 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2789C43D5C for ; Thu, 1 Sep 2005 09:50:14 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j819oDSg000558 for ; Thu, 1 Sep 2005 09:50:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j819oDxA000557; Thu, 1 Sep 2005 09:50:13 GMT (envelope-from gnats) Date: Thu, 1 Sep 2005 09:50:13 GMT Message-Id: <200509010950.j819oDxA000557@freefall.freebsd.org> To: freebsd-eclipse@FreeBSD.org From: Vladimir Grebenschikov Cc: Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vladimir Grebenschikov List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 09:50:15 -0000 The following reply was made to PR ports/85501; it has been noted by GNATS. From: Vladimir Grebenschikov To: Panagiotis Astithas Cc: Jorge Mario Mazo , bug-followup@freebsd.org, freebsd-eclipse@freebsd.org Subject: Re: ports/85501: upgrade of the CDT plugin for eclipse Date: Thu, 01 Sep 2005 13:49:05 +0400 =F7 =D3=D2, 31/08/2005 =D7 23:40 +0300, Panagiotis Astithas =D0=C9=DB=C5=D4= : > The current CDT port, as well as these new updates to 3.0.0 do not deal=20 > with the native libraries that it contains. I sent this update as a=20 > quick way for people to continue running cdt on eclipse 3.1. I am=20 > working for a complete port of CDT, but it will take some time and I am=20 > not very confident that it will deal with the mentioned crash. Does the=20 > crash happen on a system where swt or gtk were built with compiler=20 > optimization, by the way? gtk, with default compilation options. I am ready to test any patches with this crash. > Panagiotis --=20 Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-eclipse@FreeBSD.ORG Thu Sep 1 21:25:17 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D99616A41F for ; Thu, 1 Sep 2005 21:25:17 +0000 (GMT) (envelope-from past@ebs.gr) Received: from fly.ebs.gr (fly.ebs.gr [62.103.84.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 512DC43D45 for ; Thu, 1 Sep 2005 21:25:16 +0000 (GMT) (envelope-from past@ebs.gr) Received: from ebs.gr (root@hal.ebs.gr [10.1.1.2]) by fly.ebs.gr (8.12.9p1/8.12.9) with ESMTP id j81LPEID009392; Fri, 2 Sep 2005 00:25:14 +0300 (EEST) (envelope-from past@ebs.gr) Received: from [10.1.1.200] (pptp.ebs.gr [10.1.1.200]) by ebs.gr (8.13.3/8.12.11) with ESMTP id j81LPG2m025411; Fri, 2 Sep 2005 00:25:17 +0300 (EEST) (envelope-from past@ebs.gr) Message-ID: <431771B6.7040108@ebs.gr> Date: Fri, 02 Sep 2005 00:25:10 +0300 From: Panagiotis Astithas Organization: EBS Ltd. User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050830) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Stephane E. Potvin" References: <431369F0.5060909@videotron.ca> In-Reply-To: <431369F0.5060909@videotron.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-eclipse@freebsd.org Subject: Re: [Patch] Fix eclipse build after latest firefox update X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 21:25:17 -0000 Stephane E. Potvin wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I had to apply the following patch to make eclipse build after the > latest firefox update (the one who changed firefox to use the system > nspr library). > > Steph OK, I verified it and submitted it along with another cleanup patch as PR ports/85590. You may consider submitting it yourself via send-pr, next time. Thanks, Panagiotis From owner-freebsd-eclipse@FreeBSD.ORG Thu Sep 1 23:40:19 2005 Return-Path: X-Original-To: freebsd-eclipse@hub.freebsd.org Delivered-To: freebsd-eclipse@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5515016A41F for ; Thu, 1 Sep 2005 23:40:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2556143D46 for ; Thu, 1 Sep 2005 23:40:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j81NeICL007872 for ; Thu, 1 Sep 2005 23:40:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j81NeIS2007871; Thu, 1 Sep 2005 23:40:18 GMT (envelope-from gnats) Date: Thu, 1 Sep 2005 23:40:18 GMT Message-Id: <200509012340.j81NeIS2007871@freefall.freebsd.org> To: freebsd-eclipse@FreeBSD.org From: Daniel Roethlisberger Cc: Subject: Re: ports/72014: Eclipse doesn't work (SigBus 10) if it has been built with GTK X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Roethlisberger List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 23:40:19 -0000 The following reply was made to PR ports/72014; it has been noted by GNATS. From: Daniel Roethlisberger To: bug-followup@FreeBSD.org, nlsn@free.fr Cc: Oleg Sharoiko , Panagiotis Astithas Subject: Re: ports/72014: Eclipse doesn't work (SigBus 10) if it has been built with GTK Date: Fri, 2 Sep 2005 01:36:50 +0200 I have just double checked on my pentium-m box, I can confirm that adding -mno-sse2 does solve the problem for me (at least as far as I can tell, as there is no definitive way to reproduce the problem). Compiling x11-toolkits/gtk20 with CPUTYPE?=pentium-m and CFLAGS=-O -pipe results in an unstable eclipse, while compiling gtk20 with the same CPUTYPE but CFLAGS=-O -pipe -mno-sse2 saves the day, giving me a stable eclipse. Can we add some kind of -mno-sse2 hack to the GTK port for the time being, or is there a better solution? -- Daniel Roethlisberger From owner-freebsd-eclipse@FreeBSD.ORG Fri Sep 2 01:03:39 2005 Return-Path: X-Original-To: freebsd-eclipse@hub.freebsd.org Delivered-To: freebsd-eclipse@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19ED016A44A; Fri, 2 Sep 2005 01:03:39 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB99543D45; Fri, 2 Sep 2005 01:03:38 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j8213ceQ018036; Fri, 2 Sep 2005 01:03:38 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j8213c3J018032; Fri, 2 Sep 2005 01:03:38 GMT (envelope-from linimon) Date: Fri, 2 Sep 2005 01:03:38 GMT From: Mark Linimon Message-Id: <200509020103.j8213c3J018032@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, freebsd-eclipse@FreeBSD.org Cc: Subject: Re: ports/85590: update: fix compiling for java/eclipse X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 01:03:39 -0000 Synopsis: update: fix compiling for java/eclipse Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-eclipse Responsible-Changed-By: linimon Responsible-Changed-When: Fri Sep 2 01:03:23 GMT 2005 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=85590 From owner-freebsd-eclipse@FreeBSD.ORG Fri Sep 2 08:20:35 2005 Return-Path: X-Original-To: freebsd-eclipse@FreeBSD.org Delivered-To: freebsd-eclipse@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFEA816A41F for ; Fri, 2 Sep 2005 08:20:35 +0000 (GMT) (envelope-from Daniel.Graupner@silverstroke.com) Received: from mailer2.silverstroke.com (mailer2.silverstroke.com [195.124.154.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7598543D45 for ; Fri, 2 Sep 2005 08:20:34 +0000 (GMT) (envelope-from Daniel.Graupner@silverstroke.com) Received: from localhost (localhost [127.0.0.1]) by mailer2.silverstroke.com (Silverstroke mailrelay) with ESMTP id E1C672862 for ; Fri, 2 Sep 2005 10:20:30 +0200 (CEST) Received: from s-yellow.net.silverstroke.de (s-yellow.net.silverstroke.de [172.16.20.5]) by mailer2.silverstroke.com (Silverstroke mailrelay) with ESMTP id 716FB2857 for ; Fri, 2 Sep 2005 10:20:26 +0200 (CEST) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Date: Fri, 2 Sep 2005 10:20:26 +0200 Message-ID: <9343542E664B894484613D106D7D3F5F491D40@s-yellow.net.silverstroke.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FreeBSD Port: java/eclipse-cdt Thread-Index: AcWvlyuJzW99vtymQwqZzAWh2X/vow== From: "Daniel Graupner" To: X-Virus-Scanned: by AMaViS 0.3.12pre5 Cc: Subject: FreeBSD Port: java/eclipse-cdt X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 08:20:36 -0000 Hello, Just want to ask if there are plans to update the port to 3.0 ? Regards, Daniel. From owner-freebsd-eclipse@FreeBSD.ORG Fri Sep 2 08:31:08 2005 Return-Path: X-Original-To: freebsd-eclipse@FreeBSD.org Delivered-To: freebsd-eclipse@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BE8C16A41F for ; Fri, 2 Sep 2005 08:31:08 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vbook.fbsd.ru (swsoft-mipt-nat.sw.ru [195.214.233.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE81443D45 for ; Fri, 2 Sep 2005 08:31:07 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.52 (FreeBSD)) id 1EB6wz-0008eT-Ow; Fri, 02 Sep 2005 12:31:05 +0400 From: Vladimir Grebenschikov To: Daniel Graupner In-Reply-To: <9343542E664B894484613D106D7D3F5F491D40@s-yellow.net.silverstroke.de> References: <9343542E664B894484613D106D7D3F5F491D40@s-yellow.net.silverstroke.de> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Fri, 02 Sep 2005 12:31:04 +0400 Message-Id: <1125649864.1102.3.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: freebsd-eclipse@FreeBSD.org Subject: Re: FreeBSD Port: java/eclipse-cdt X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 08:31:08 -0000 =F7 =D0=D4, 02/09/2005 =D7 10:20 +0200, Daniel Graupner =D0=C9=DB=C5=D4: > Hello, >=20 > Just want to ask if there are plans to update the port to 3.0 ? See patch in ports/85300. http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/85300 It looks like to work, but crash eclipse on big project indexing for me (in native indexes mode) > Regards, > Daniel. --=20 Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-eclipse@FreeBSD.ORG Fri Sep 2 09:50:26 2005 Return-Path: X-Original-To: freebsd-eclipse@hub.freebsd.org Delivered-To: freebsd-eclipse@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A7EC16A41F for ; Fri, 2 Sep 2005 09:50:26 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAC1243D4C for ; Fri, 2 Sep 2005 09:50:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j829oPBP092768 for ; Fri, 2 Sep 2005 09:50:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j829oPfF092767; Fri, 2 Sep 2005 09:50:25 GMT (envelope-from gnats) Date: Fri, 2 Sep 2005 09:50:25 GMT Message-Id: <200509020950.j829oPfF092767@freefall.freebsd.org> To: freebsd-eclipse@FreeBSD.org From: Panagiotis Astithas Cc: Subject: Re: ports/72014: Eclipse doesn't work (SigBus 10) if it has been built with GTK X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Panagiotis Astithas List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 09:50:26 -0000 The following reply was made to PR ports/72014; it has been noted by GNATS. From: Panagiotis Astithas To: gnome@freebsd.org Cc: Daniel Roethlisberger , bug-followup@freebsd.org, nlsn@free.fr, Oleg Sharoiko Subject: Re: ports/72014: Eclipse doesn't work (SigBus 10) if it has been built with GTK Date: Fri, 02 Sep 2005 12:40:15 +0300 I'm forwarding this to the people who are responsible for this. Daniel Roethlisberger wrote: > I have just double checked on my pentium-m box, I can confirm that > adding -mno-sse2 does solve the problem for me (at least as far as I can > tell, as there is no definitive way to reproduce the problem). > > Compiling x11-toolkits/gtk20 with CPUTYPE?=pentium-m and CFLAGS=-O -pipe > results in an unstable eclipse, while compiling gtk20 with the same > CPUTYPE but CFLAGS=-O -pipe -mno-sse2 saves the day, giving me a stable > eclipse. > > Can we add some kind of -mno-sse2 hack to the GTK port for the time > being, or is there a better solution? Some background: In PR ports/72014 it was reported a long time ago that eclipse/gtk crashes and this was tracked down to non-standard compiler optimizations when building gtk. There have been similar bug reports filed against the eclipse and gcc bug databases. Some gcc people have tracked it down to incorrect stack alignment (see ports/72014 for the pointers) and have received reports that using -mno-sse2 fixed it. Daniel has verified that this seems to help our case also. Therefore the question is, should we force -mno-sse2 to the compiler flags for the gtk ports? I would expect less bug reports from people who compile gtk apps with non-standard CFLAGS, at least. Cheers, Panagiotis From owner-freebsd-eclipse@FreeBSD.ORG Fri Sep 2 17:30:23 2005 Return-Path: X-Original-To: freebsd-eclipse@hub.freebsd.org Delivered-To: freebsd-eclipse@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 256A416A41F for ; Fri, 2 Sep 2005 17:30:23 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7ACF43D45 for ; Fri, 2 Sep 2005 17:30:22 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j82HUM3G053010 for ; Fri, 2 Sep 2005 17:30:22 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j82HUMRV053008; Fri, 2 Sep 2005 17:30:22 GMT (envelope-from gnats) Date: Fri, 2 Sep 2005 17:30:22 GMT Message-Id: <200509021730.j82HUMRV053008@freefall.freebsd.org> To: freebsd-eclipse@FreeBSD.org From: "Jeremy Messenger" Cc: Subject: Re: ports/72014: Eclipse doesn't work (SigBus 10) if it has been built with GTK X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jeremy Messenger List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 17:30:23 -0000 The following reply was made to PR ports/72014; it has been noted by GNATS. From: "Jeremy Messenger" To: "Panagiotis Astithas" Cc: "Oleg Sharoiko" , nlsn@free.fr, bug-followup@freebsd.org, "Daniel Roethlisberger" , gnome@freebsd.org Subject: Re: ports/72014: Eclipse doesn't work (SigBus 10) if it has been built with GTK Date: Fri, 02 Sep 2005 12:17:48 -0500 On Fri, 02 Sep 2005 04:40:15 -0500, Panagiotis Astithas wrote: > I'm forwarding this to the people who are responsible for this. > > Daniel Roethlisberger wrote: >> I have just double checked on my pentium-m box, I can confirm that >> adding -mno-sse2 does solve the problem for me (at least as far as I can >> tell, as there is no definitive way to reproduce the problem). >> Compiling x11-toolkits/gtk20 with CPUTYPE?=pentium-m and CFLAGS=-O >> -pipe >> results in an unstable eclipse, while compiling gtk20 with the same >> CPUTYPE but CFLAGS=-O -pipe -mno-sse2 saves the day, giving me a stable >> eclipse. >> Can we add some kind of -mno-sse2 hack to the GTK port for the time >> being, or is there a better solution? > > > Some background: > > In PR ports/72014 it was reported a long time ago that eclipse/gtk > crashes and this was tracked down to non-standard compiler optimizations > when building gtk. There have been similar bug reports filed against the > eclipse and gcc bug databases. Some gcc people have tracked it down to > incorrect stack alignment (see ports/72014 for the pointers) and have > received reports that using -mno-sse2 fixed it. Daniel has verified that > this seems to help our case also. It's a nice find the locate that SSE2 is causing the problem. Mono/gtk-sharp have the same problems and we always have to tell them to not tweak the CPUTYPE. After look at our PR and GCC's PRs, looks like might be either GCC or our libc bug. > Therefore the question is, should we force -mno-sse2 to the compiler > flags for the gtk ports? I would expect less bug reports from people who > compile gtk apps with non-standard CFLAGS, at least. It's good idea, I would like to add -mno-sse2 too. Here's patch, so let me know if I don't understand it correct or/and my English isn't right. http://people.freebsd.org/~mezz/diff/gtk20.diff Keep in mind, this patch is for MC. After that go in MC and I will put in offical one too. Cheers, Mezz > Cheers, > > Panagiotis -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From owner-freebsd-eclipse@FreeBSD.ORG Fri Sep 2 22:10:14 2005 Return-Path: X-Original-To: freebsd-eclipse@hub.freebsd.org Delivered-To: freebsd-eclipse@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 699D116A41F for ; Fri, 2 Sep 2005 22:10:14 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17D0043D46 for ; Fri, 2 Sep 2005 22:10:14 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j82MADwf089786 for ; Fri, 2 Sep 2005 22:10:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j82MADIB089785; Fri, 2 Sep 2005 22:10:13 GMT (envelope-from gnats) Date: Fri, 2 Sep 2005 22:10:13 GMT Message-Id: <200509022210.j82MADIB089785@freefall.freebsd.org> To: freebsd-eclipse@FreeBSD.org From: "Jeremy Messenger" Cc: Subject: Re: ports/72014: Eclipse doesn't work (SigBus 10) if it has been built with GTK X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jeremy Messenger List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 22:10:14 -0000 The following reply was made to PR ports/72014; it has been noted by GNATS. From: "Jeremy Messenger" To: "Panagiotis Astithas" Cc: gnome@freebsd.org, "Oleg Sharoiko" , nlsn@free.fr, bug-followup@freebsd.org, "Daniel Roethlisberger" Subject: Re: ports/72014: Eclipse doesn't work (SigBus 10) if it has been built with GTK Date: Fri, 02 Sep 2005 17:10:04 -0500 On Fri, 02 Sep 2005 12:17:48 -0500, Jeremy Messenger wrote: > On Fri, 02 Sep 2005 04:40:15 -0500, Panagiotis Astithas > wrote: > >> I'm forwarding this to the people who are responsible for this. >> >> Daniel Roethlisberger wrote: >>> I have just double checked on my pentium-m box, I can confirm that >>> adding -mno-sse2 does solve the problem for me (at least as far as I >>> can >>> tell, as there is no definitive way to reproduce the problem). >>> Compiling x11-toolkits/gtk20 with CPUTYPE?=pentium-m and CFLAGS=-O >>> -pipe >>> results in an unstable eclipse, while compiling gtk20 with the same >>> CPUTYPE but CFLAGS=-O -pipe -mno-sse2 saves the day, giving me a stable >>> eclipse. >>> Can we add some kind of -mno-sse2 hack to the GTK port for the time >>> being, or is there a better solution? >> >> >> Some background: >> >> In PR ports/72014 it was reported a long time ago that eclipse/gtk >> crashes and this was tracked down to non-standard compiler >> optimizations when building gtk. There have been similar bug reports >> filed against the eclipse and gcc bug databases. Some gcc people have >> tracked it down to incorrect stack alignment (see ports/72014 for the >> pointers) and have received reports that using -mno-sse2 fixed it. >> Daniel has verified that this seems to help our case also. > > It's a nice find the locate that SSE2 is causing the problem. > Mono/gtk-sharp have the same problems and we always have to tell them to > not tweak the CPUTYPE. After look at our PR and GCC's PRs, looks like > might be either GCC or our libc bug. > >> Therefore the question is, should we force -mno-sse2 to the compiler >> flags for the gtk ports? I would expect less bug reports from people >> who compile gtk apps with non-standard CFLAGS, at least. > > It's good idea, I would like to add -mno-sse2 too. Here's patch, so let > me know if I don't understand it correct or/and my English isn't right. I have committed it in both MC and offical ports tree. Cheers, Mezz > http://people.freebsd.org/~mezz/diff/gtk20.diff > > Keep in mind, this patch is for MC. After that go in MC and I will put > in offical one too. > > Cheers, > Mezz > >> Cheers, >> >> Panagiotis -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org