Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Fix fnchange.lst
Date: Sun, 20 Sep 2009 17:49:00 -0000	[thread overview]
Message-ID: <83my4pv78y.fsf@gnu.org> (raw)
In-Reply-To: <20090920161048.GX8910@adacore.com>

> Date: Sun, 20 Sep 2009 09:10:48 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
>     http://www.sourceware.org/gdb/ari/
> 
> I see there are 10 warnings remaining. Are these actually fixable?

Not easily: they belong to libdecnumber and gnulib, which are compiled
into the DJGPP port.  To fix those, I need to add stuff to
gdb/config/djgpp to actually edit some source files, not just rename
files during unpacking (which is what fnchange.lst does).

It's on my TODO, but when I will get to it is anybody's guess.  Not
that too many people on the DJGPP forum are crying bloody murder for
lack of support of the build on plain DOS systems...

> I don't quite understand what the warnings say, because I can't find
> files such as decimal1.h, for instance.

The original output of doschk is mangled by the ARI script, as part of
accounting for fnchange.lst renaming, so the first of the two names it
complains about is already 8+3-butchered.  Run "find . | doschk" in
the source tree, and you will see the original file names that clash
after 8+3 truncation.

> I don't think you'll have write priviledges. If you want, I can add
> your key to the authorized_keys, or I can commit the changes for you.

The latter would be more than enough.  I will see if I can find time
to craft a script that you wanted.

Thanks.


  reply	other threads:[~2009-09-20 17:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-19  9:50 Eli Zaretskii
2009-09-19 15:58 ` Joel Brobecker
2009-09-19 17:47   ` Eli Zaretskii
2009-09-20 16:11     ` Joel Brobecker
2009-09-20 17:49       ` Eli Zaretskii [this message]
2009-09-20 19:48         ` Eli Zaretskii
2009-09-21 16:56           ` Joel Brobecker
2009-10-01 17:01           ` Joel Brobecker
2009-10-02 11:43             ` Eli Zaretskii
2009-10-02 15:25               ` Joel Brobecker

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=83my4pv78y.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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