Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] add gdb.threads/pthread_cond_wait.* in fnchange.lst
Date: Thu, 20 May 2004 05:47:00 -0000	[thread overview]
Message-ID: <ur7tfa8za.fsf@gnu.org> (raw)
In-Reply-To: <20040519220040.GK10684@gnat.com>

> Date: Wed, 19 May 2004 15:00:40 -0700
> From: Joel Brobecker <brobecker@gnat.com>
> 
>         * config/djgpp/fnchange.lst: Add entries for pthread_cond_wait.exp
>         and pthread_cond_wait.c.
> 
> I must admit that i was confused a bit by what I saw. For instance,
> I saw that we didn't translate the "testsuite" part in the path,
> although it has 9 characters. Nor did we translate directory names
> such as "gdb.base" or "gdb.arch" (extension has more than 3 chars).

The OS truncates the names to 8+3 limits automatically when the
tarball is untarred; that truncation is an integral part of the
operation of the DOS system calls which work with file names.  So the
only 2 problems that we need to fix with entries in fnchange.lst are:

  - When 2 or more files produce the same name after truncation to
    8+3;

  - When a file's name includes characters that are disallowed in DOS
    file names.  Examples of such characters include `+', `,', `:',
    and a few more.  File names with leading dots, like .gdbinit, are
    also not allowed.

The fnchange.lst file is submitted to a program used to untar the
distribution (see djunpack.bat for the gory details), and which
performs the renaming on the fly.  That program automatically renames
some of the files whose names are invalid on DOS and are frequently
used in GNU software, like foo.c++, .foobar, etc.  This is another
reason that some invalid names might be missing from fnchange.lst.


  reply	other threads:[~2004-05-20  5:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19 22:00 Joel Brobecker
2004-05-20  5:47 ` Eli Zaretskii [this message]
2004-05-20 16:27   ` Joel Brobecker
2004-05-21 16:38     ` Eli Zaretskii
2004-05-21 17:25       ` Joel Brobecker
2004-05-20  2:57 Michael Elizabeth Chastain
2004-05-20  5:40 ` 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=ur7tfa8za.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.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