From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 6642C1384B4 for ; Tue, 3 Nov 2015 14:56:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 04A58E08A5; Tue, 3 Nov 2015 14:56:32 +0000 (UTC) Received: from mail-ob0-f179.google.com (mail-ob0-f179.google.com [209.85.214.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 10FCEE07B3 for ; Tue, 3 Nov 2015 14:56:31 +0000 (UTC) Received: by obdgf3 with SMTP id gf3so13861377obd.3 for ; Tue, 03 Nov 2015 06:56:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=QOQYYkjx1czXSGMyQ5GjvUhz34U8lX9/dHhdTuBX7Jk=; b=nceCqgz++Tc5T8jkldNDPruVsD2x/DVS6AEwhtmUY8mMTSZwYn/Ovi6crmPs47HWhU Csg2HLiFC24VHiYMVKRUa745rjH01OQI0/N21qOrBBwROugvidKp9Wl9Vifvfs9X4N0m lnbXPuG+93PdN7akoSQ0tmgOFw34AdsAG5sozxcpzGh1XLbmQOhuawr9hztcr4UbJYt9 ecOsa28O0eekdn9dhMkRclIWG9rfoTQscTCgq8OdsZeIEmfd3D8Li4KnnRshV35+A8gP 4tcCb9AD/PAHiNMu+lmgInW7qQrOPLgV0wKFlHyeui6tZp9uq2bRxegd0ArFWFYdAitb sNJg== X-Received: by 10.60.140.228 with SMTP id rj4mr19386161oeb.15.1446562590489; Tue, 03 Nov 2015 06:56:30 -0800 (PST) Received: from linux1 (cpe-66-68-34-247.austin.res.rr.com. [66.68.34.247]) by smtp.gmail.com with ESMTPSA id p3sm10881774oei.9.2015.11.03.06.56.29 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Nov 2015 06:56:29 -0800 (PST) Sender: William Hubbs Received: (nullmailer pid 8141 invoked by uid 1000); Tue, 03 Nov 2015 14:56:29 -0000 Date: Tue, 3 Nov 2015 08:56:29 -0600 From: William Hubbs To: gentoo-dev@lists.gentoo.org Cc: Justin Lecker Subject: Re: [gentoo-dev] [PATCH v1] enable gccgo for all platform Message-ID: <20151103145629.GA8071@linux1> Mail-Followup-To: gentoo-dev@lists.gentoo.org, Justin Lecker References: <1446484646-14770-1-git-send-email-lenohou@gmail.com> <5637C3AE.50609@gentoo.org> <20151102223835.GA2830@whubbs1.ad.gaikai.biz> <563865FC.7060206@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" Content-Disposition: inline In-Reply-To: <563865FC.7060206@gentoo.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-Archives-Salt: 4b17ca53-0753-417c-81cf-f190f6b60d6b X-Archives-Hash: 6d9bf03c28692283e8dd12dbab7d5a0e --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 03, 2015 at 08:45:00AM +0100, Justin (jlec) wrote: > On 02/11/15 23:38, William Hubbs wrote: > > On Mon, Nov 02, 2015 at 09:12:30PM +0100, Justin Lecher (jlec) wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA512 > >> > >> How about a virtual here? > >=20 > > I don't see that working out to well because the compilers are > > completely different from each other. As I said, the reference > > implementation of the go language is dev-lang/go and the other one, that > > is part of gcc, as I understand it, is not quite as fully developed as > > dev-lang/go. > >=20 > > Thanks, > >=20 > > William > >=20 >=20 > Hi William, >=20 > but instead of adding >=20 > DEPEND=3D"||=B7( > >=3Ddev-lang/go-1.4 > >=3Dsys-devel/gcc-5.1.0:=3D[go] =20 The || dependencies you list should not be needed in most cases. As has been pointed out in the thread so far, gcc-5 only supports go-1.4. dev-lang/go is at 1.5, so really the only thing that should be built with gccgo is dev-lang/go. Also, the golang eclasses are designed to work with dev-lang/go, so they do not need a dependency on gccgo. Starting with go-1.5, most of the tools themselves are written in Go, so you need an earlier version of Go installed to build it (this is where I think I can use gccgo), but I'm not convinced yet about making it a virtual. > Another problem which you have with these split deps is the following. Im= agine > the user has gcc-5[go] installed, which fullfills the dependency requirem= ent. > But she selected gcc-4.9 as the active compiler, which doesn't have go su= pport. > The build will fail. For fortran we test in pkg_setup if we have a working > fortran compiler present. You would need to do the same for go compiler. The issue I see is a user could have gcc-5[go] and go-1.6 installed in the future. In that case, you would have packages that build with go-1.6 but not gcc-5[go], so gcc-5[go] would not fulfill the requirement. I see gcc-5[go] as a separate Go compiler, but it will always be behind dev-lang/go, so you will have things that build with dev-lang/go but not gccgo. Also, the commands to do the builds are completely different depending on which one you are using. I'm not sure of a way to deal with those issues in a virtual like you propo= se. William --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlY4yx0ACgkQblQW9DDEZTh9gwCbBjXj59AiGlLk9yD1TeYr0yJL XIYAoJK01ZnTQ3R3P8kIMPnx0xyZPvv5 =bc4l -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm--