public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: shuah <shuah@kernel.org>
To: Yauheni Kaliuta <yauheni.kaliuta@redhat.com>
Cc: linux-kselftest@vger.kernel.org, bpf@vger.kernel.org,
	shuah <shuah@kernel.org>
Subject: Re: OUTPUT and TEST_CUSTOM_PROGS
Date: Tue, 26 May 2020 10:43:57 -0600	[thread overview]
Message-ID: <c049c93e-d962-ac15-e623-34df9af10a8b@kernel.org> (raw)
In-Reply-To: <xuny367osf2z.fsf@redhat.com>

On 5/25/20 12:28 AM, Yauheni Kaliuta wrote:
> Hi!
> 
> lib.mk expects TEST_GEN_PROGS, TEST_GEN_PROGS_EXTENDED and
> TEST_GEN_FILES to be in local directory and tries to handle out
> of tree build adding OUTPUT to it at the beginning.
> 
> commit be16a244c199 ("selftests: lib.mk: add TEST_CUSTOM_PROGS to
> allow custom test run/install") adds TEST_CUSTOM_PROGS but it
> handles it differently. Should it add OUTPUT as well?
> 

Individual tests apply OUTPUT to TEST_CUSTOM_PROGS. lib.mk rules
can't build TEST_CUSTOM_PROGS and it is left up to tests to
handle them as custom.

So no on adding OUTPUT to TEST_CUSTOM_PROGS in lib.mk.

thanks,
-- Shuah

      reply	other threads:[~2020-05-26 16:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25  6:28 OUTPUT and TEST_CUSTOM_PROGS Yauheni Kaliuta
2020-05-26 16:43 ` shuah [this message]

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=c049c93e-d962-ac15-e623-34df9af10a8b@kernel.org \
    --to=shuah@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=yauheni.kaliuta@redhat.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