zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: PATCH: Block device tests
Date: Wed, 30 May 2001 10:21:26 +0100	[thread overview]
Message-ID: <Tc0a88d0153d5a3480d@mailsweeper01.cambridgesiliconradio.com> (raw)
In-Reply-To: ""Bart Schaefer""'s message of "Tue, 29 May 2001 15:37:55 -0000." <1010529153756.ZM13431@candle.brasslantern.com>

"Bart Schaefer" wrote:
> On May 29, 11:34am, Peter Stephenson wrote:
> } Subject: Re: PATCH: Block device tests
> }
> } "Bart Schaefer" wrote:
> } > +  if ! grep '#define HAVE_FIFOS' $ZTST_testdir/../config.h; then
> } 
> } $ZTST_testdir is where we are running the tests.  Unfortunately this will
> } break if you are compiling separately from the source tree and then running
> } individual tests in the test directory
> 
> There are several other tests which rely on using a path relative to
> $ZTST_testdir:

The point was a little different: that config.h now has to be findable with
respect to wherever you're running the test, which therefore has to be the
Test subdirectory of the build.  Up to now, you could use the Test
subdirectory of the source tree, if different --- or anywhere else if you
adapted the path to the files in the latter directory.

On balance, it may be an advantage doing it this way: if we implement a way
of saying what's not implemented and hence shouldn't be checked on certain
systems, that's certainly going to have to go through one of the config.*
files.  In fact, we might get away with sourcing config.cache, and testing
the cv variables.  I won't be looking at that before the release.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK                          Tel: +44 (0)1223 392070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************


  reply	other threads:[~2001-05-30  9:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-22 15:14 Almost all tests pass under new cygwin Andrej Borsenkow
2001-05-22 15:24 ` Andrej Borsenkow
2001-05-22 15:31 ` Bart Schaefer
2001-05-22 15:44   ` Oliver Kiddle
2001-05-23 16:51     ` About zmodload test segfaults Bart Schaefer
2001-05-24 12:15       ` Andrej Borsenkow
2001-05-25 16:54         ` PATCH: Block device tests Bart Schaefer
2001-05-26  8:24           ` Andrej Borsenkow
2001-05-27 22:54             ` Bart Schaefer
2001-05-28  6:50               ` Andrej Borsenkow
2001-05-28 16:06                 ` Bart Schaefer
2001-05-28 17:25                   ` Bart Schaefer
2001-05-29 10:34                   ` Peter Stephenson
2001-05-29 10:51                     ` Andrej Borsenkow
2001-05-29 15:37                       ` Bart Schaefer
2001-05-30  9:21                         ` Peter Stephenson [this message]
2001-05-28  9:21       ` About zmodload test segfaults Sven Wischnowsky
2001-05-22 15:53   ` Almost all tests pass under new cygwin Andrej Borsenkow
2001-05-23 11:40 ` Peter Stephenson

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=Tc0a88d0153d5a3480d@mailsweeper01.cambridgesiliconradio.com \
    --to=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).