From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 81742 invoked by alias); 8 Apr 2015 20:03:22 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 81694 invoked by uid 89); 8 Apr 2015 20:03:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.9 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 08 Apr 2015 20:03:21 +0000 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (Postfix) with ESMTPS id DCE2D8E68D; Wed, 8 Apr 2015 20:03:19 +0000 (UTC) Received: from host1.jankratochvil.net (ovpn-116-21.ams2.redhat.com [10.36.116.21]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t38K3Fux026651 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 8 Apr 2015 16:03:18 -0400 Date: Wed, 08 Apr 2015 20:03:00 -0000 From: Jan Kratochvil To: Paul_Koning@dell.com Cc: eliz@gnu.org, gdb-patches@sourceware.org, pmuldoon@redhat.com Subject: Re: [PATCH v2 7/9] compile: New 'compile print' Message-ID: <20150408200315.GA6777@host1.jankratochvil.net> References: <20150406172623.31404.58833.stgit@host1.jankratochvil.net> <20150406172716.31404.8551.stgit@host1.jankratochvil.net> <83bnj1jgsw.fsf@gnu.org> <021F612D-0E51-44ED-BA7F-894A8B51F5BF@dell.com> <20150406175250.GA314@host1.jankratochvil.net> <0484210C-BBE9-4C64-8F51-7DC74ACF8F86@dell.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Content-Disposition: inline In-Reply-To: <0484210C-BBE9-4C64-8F51-7DC74ACF8F86@dell.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-IsSubscribed: yes X-SW-Source: 2015-04/txt/msg00306.txt.bz2 On Mon, 06 Apr 2015 19:58:31 +0200, Paul_Koning@dell.com wrote: > On Apr 6, 2015, at 1:52 PM, Jan Kratochvil wrote: > > On Mon, 06 Apr 2015 19:49:28 +0200, Paul_Koning@dell.com wrote: > > > Also, “the compiler” begs the question: which one, i.e., how is “the > > > compiler” found? > > > > A complicated way, for non-native targets an appropriate cross-gcc should be > > found. > > Ok. I would not expect that to be documented in NEWS, but it seems like it > should be in gdb.texinfo or some similar spot. I have a whole pile of > cross-compilers in various places; I would need to understand what the > algorithm looks like to be able to ensure that the correct one is found. I find it should "just work": gdb: compile_to_object(): ARCH(-[^-]*)?-OS ARCH=gdbarch_gnu_triplet_regexp i386/x86_64: (x86_64|i.86) s390/s390x: s390x? *: bfd_arch_info::arch_name OS=gdb_osabi_names.regexp GNU/Linux: linux(-gnu)? *: "" gcc: libcc1_set_arguments()->find_compiler(): $PATH Just make your cross-compiler accessible by $PATH and cross your fingers. If it does not work it is a bug that should be filed+fixed. It is questionable whether it should be in GDB manual or GCC manual. So far the GCC manual does not mention GCC's libcc1 GDB interface at all. Jan