From: Petr Vorel <pvorel@suse.cz>
To: Joerg Vehlow <lkml@jv-coder.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 0/3] openposix: Fix installation file layout
Date: Fri, 26 Aug 2022 10:49:44 +0200 [thread overview]
Message-ID: <YwiJKHTxbLnyDkob@pevik> (raw)
In-Reply-To: <20220727053307.3009235-1-lkml@jv-coder.de>
Hi all,
> Update to v1:
> - Replaced deprecated AC_PROG_CC_C99
> - Fixed whitespace
> - Fixed help message for configure script of ltp
> - Added a more verbose commit message to the last commit
I didn't remember the reason for these fixes. It was in v1 [1]:
as described in my RFC, here is a first implementation of a fixed
installation layout for open posix tests.
I implemented this using autoconf, to be able to specify the
installation location of the tests.
If build standalone, the open posix tests are still installed to
/opt/open_posix_testsuite/{conformance,functional,stress}, but when
installed as part of ltp, they are installed to
/opt/ltp/testcases/open_posix_testsuite/*
Kind regards,
Petr
[1] https://lore.kernel.org/ltp/20220627125321.1560677-1-lkml@jv-coder.de/
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2022-08-26 8:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 5:33 [LTP] [PATCH v2 0/3] openposix: Fix installation file layout Joerg Vehlow
2022-07-27 5:33 ` [LTP] [PATCH v2 1/3] openposix: Fix existence test for local flag-files Joerg Vehlow
2022-07-29 17:16 ` Petr Vorel
2022-08-23 10:03 ` Petr Vorel
2022-07-27 5:33 ` [LTP] [PATCH v2 2/3] openposix: Setup autoconf and fix installation layout Joerg Vehlow
2022-08-29 5:49 ` Petr Vorel
2022-08-30 11:00 ` Richard Palethorpe
2022-07-27 5:33 ` [LTP] [PATCH v2 3/3] configure: Integrate open posix testsuite configure Joerg Vehlow
2022-07-29 17:23 ` Petr Vorel
2022-08-01 7:16 ` Richard Palethorpe
2022-08-30 9:59 ` Li Wang
2022-08-03 4:45 ` Joerg Vehlow
2022-08-29 16:42 ` Petr Vorel
2022-08-30 11:01 ` Richard Palethorpe
2022-08-30 11:37 ` Petr Vorel
2022-08-26 8:49 ` Petr Vorel [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=YwiJKHTxbLnyDkob@pevik \
--to=pvorel@suse.cz \
--cc=lkml@jv-coder.de \
--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.