From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eli Zaretskii 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 Message-id: References: <20040520025754.1761C4B104@berman.michael-chastain.com> X-SW-Source: 2004-05/msg00598.html > 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.