Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>,
	Masaki Muranaka <monaka@monami-software.com>
Subject: Re: [doc] Avoid conflicts between gdb and cross-gdb.
Date: Sat, 02 Aug 2014 12:58:00 -0000	[thread overview]
Message-ID: <3531941.zJjkhARRvn@vapier> (raw)
In-Reply-To: <20140801150722.GJ14672@adacore.com>

[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]

On Fri 01 Aug 2014 08:07:22 Joel Brobecker wrote:
> On Tue, Jul 01, 2014 at 05:18:25PM +0900, Masaki Muranaka wrote:
> > After applied hash 43662968, gdb.1 and other man pages are not added
> > target triplet even if we configure with --target=.
> > 
> > It causes conflicts on some distributions.
> > And uninstall rules requires $(transform) variable.
> > 
> > I think this should be fixed by adding the target triplet.
> > 
> > >From e89f13505363c41b683a1b02125f1fea02aa486c Mon Sep 17 00:00:00 2001
> > 
> > From: Masaki Muranaka <monaka@monami-software.com>
> > Date: Tue, 1 Jul 2014 17:08:15 +0900
> > Subject: [PATCH] Add target triplet to man files.
> > 
> > ---
> > 
> >  gdb/doc/ChangeLog   | 4 ++++
> >  gdb/doc/Makefile.in | 6 ++++--
> >  2 files changed, 8 insertions(+), 2 deletions(-)
> > 
> > diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
> > index 7c1d1bb..10b1114 100644
> > --- a/gdb/doc/ChangeLog
> > +++ b/gdb/doc/ChangeLog
> > @@ -1,3 +1,7 @@
> > +2014-07-01  Masaki Muranaka  <monaka@monami-software.com>
> > +
> > + * Makefile.in : Add target triplet to man files.
> 
> The patch makes sense to me.  Unfortunately, when I tried to test
> the patch, it did not apply.  Attached is what I ended up pushing
> (I kept you as the author off the git commit).

along these lines, should we also transform the default gdb datadir (for 
python and xml files) ?  and info pages ?  looking at my cross-debugger 
installs, those are the other big missing pieces.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-08-02 12:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01  8:18 Masaki Muranaka
2014-08-01 15:07 ` Joel Brobecker
2014-08-02 12:58   ` Mike Frysinger [this message]
2014-08-06 13:24     ` Joel Brobecker
2014-08-06 17:05       ` Eli Zaretskii
2014-08-06 17:37         ` Joel Brobecker
2014-08-06 17:40           ` Eli Zaretskii
2014-08-06 19:53             ` Joel Brobecker
2014-08-06 20:05               ` Doug Evans
2014-08-06 21:34                 ` Joel Brobecker
2014-08-07 15:43                   ` Eli Zaretskii
2014-08-07 15:53                     ` Joel Brobecker
2014-08-08  6:19                     ` Mike Frysinger
2014-08-21 14:26                       ` Pedro Alves
2014-08-21 15:00                         ` Eli Zaretskii
2014-08-07  0:21         ` Mike Frysinger
2014-08-07 15:50           ` Eli Zaretskii
2014-08-08  2:53             ` Mike Frysinger
2014-08-08  6:05               ` Eli Zaretskii
2014-08-08  7:17                 ` Mike Frysinger
2014-08-21 14:30                   ` Pedro Alves
2014-08-06 22:55       ` Mike Frysinger

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=3531941.zJjkhARRvn@vapier \
    --to=vapier@gentoo.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=monaka@monami-software.com \
    /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