Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: brobecker@gnat.com, gdb-patches@sources.redhat.com
Subject: Re: [patch] add gdb.threads/pthread_cond_wait.* in fnchange.lst
Date: Thu, 20 May 2004 05:40:00 -0000	[thread overview]
Message-ID: <usmdva9cl.fsf@gnu.org> (raw)
In-Reply-To: <20040520025754.1761C4B104@berman.michael-chastain.com>

> Date: Wed, 19 May 2004 22:57:54 -0400 (EDT)
> From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
> 
> My understanding is that the test suite does not actually *run*
> on djgpp.  So the files just need to un-tar cleanly, which means
> only one '.' in the filename and no '+' and the default truncation
> to 8.3 has to give unique names.  So your files would have unpacked
> to testsuit/gdb.thr/pthread_.exp and testsuit/gdb.thr/pthread_.c
> and that would be okay (just barely, because of pthreads.exp).
> 
> Eli is the expert on this ... Eli?

You are absolutely right.

Note that, while the test suite cannot be run with the DJGPP build
(because `expect' needs async subprocesses that DJGPP doesn't
support), even if it could be run, the truncated names would work.
That is because, when a program tries to open a file whose name is
pthread_cond_wait.exp, the OS silently truncates that to the 8+3
limits, yielding pthread_.exp and looks for a file by that truncated
name.  That's why we can compile GDB itself (which involves the
compiler, Make, the linker, etc. having to open the source files),
although many of its source files have names in excess of 8+3 limits.


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

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