From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21911 invoked by alias); 8 Aug 2014 06:19:47 -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 21900 invoked by uid 89); 8 Aug 2014 06:19:46 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.4 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: smtp.gentoo.org Received: from smtp.gentoo.org (HELO smtp.gentoo.org) (140.211.166.183) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Fri, 08 Aug 2014 06:19:45 +0000 Received: from vapier.localnet (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 5A88634006B; Fri, 8 Aug 2014 06:19:43 +0000 (UTC) From: Mike Frysinger To: Eli Zaretskii Cc: Joel Brobecker , dje@google.com, gdb-patches@sourceware.org, monaka@monami-software.com Subject: Re: [doc] Avoid conflicts between gdb and cross-gdb. Date: Fri, 08 Aug 2014 06:19:00 -0000 Message-ID: <1554189.EX2Nlz1ClI@vapier> User-Agent: KMail/4.13.3 (Linux/3.14.2; KDE/4.13.3; x86_64; ; ) In-Reply-To: <8361i4nw49.fsf@gnu.org> References: <20140806213412.GD4881@adacore.com> <8361i4nw49.fsf@gnu.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2225048.3YHJ7nAUjG"; micalg="pgp-sha1"; protocol="application/pgp-signature" X-IsSubscribed: yes X-SW-Source: 2014-08/txt/msg00162.txt.bz2 --nextPart2225048.3YHJ7nAUjG Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" Content-length: 1519 On Thu 07 Aug 2014 18:43:34 Eli Zaretskii wrote: > > (1) Should we support out of the box distinct targets to be installed > > at the same prefix? > > (2) Should the name of some of those files match the name of > > the executable? > >=20 > > For (1), I'm leaning towards a "not necessary", but we can perhaps > > find a middle ground. I don't know the various defaults to really > > help making a decision without spending some time to look at it. > > Either way, I have a fairly neutral opinion, so I am happy following > > the group. > >=20 > > For (2), I thought that for the man page, and (to some degree, since > > I know little about info) the "info" page as well. But again, > > I don't really have much of opinion on that. >=20 > But "info FOO" does not mean "show me the file FOO", it means "show me > the manual whose DIR entry is FOO". (Although the stand-alone Info > reader falls back to the file interpretation if it doesn't find FOO in > the DIR menu.) >=20 > And the Info system doesn't really support more than one manual for > the same tool anyway. >=20 > So I think, unlike the man pages, the Info manual should not be > renamed. yes, you'd actually have to rewrite the base node name so that instead of=20 identifying itself as "gdb" it'd be "${target}-gdb" (i.e. apply the program= =20 transformation). then doing `info sh4-linux-gnu-gdb` would give you the=20 correct man page. this matches the man page behavior where you can do `man= =20 sh4-linux-gnu-gdb` and such. -mike= --nextPart2225048.3YHJ7nAUjG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABAgAGBQJT5GwFAAoJEEFjO5/oN/WB/G0P/0ZwEnYpMSE4giohdorzWE5n n63X6bUi1yPpsC5odOEIkxP/bO0nNfeDyFl7IgiWPv4xtF8CdJVO+amYEjCrVyRT C63kDaQ9ryRdUnwgnVtTNNo4eQ1JaLmBgp/7DRPmrJq3xFUtQCAzCNqsK4f54Gbh ZTRv3s+FSC1njFiK555O5FgxScbVW4G9BnIIaedFcJ97QPScAEMyw/n1lAmV0513 koKrhgNJ58RT0uGhze9oiZ9cw8q/xRnnpr/tguUhSW2B1dBs/bpuwp5GsNIDqCka kNVHoC24S3eB0YsRuHLl8siu/m+SKycWtVZc9HZrHZ/ouhJJ+Cf90urrpl5FKNOW Lx9PFEbarMFpkZpuaXHspzP0ycxsA+cqOfxHY+HVBFqvRLnVfMQyDCRWyD9jtP79 AmVyx+deyDEYV4jtrVksRf40Oiub/lYvUaomxOCaz8lHReIaGqa9K8NEKF/SlNDo nKuWutr3ybd0TY51YQ4hIbKR+xJ5P2dXm+g3hInjLWpbCiOifdMmV+m8++CrkwjA HvMMMqJv848WkXcwuvpJ6pF8xHnN9p5quM4QNrcsJ4StPxJaO3iR6D7YFJ8wx6/1 7DJ6LBRUOaxuGtru+7NshV8T2hUlS2uV4XNbLymhyxJe6LTsQyLuD1oy9NHYoTKI 16sHuV2pZ3UhL3oPRUmR =hemZ -----END PGP SIGNATURE----- --nextPart2225048.3YHJ7nAUjG--