[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AT_TESTED and (non)fatal errors
From: |
Ralf Wildenhues |
Subject: |
Re: AT_TESTED and (non)fatal errors |
Date: |
Thu, 17 Mar 2005 11:11:04 +0100 |
User-agent: |
Mutt/1.4.1i |
Hi Noah,
* Noah Misch wrote on Wed, Mar 16, 2005 at 03:40:27AM CET:
> On Fri, Mar 11, 2005 at 03:30:39PM +0100, Ralf Wildenhues wrote:
> >
> > Right now, the testsuite fails when it there is at least one program
> > missing which is necessary for one test, even if all I want is to run
> > some other test which does not need the program. Ideally, I would like
> > something like SKIP if the program is not available, and AT_TESTED to
> > allow to work more test-local.
>
> That sounds appropriate. Do you have an implementation in mind?
No, have not thought about that yet.
> If not, I'll make a note to work something up.
Great.
*snip*
> > What is the best way around this, short of creating stub commands in
> > $PATH somewhere (which I don't think I can force users to do)?
> > Or should we just ditch AT_TESTED and write our own little macro?
>
> There is no good way to continue using AT_TESTED with a scheme like this;
> arguments to AT_TESTED are single-quoted in `testsuite', so variable arguments
> do not work. I will fix that, but I suggest avoiding AT_TESTED for now.
That's what I was afraid of.
Thanks for your response. I will work up a patch (to libtool-patches
only) to this extent.
Regards,
Ralf