From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25802 invoked by alias); 4 May 2013 17:22:41 -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 25758 invoked by uid 89); 4 May 2013 17:22:34 -0000 X-Spam-SWARE-Status: No, score=-5.1 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.1 Received: from mail-vb0-f52.google.com (HELO mail-vb0-f52.google.com) (209.85.212.52) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Sat, 04 May 2013 17:22:33 +0000 Received: by mail-vb0-f52.google.com with SMTP id p13so2117435vbe.11 for ; Sat, 04 May 2013 10:22:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding :x-gm-message-state; bh=dCNpeyXhwOQjC4Ulg49iNoxsvtR8YN0j/oVwbzazHlI=; b=ikWaeGxflBxsZMRcUgwh/sww9M/Qd7Vsuh2i76T2FpoW5rqchcNA91oegjOVBZzB+F fajLWO4rKPb29rS/I/zxjQVwZTVlnV8lnYyORNjrWtZXJx6c4tkKm4JH3InbGELEZ2Q+ BKPCCn2PwazmJc6N0rA1Q/nY/++WTuDhZdO8u0ssSt88Eeb67O0JciO08aHq4e7z/eFA vjW1atoMMpXKvsaR+rHr99cl9x7STPaGhMuq7K586cuYhtx8QfBc78PS53EefnXQ2aHi dRMA89pInNj62g9CHU7q+I0cfbvMIvcoFrOCgdiYXG+3WjS3G2GEbfI1LxXDZ3jksRkT f9lw== MIME-Version: 1.0 X-Received: by 10.220.153.69 with SMTP id j5mr4979224vcw.35.1367688152009; Sat, 04 May 2013 10:22:32 -0700 (PDT) Received: by 10.220.173.7 with HTTP; Sat, 4 May 2013 10:22:31 -0700 (PDT) In-Reply-To: References: <8738u4sc19.fsf@kepler.schwinge.homeip.net> Date: Sat, 04 May 2013 17:22:00 -0000 Message-ID: Subject: Re: [patch] for mig check in GDB's configure From: Doug Evans To: =?UTF-8?B?6ZmG5bKz?= Cc: Thomas Schwinge , bug-hurd@gnu.org, gdb-patches Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQlE8TqOPbE9Ulp3dADL9OkzVvCZPxFK9kfdHoblKjfjlH+meJPCdDn4rW++gEkQqZd8TXrq8XQLD+C5UBpngd9dDLp36jKdPYeywp7V5Rzc9Tvv9LZXCSmUmd+EmWAgXDmM3JfMviKNV+MLpCipIqW7+OxH2hISFbJGfYKZ4Rx1dL9FmekhVikrSCTcWr/MCe4FdTNT5fl7V+eArlp9WvfcSU6MYg== X-SW-Source: 2013-05/txt/msg00078.txt.bz2 On Fri, May 3, 2013 at 3:43 AM, =E9=99=86=E5=B2=B3 wrote: >> Hmm, I think that instead of only examining the host system, $host, this >> also needs to examine the target system, $target. (Please tell if the >> difference between build, host, and target system is not clear to you.) >> The MIG tool is used to generate files (from RPC definition files) that >> are used by the native GDB port for GNU Hurd (which, of couse, is the >> only GNU Hurd port that currently exists.) But if someone, for example, >> builds GDB targeting mips-linux-gnu on a GNU Hurd system, they would not >> need the MIG tool. >> > > To my knowledge now, $target just need to set when building a compiler > which specify which plateform your compiler generate code for. When we > build GDB, it is trivial to check the variable. > In your example, builds GDB targeting mips-linux-gnu means the GDB is > running on mips-linux. So we only need to set the > $host=3Dmips-linux-gnu, $build=3D*-*-gnu. > Maybe I have got a wrong understanding about these gcc terms. I can run gdb on an x86 system and debug a program running on a mips system via gdbserver (or some other program that speaks gdb's remote protocol). --build =3D system you're building the tool on --host =3D system the tool will run on --target =3D system the tool will handle or target (generate code for in the case of gcc, debug in the case of gdb) [These terms are common to all GNU tools, not just gcc btw.] All three can be different for gdb as well as gcc. So for example I *could*, given appropriately ported tools, build gdb on x86, run it on mips, and have it debug programs running on arm.