Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: muller@ics.u-strasbg.fr, gdb-patches@sourceware.org,
	brobecker@adacore.com
Subject: Re: GDB ARIndex cleanup
Date: Thu, 02 Apr 2009 19:40:00 -0000	[thread overview]
Message-ID: <ur60aj13o.fsf@gnu.org> (raw)
In-Reply-To: <1238685112.3236.18.camel@localhost.localdomain>

> From: Thiago Jung Bauermann <bauerman@br.ibm.com>
> Cc: muller@ics.u-strasbg.fr, gdb-patches@sourceware.org,
>         Joel Brobecker <brobecker@adacore.com>
> Date: Thu, 02 Apr 2009 12:11:52 -0300
> 
> El vie, 27-03-2009 a las 17:03 +0300, Eli Zaretskii escribió:
> > Last, but not least: the libdecnumber/ directory and its
> > subdirectories have numerous file-name clashes:
> > 
> >     The following resolve to the same DOS file names:
> <snip>
> > Would it be possible to rename some of the files to resolve these
> > issues?  Again, it is not possible to use the fnchange.lst machinery
> > here, as these files are used during the DJGPP build.
> 
> libdecnumber is an external library which is imported into the GDB and
> GCC trees, so I believe you'd have to discuss this with the library's
> author.
> 
> The GCC folks seem to incorporate fixes directly to their copy (which
> then get copied to us), so perhaps they'll consider the renaming without
> involving upstream libdecnumber...

Like with gnulib (or maybe even more), I don't think I stand a chance
to get positive responses to my request for this, unless GDB supports
it as a whole project.

I guess I'm asking GDB to ask for this on behalf of the DJGPP port.


  reply	other threads:[~2009-04-02 19:40 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 15:29 Pierre Muller
2009-03-26 20:53 ` Eli Zaretskii
2009-03-27  8:23   ` Pierre Muller
2009-03-27  8:47     ` Eli Zaretskii
2009-03-27 14:12       ` Eli Zaretskii
2009-03-27 15:35         ` Eli Zaretskii
2009-04-02 15:12         ` Thiago Jung Bauermann
2009-04-02 19:40           ` Eli Zaretskii [this message]
2009-04-02 20:34             ` Joel Brobecker
2009-03-26 23:18 ` Joel Brobecker
2009-03-27  2:22   ` Daniel Jacobowitz
2009-03-27  8:43   ` Pierre Muller
2009-03-27 16:04     ` Joel Brobecker
2009-03-27 16:46       ` Daniel Jacobowitz
2009-04-14 23:06   ` [RFC] GDB ARIndex Linux rule cleanup Pierre Muller
2009-04-14 23:23     ` Mark Kettenis
2009-04-14 23:38       ` Pedro Alves
2009-04-14 23:41         ` Joel Brobecker
2009-04-15  7:06           ` Pierre Muller
2009-04-15  7:33           ` Eli Zaretskii
2009-04-15 14:00     ` Ulrich Weigand
2009-04-15 14:21       ` Pedro Alves
2009-04-15 15:32         ` Ulrich Weigand
2009-04-15 15:54           ` Pedro Alves
2009-04-15 14:25       ` Eli Zaretskii
2009-04-15 15:15         ` Daniel Jacobowitz
2009-04-15 15:23         ` Ulrich Weigand
2009-04-15 15:34           ` Mark Kettenis
2009-04-15 16:00             ` Eli Zaretskii
2009-04-15 16:04           ` Eli Zaretskii
2009-04-15 17:34             ` Ulrich Weigand
2009-04-15 18:07               ` Eli Zaretskii
2009-04-15 18:55                 ` Ulrich Weigand

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=ur60aj13o.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bauerman@br.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    /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