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.50) id 1EhHKn-0000hy-3k for garchives@archives.gentoo.org; Wed, 30 Nov 2005 02:04:37 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jAU249U6008198; Wed, 30 Nov 2005 02:04:09 GMT Received: from sommereik.ii.uib.no (sommereik.ii.uib.no [129.177.16.236]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jAU249To003541 for ; Wed, 30 Nov 2005 02:04:09 GMT Received: from karlkalleberg.uwaterloo.ca ([129.97.92.44]:37632) by sommereik.ii.uib.no with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43) id 1EhHKK-0000qi-UL; Wed, 30 Nov 2005 03:04:09 +0100 Message-ID: <438D08A5.5000600@gentoo.org> Date: Wed, 30 Nov 2005 03:04:21 +0100 From: Karl Trygve Kalleberg Organization: Gentoo Foundation User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en 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: Joshua Nichols CC: gentoo-java@lists.gentoo.org Subject: [gentoo-java] Re: filtering compilers for ejavac/eant References: <2293c7bf0511141635s358df41bjda4febf14770827b@mail.gmail.com> In-Reply-To: <2293c7bf0511141635s358df41bjda4febf14770827b@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: d7bea2ef-a7b9-446f-8953-67f3ddf52470 X-Archives-Hash: d7b5b55f394f1d46891ab5b54366020e Joshua Nichols wrote: > Salutations, Indeed:) > I've been doing a little work on axxo's overlay recently, particularly > with choosing a sane compiler, ie it supports the desired -source and > -target. It seems there's a number of packages that jikes doesn't like > (surprise). I was talking with axxo about how to handle this, and > wanted some input from you. > > The current way of handling jikes is to not use eant/ejavac when the > package doesn't work with all the compilers. I'm not particularly fond > of this, because it doesn't give any indication that the package > doesn't work with a particular compiler. > > Instead, I think an ebuild should know that it doesn't work. As its > implemented, you can specify JAVA_PKG_FILTER_COMPILER to specify a > list of compilers not to use. I think that this should be used in > ebuilds that don't work with jikes (or alternatively, have a function > which handles this modifying this variable). > > Axxo had some reservations about this, because he thought it wouldn't > be much better than the old way of doing it with use flags. I don't > think this is quite the case though, you don't get 'use flag > pollution' with multiple compilers, and that most packages work with > all the compilers. > > Please let me know what you think. Well, we need to come with *some* solution. As I see it, there are essentially two choices: 1a) For each package, we explictly list the compilers we know this package works with. This can be done in src_compile, via an eclass function; java-pkg_declare-compilers "javac ecj jikes". 1b) Same as 1a, but by default, we resort to a JAVA_SUPPORTED_COMPILERS variable defined in the java-pkg.eclass as the default setting. 2a) We do your filtering stuff. 2b) We define a fancy-schmancy filter function in the spirit of flag-o-matic, java-pkg_filter-compilers "jikes", and invoke this in src_compile before eant/ejavac/ewhatever For now, I don't see any other sane alternatives. My personal favourite is 2b, since there is already a long standing precedence with flag-o-matic on this. -- Karl T -- gentoo-java@gentoo.org mailing list