Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>, 	<drow@false.org>
Subject: RE: [RFC] Doschk.c and update-web-ari changes
Date: Fri, 26 Oct 2007 14:13:00 -0000	[thread overview]
Message-ID: <008801c817d0$ccb32cb0$66198610$@u-strasbg.fr> (raw)
In-Reply-To: <uprz2rz0b.fsf@gnu.org>



> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] On Behalf Of Eli Zaretskii
> Sent: Friday, October 26, 2007 11:45 AM
> To: Pierre Muller
> Cc: gdb-patches@sourceware.org; drow@false.org
> Subject: Re: [RFC] Doschk.c and update-web-ari changes
> 
> > From: "Pierre Muller" <muller@ics.u-strasbg.fr>
> > Cc: "'Eli Zaretskii'" <eliz@gnu.org>,
> > 	<drow@false.org>
> > Date: Fri, 26 Oct 2007 09:44:06 +0200
> >
> >   Here are the changes I made to doschk.c
> > and update-web-ari to get a better result.
> >
> >   The changes inside doschk.c are mainly aimed
> > to facilitate the correct handling by update-web-ari.
> 
> FWIW, I don't think it's a good idea to change doschk.c for this.
> This program is widely available and used, so it's better to modify
> our script to use doschk's output as-is; otherwise everyone will need
> to install a patched doschk to get things right, and also we will need
> to remember to keep a patched version where the ari script is run.

  I thought that this was a local file only,
is it part of the djgpp distribution?
  I found a directory named doschk
in src/utils but the directory is empty...


  Do you know if the file in the ss directory is the
same as your file? 
  Where is the main source located?

 
> >   As you will see, lots of these duplicates are
> > in directories that will probably not be in the DJGPP
> > gdb sources.
> 
> If you want to rely on the fact that some directories are omitted from
> the DJGPP source zip files, then I don't think it's right to do so,
> because the file-name conflicts are already resolved in those zip
> files anyhow.  What is important is that a DJGPP user could unpack the
> official GDB tarball using djunpack.bat without any problems.  This
> means that file-name conflicts in the official GDB tarball should be
> resolved either by renaming files or by adding lines to fnchange.lst.

  It should also be possible to do that.
I will just need to get the directory from the 
fullname part.
  Currently, with the cvs doschk.c sources,
I get this:
CHANGELO DOS 8.3 dup	4	Filename gdb/ChangeLog
					Filename gdb/ChangeLog-2006
					Filename opcodes/ChangeLog
					Filename opcodes/ChangeLog-2006
 
Which are of course two separate duplicates.

> > 	* doschk.c (fill_ent): Use lowercase characters.
> 
> Why?
> 
> > 	(display_problems): Also proint relative path with dos_name.
>                                  ^^^^^^
> You meant "print".

  Yes of course, sorry.

Pierre



  reply	other threads:[~2007-10-26 13:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26  7:56 Pierre Muller
2007-10-26 12:05 ` Eli Zaretskii
2007-10-26 14:13   ` Pierre Muller [this message]
2007-10-26 15:30     ` Eli Zaretskii

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='008801c817d0$ccb32cb0$66198610$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --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