From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9054 invoked by alias); 29 Oct 2014 10:37:35 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 9041 invoked by uid 89); 29 Oct 2014 10:37:33 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-wg0-f48.google.com Received: from mail-wg0-f48.google.com (HELO mail-wg0-f48.google.com) (74.125.82.48) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Wed, 29 Oct 2014 10:37:33 +0000 Received: by mail-wg0-f48.google.com with SMTP id m15so1507938wgh.35 for ; Wed, 29 Oct 2014 03:37:30 -0700 (PDT) X-Received: by 10.194.94.9 with SMTP id cy9mr2140457wjb.117.1414579050024; Wed, 29 Oct 2014 03:37:30 -0700 (PDT) Received: from [192.168.10.150] (net-37-117-142-149.cust.vodafonedsl.it. [37.117.142.149]) by mx.google.com with ESMTPSA id 4sm4709220wjx.39.2014.10.29.03.37.27 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Oct 2014 03:37:29 -0700 (PDT) Message-ID: <5450C366.5040909@gnu.org> Date: Wed, 29 Oct 2014 10:37:00 -0000 From: Paolo Bonzini User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Jakub Jelinek , Phil Muldoon , DJ Delorie , Alexandre Oliva , Ralf Wildenhues CC: gcc-patches@gcc.gnu.org Subject: Re: libcc1 References: <20141029103151.GQ10376@tucnak.redhat.com> In-Reply-To: <20141029103151.GQ10376@tucnak.redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2014-10/txt/msg03037.txt.bz2 On 10/29/2014 11:31 AM, Jakub Jelinek wrote: > It would be nice to have libcc1 built just once, not bootstrap it, but > it is a build module, is that possible? > In toplevel configure.ac I'm seeing: > host_tools="texinfo flex bison binutils gas ld fixincludes gcc cgen sid sim gdb gprof etc expect dejagnu m4 utils guile fastjar gnattools libcc1" Stuff such as texinfo and flex is in host_tools just as a relic of the old Cygnus tree. fixincludes is in there for running it after installation. The ones that matter in the common case are biuntils, gas, ld, gcc, gdb, gnattools and of course libcc1. > shouldn't libcc1 be in build_tools instead? > I mean, it is a library meant to be dlopened by gdb and gcc > plugin that uses that library, so in canadian-cross should be > for the build target, where the resulting compiler will be run > and where gdb will be run. That is host, not build. Build is the system you are on. Say you're cross-building a native mingw compiler and debugger: build = i686-pc-linux-gnu host = i686-pc-mingw (or whatever they use these days) target = i686-pc-mingw You cannot link build-libcc1 (for i686-pc-linux-gnu) into host-gcc or host-gdb. But you surely know this, so perhaps it's me who is missing something.