All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Vehlow <lkml@jv-coder.de>
To: rpalethorpe@suse.de
Cc: ltp@lists.linux.it, Joerg Vehlow <joerg.vehlow@aox.de>
Subject: Re: [LTP] [PATCH 2/3] openposix: Setup autoconf and fix installation layout
Date: Wed, 27 Jul 2022 07:26:52 +0200	[thread overview]
Message-ID: <9fb52291-7d86-25cb-d4de-52fb4db78eb2@jv-coder.de> (raw)
In-Reply-To: <87czekrseu.fsf@suse.de>

Hi Richard,

Am 7/5/2022 um 7:57 AM schrieb Richard Palethorpe:
> Hello Joerg,
> 
> Joerg Vehlow <lkml@jv-coder.de> writes:
> 
>>  
>> -distclean: distclean-makefiles
>> +.PHONY: distclean
>> +distclean: clean distclean-makefiles
>> +	@rm -f $(AUTOGENERATED_FILES)
> 
> Shouldn't this also include the configure script itself? Running
> distclean on the LTP root removes the top level configure script.
No it does not. If autotools generates all the makefiles, it would do
that, but with the hand-crafted makefiles of ltp, it does not.
The same is true for the realtime testsuite. It only deletes the
configure script in maintainer-clean. To keep it consistent, I went for
the same cleanup, as ltp itself an the realtime testsuite use.

$ make distclean &>/dev/null && ls configure
configure


>> diff --git a/testcases/open_posix_testsuite/QUICK-START b/testcases/open_posix_testsuite/QUICK-START
>> index 6f5d881b4..649d7a3d7 100644
>> --- a/testcases/open_posix_testsuite/QUICK-START
>> +++ b/testcases/open_posix_testsuite/QUICK-START
>> @@ -10,8 +10,6 @@ No worries! Here's a quick doc to help you around POSIX** Test Suite.
>>  Setting up your machine
>>  ========================
>>  
>> -* There is nothing to install, the suite is intended to be run directly.
>> -
>>  * See the "BUILD" file for info on how to set up the Makefile and your machine,
>>    depending on what specific area you are concentrating on.
>>  (Signals, Semaphores, Threads, Timers or Message Queues).
>> @@ -20,8 +18,8 @@ Setting up your machine
>>  Running the tests
>>  ===================
>>  
>> -* Easiest way to run all the tests is to do a "make all" in the top-level
>> -  directory.
>> +* Easiest way to run all the tests is to do a "./configure && make all"
> 
> Trailing whitespace at the end of this line
Fixed in v2

>> diff --git a/testcases/open_posix_testsuite/configure.ac b/testcases/open_posix_testsuite/configure.ac
>> new file mode 100644
>> index 000000000..ae0399d07
>> --- /dev/null
>> +++ b/testcases/open_posix_testsuite/configure.ac
>> @@ -0,0 +1,18 @@
>> +AC_PREREQ(2.61)
>> +AC_INIT([open_posix_testsuite], [LTP_VERSION], [ltp@lists.linux.it])
>> +AC_CONFIG_FILES([ \
>> +    include/mk/config.mk \
>> +])
>> +
>> +AC_PROG_CC_C99
> 
> This causes a deprecation warning for me
As already explained, I will replace it with AC_PROG_CC in v2

Joerg


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  parent reply	other threads:[~2022-07-27  5:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 12:53 [LTP] [0/3] openposix: Fix installation file layout Joerg Vehlow
2022-06-27 12:53 ` [LTP] [PATCH 1/3] openposix: Fix existence test for local flag-files Joerg Vehlow
2022-06-27 12:53 ` [LTP] [PATCH 2/3] openposix: Setup autoconf and fix installation layout Joerg Vehlow
2022-07-05  5:57   ` Richard Palethorpe
2022-07-05  6:28     ` Richard Palethorpe
2022-07-05  6:37       ` Joerg Vehlow
2022-07-05  7:37         ` Richard Palethorpe
2022-07-27  5:42           ` Joerg Vehlow
2022-07-05  6:43     ` Joerg Vehlow
2022-07-27  5:26     ` Joerg Vehlow [this message]
2022-06-27 12:53 ` [LTP] [PATCH 3/3] configure: Integrate open posix testsuite configure Joerg Vehlow
2022-07-05  6:22   ` Richard Palethorpe

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=9fb52291-7d86-25cb-d4de-52fb4db78eb2@jv-coder.de \
    --to=lkml@jv-coder.de \
    --cc=joerg.vehlow@aox.de \
    --cc=ltp@lists.linux.it \
    --cc=rpalethorpe@suse.de \
    /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.