All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] configure.ac: Fix --with* options
Date: Thu, 14 Nov 2019 16:36:47 +0800	[thread overview]
Message-ID: <CAEemH2dPwqX1FtNvF7=hxbAfVMz7i_u+TpUBaU1mqKhY-G0Vig@mail.gmail.com> (raw)
In-Reply-To: <1c4d8fb5-58e4-5483-26c7-7ab38b5fbd9c@jv-coder.de>

On Thu, Nov 14, 2019 at 4:09 PM Joerg Vehlow <lkml@jv-coder.de> wrote:

> Hi,
> >
> >     Defining AC_ARG_WITH within an if to express dependencies does not
> >     work.
> >     ./configure --with-realtime-testsuite set
> with_realtime_testsuite=yes,
> >     even if with_bash=no or with_python=no. The check is removed
> >     completely.
> >
> >
> > Or, maybe we can make use of AS_IF here? and I noticed there are many
> > places that use "if test ..." in the configure.ac
> > <http://configure.ac> file. That looks tangly...
> I left a TODO in there so it can be fixed later, maybe together with
> other errors. I think this does not block merging this patch first?
>

Well, I just saw adding new #TODO here and hoping to solve this together, a
simple way I was thinking is:

+AS_IF([test "x$with_bash" != xyes || test "x$with_python" != xyes],
+  [with_realtime_testsuite=no]
+)

Of course, It's fine to fix that in a separate patch!


> The python requirement for realtime-testsuite is outdated/wrong anyway,
> if I remember correctly. A colleague of mine recently
> investigated the python requirement and we came to the conclusion, that
> it is not needed for running the test.
> I think it was used only for manual test result evaluation.


> So there seems to be more work regarding dependencies between configure
> options.
>

Yes, thanks for investigating this. Looking forward to more patches :).

For this one:
    Reviewed-by: Li Wang <liwang@redhat.com>

-- 
Regards,
Li Wang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20191114/00f1db0f/attachment.htm>

  reply	other threads:[~2019-11-14  8:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13 10:41 [LTP] [PATCH] configure.ac: Fix --with* options Joerg Vehlow
2019-11-13 16:02 ` Petr Vorel
2019-11-14  3:24 ` Li Wang
2019-11-14  6:31   ` Joerg Vehlow
2019-11-14  7:59     ` Li Wang
2019-11-14  8:09       ` Joerg Vehlow
2019-11-14  8:36         ` Li Wang [this message]
2019-11-18  6:16           ` Petr Vorel
2019-11-18  6:38             ` Li Wang
2019-11-18  6:40             ` Joerg Vehlow
2019-11-18  8:59               ` Petr Vorel
2019-11-18 20:41     ` Petr Vorel

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='CAEemH2dPwqX1FtNvF7=hxbAfVMz7i_u+TpUBaU1mqKhY-G0Vig@mail.gmail.com' \
    --to=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.