public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@golang.org>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
		"gofrontend-dev@googlegroups.com"
	<gofrontend-dev@googlegroups.com>,
	Lynn Boger <laboger@linux.vnet.ibm.com>
Subject: Re: Patch RFA: Support for building Go tools
Date: Fri, 09 Jan 2015 21:24:00 -0000	[thread overview]
Message-ID: <CAOyqgcUpbmsbqr-PpMugO2xZOZe183-ogOsoUMvd8mEQ06kjww@mail.gmail.com> (raw)
In-Reply-To: <54AFF673.10202@gnu.org>

On Fri, Jan 9, 2015 at 7:40 AM, Paolo Bonzini <bonzini@gnu.org> wrote:
>
>
> On 09/01/2015 15:24, Ian Lance Taylor wrote:
>>> >
>>> > This should work automatically, the only difference is that you must
>>> > omit $(LIBGODEP) from the dependencies.
>> What will happen if there is no installed gccgo at the right version?
>
> Compilation fails.
>
>> What should happen?
>
> Compilation fails. :)
>
>> I haven't been keeping track--will the build machinery now build a
>> build-x-host Go compiler?
>
> No, but the build machinery should point the Makefile variables to a
> build-x-host tool from the PATH.  If it doesn't, you need to modify the
> toplevel configure.ac and Makefile.tpl.

I forgot: there is another problem with using the build-x-host
compiler to build the tools.  That will build them with the host
version of the go/build package, which will set the default values for
the architecture and OS to be that of the host, not the target.  They
should really be the target.  We can fix this, but it will require
some thought.

I plan to commit the version that does not do anything when building a
cross-compiler in order to proceed.  The situation will not be worse
than it is today.

Ian

  reply	other threads:[~2015-01-09 21:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08 21:35 Ian Lance Taylor
2015-01-08 21:51 ` pinskia
2015-01-09  8:54 ` Paolo Bonzini
2015-01-09  9:10   ` Paolo Bonzini
2015-01-09 14:28   ` Ian Lance Taylor
2015-01-09 15:51     ` Paolo Bonzini
2015-01-09 21:24       ` Ian Lance Taylor [this message]
2015-01-09 21:29         ` Ian Lance Taylor
2015-01-14 19:30 Uros Bizjak
2015-01-15 22:18 ` Ian Lance Taylor

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=CAOyqgcUpbmsbqr-PpMugO2xZOZe183-ogOsoUMvd8mEQ06kjww@mail.gmail.com \
    --to=iant@golang.org \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gofrontend-dev@googlegroups.com \
    --cc=laboger@linux.vnet.ibm.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).