From: Ryan Hill <rhill@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [PATCH v1] enable gccgo for all platform
Date: Sun, 15 Nov 2015 02:34:41 -0600 [thread overview]
Message-ID: <20151115023441.3ce747ee@caribou.gateway.pace.com> (raw)
In-Reply-To: 1446484646-14770-1-git-send-email-lenohou@gmail.com
[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]
On Mon, 2 Nov 2015 12:17:26 -0500
Leno Hou <lenohou@gmail.com> wrote:
> 1. go compiler only support x86 platform
> 2. gcc 5 includes go command to build go apps
> 3. for coreos enablement, it's use gcc 5 to build go apps
> diff --git a/app-admin/consul-template/consul-template-0.9.0-r1.ebuild
> b/app-admin/consul-template/consul-template-0.9.0-r1.ebuild index
> cbc1059..a24ec80 100644 ---
> a/app-admin/consul-template/consul-template-0.9.0-r1.ebuild +++
> b/app-admin/consul-template/consul-template-0.9.0-r1.ebuild @@ -14,7 +14,10
> @@ LICENSE="MPL-2.0" SLOT="0"
> IUSE="test"
>
> -DEPEND=">=dev-lang/go-1.4:=
> +DEPEND="|| (
> + >=dev-lang/go-1.4:=
> + >=sys-devel/gcc-5.1.0:=[go]
> + )
> test? ( dev-go/go-tools )
> app-admin/consul
> app-admin/vault"
You cannot simply have a dependency on gcc like this. Just because there is a
compiler installed that satisfies the dependency doesn't mean that compiler is
the one currently being used. I could have gcc 5 with go support installed
while using gcc 6 without go. You need to either do a compile test or query
the compiler in some way to ensure the needed support is there. Look at the
fortran virtual and fortran-2 eclass for an example.
--
Ryan Hill psn: dirtyepic_sk
gcc-porting/toolchain/wxwidgets @ gentoo.org
47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 475 bytes --]
next prev parent reply other threads:[~2015-11-15 8:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 17:17 [gentoo-dev] [PATCH v1] enable gccgo for all platform Leno Hou
2015-11-02 17:30 ` William Hubbs
2015-11-02 20:12 ` Justin Lecher (jlec)
2015-11-02 22:38 ` William Hubbs
2015-11-03 2:40 ` Leno Hou
2015-11-03 7:45 ` Justin (jlec)
2015-11-03 14:56 ` William Hubbs
2015-11-03 15:09 ` James Le Cuirot
2015-11-04 23:46 ` William Hubbs
2015-11-04 2:41 ` Leno Hou
2015-11-03 20:35 ` Zac Medico
2015-11-15 8:34 ` Ryan Hill [this message]
2015-12-21 22:52 ` William Hubbs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151115023441.3ce747ee@caribou.gateway.pace.com \
--to=rhill@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox