From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1FWEQn-0000kc-Qd for garchives@archives.gentoo.org; Wed, 19 Apr 2006 15:17:26 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.6/8.13.5) with SMTP id k3JFHo42023930; Wed, 19 Apr 2006 15:17:50 GMT Received: from banta-im.com (roy-rogers.nfic.com [208.231.230.100]) by robin.gentoo.org (8.13.6/8.13.5) with ESMTP id k3JFHndI004785 for ; Wed, 19 Apr 2006 15:17:50 GMT Received: from by banta-im.com (8.9.3/8.9.3) with ESMTP id LAA29371; Wed, 19 Apr 2006 11:15:37 -0400 (EDT) Message-ID: <44465419.3010503@gentoo.org> Date: Wed, 19 Apr 2006 11:15:37 -0400 From: Joshua Nichols User-Agent: Mail/News 1.5 (X11/20060414) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-java@gentoo.org MIME-Version: 1.0 To: Ivan Yosifov CC: gentoo-java@lists.gentoo.org Subject: Re: [gentoo-java] migration/eclass/java-utils.eclass: line 97: [: -ge: unary operator expected References: <200604181531.47237.ivan@yosifov.net> <444515A4.3070508@gentoo.org> <200604191108.28151.ivan@yosifov.net> In-Reply-To: <200604191108.28151.ivan@yosifov.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 01f198e8-568e-4bc3-9803-4dd291f9f229 X-Archives-Hash: be019d89d3d640fb6bc0ec41886d916f Ivan Yosifov wrote: > Am Dienstag, 18. April 2006 19:36 schrieb Joshua Nichols: > >> Ivan Yosifov wrote: >> >>> Hello, >>> >>> Happens while emergeing eclipse: >>> >>> home ~ # emerge -1 eclipse-sdk >>> Calculating dependencies... done! >>> >>> >>>>>> Emerging (1 of 1) dev-util/eclipse-sdk-3.1.2 to / >>>>>> checksums files .... >>>>>> checksums src_uri ;-) eclipse-sourceBuild-srcIncluded-3.1.2.zip >>>>>> >>> * Checking for sufficient physical RAM >>> * Checking for bad CFLAGS >>> * Found offending option -fomit-frame-pointer in your CFLAGS >>> .... >>> * Tip: use equery depgraph "=eclipse-sdk-3.1.2" to list all >>> dependencies. >>> >>> /usr/local/portage/migration/migration/eclass/java-utils.eclass: line 97: >>> [: -ge: unary operator expected >>> Detected a JDK < 1.5.0 >>> Detected a JDK >= 1.4.2 >>> >>> >>>>>> Unpacking source... >>>>>> >>> /usr/local/portage/migration/migration/ is where I've put the migration >>> overlay revision 2114. Bash is 3.1_p17. Is this an eclass bug or >>> something else ? >>> >> Something else, I think. I've been working on the eclipse ebuilds (while >> using migration-overlay, obviously), and hadn't noticed any problems. >> >> It might have something to do with the ebuild itself. Someone went and >> committed a bump to 3.1.2 without consulting with us Java folks, so I'm >> not sure what condition it is. Expect to see a new revision in a day or >> so... >> >> Josh >> > > I am getting the same with the new eclipse-sdk-3.1.2-r1. I added some > debugging output to the eclass in java-utils_is-vm-version-ge(): > > --- ./java-utils.eclass 2006-04-19 10:58:43.000000000 +0300 > +++ /usr/local/portage/migration/migration/eclass/java-utils.eclass > 2006-04-19 11:00:25.000000000 +0300 > @@ -91,6 +91,12 @@ > local vm_patch=$(echo ${vm_version} | cut -d. -f3) > local vm_extra=$(echo ${vm_version} | cut -d. -f4) > > + echo ${vm_major} > + echo ${vm_minor} > + echo ${user_major} > + echo ${user_minor} > + echo ${vm_patch} > + echo ${user_patch} > if [ ${vm_major} -ge ${user_major} ] && [ ${vm_minor} -gt > ${user_minor} ] ; then > echo "Detected a JDK >= ${user_version}" > return 0 > > and the output is: > > * Tip: use equery depgraph "=eclipse-sdk-3.1.2-r1" to list all dependencies. > > 1 > 5 > 1 > 5 > > 0 > /usr/local/portage/migration/migration/eclass/java-utils.eclass: line 103: > [: -ge: unary operator expected > Detected a JDK < 1.5.0 > 1 > 5 > 1 > 4 > > 2 > Detected a JDK >= 1.4.2 > >>>> Unpacking source... >>>> > > ,meaning that vm_patch is ending up empty and that seems to confuse -ge > conditionals using it. > > I'll have to look into this, but it probably just needs to sanity checking for the vm_extra and company. Aside from that, what is the original of the ebuild for eclipse that you are using? Also, which VM are you using? I haven't been able to quite reproduce this problem... Josh -- gentoo-java@gentoo.org mailing list