From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, go]: Restore bootstrap
Date: Fri, 25 Jul 2014 06:51:00 -0000 [thread overview]
Message-ID: <53D1FAA1.4010400@suse.cz> (raw)
In-Reply-To: <CAKOQZ8za4jFtARfUoWQZF6GoVTy_0xi8KNCrEC-N7fh7F7kKvQ@mail.gmail.com>
On 07/25/2014 03:51 AM, Ian Lance Taylor wrote:
> On Thu, Jul 24, 2014 at 12:21 PM, Martin Liška <mliska@suse.cz> wrote:
>> On 07/24/2014 07:57 PM, Uros Bizjak wrote:
>>> Hello!
>>>
>>> 2014-07-24 Uros Bizjak <ubizjak@gmail.com>
>>>
>>> * go/go-gcc.cc (Gcc_backend::global_variable_set_init): Rename
>>> symtab_get_node to symtab_node::get.
>>>
>>> Tested on x86_64-linux-gnu and committed to mainline SVN.
>>>
>>> Uros.
>> Hello,
>> thank you for your fix. As I see my configure output:
>>
>> $ ../configure --disable-bootstrap --enable-checking=release
>> --enable-languages=all --disable-multilib
>>
>> The following languages will be built: c,c++,fortran,java,lto,objc
>> *** This configuration is not supported in the following subdirectories:
>> gnattools target-libada target-libgo target-libbacktrace
>> (Any other directories should still work fine.)
>>
>> I thought with 'all' I cover all front-ends, is it really intended behavior
>> that go is disable by 'all'?
> Yes, --enable-languages=all is the default, so it only builds the
> frontends that are enabled by default, so it does not build the Go or
> Ada frontends. I know it doesn't make much sense.
>
> Ian
I would suggest to replace currently used 'all' to 'default'. And 'all' can be really used for all possible frontends we have :) I know it changes the behavior, but I hope I makes sense?
Thank you,
Martin
next prev parent reply other threads:[~2014-07-25 6:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 18:14 Uros Bizjak
2014-07-24 20:08 ` Martin Liška
2014-07-25 3:11 ` Ian Lance Taylor
2014-07-25 6:51 ` Martin Liška [this message]
2014-07-28 11:03 ` Gerald Pfeifer
2014-07-28 16:28 ` Mike Stump
2014-07-29 9:19 ` Martin Liška
2014-07-29 17:02 ` Mike Stump
2014-07-29 20:47 ` Martin Liška
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=53D1FAA1.4010400@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).