From: Nick Alcock <nick.alcock@oracle.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com, sam@gentoo.org
Subject: Re: [PATCH 01/14] No longer depend on libsystemd
Date: Mon, 28 Oct 2024 16:14:57 +0000 [thread overview]
Message-ID: <8734kgrypq.fsf@esperi.org.uk> (raw)
In-Reply-To: <ZxsAplgn-aSrZkF2@kvh-deb-bpf.us.oracle.com> (Kris Van Hees's message of "Thu, 24 Oct 2024 22:21:26 -0400")
On 25 Oct 2024, Kris Van Hees stated:
> On Thu, Oct 24, 2024 at 12:37:45PM +0100, Nick Alcock wrote:
>> --- a/GNUmakefile
>> +++ b/GNUmakefile
>> @@ -102,6 +102,7 @@ PKGCONFIGDIR = $(prefix)/share/pkgconfig
>> INSTPKGCONFIGDIR = $(DESTDIR)$(PKGCONFIGDIR)
>> TESTDIR = $(LIBDIR)/dtrace/testsuite
>> INSTTESTDIR = $(DESTDIR)$(TESTDIR)
>> +WITH_SYSTEMD = true
>
> Why not: WITH_SYSTEMD = y
>
> (since everything else seems to use = y)
Fixed (though there is nothing else in GNUmakefile that uses = y, or in
any Build script, so I'm not sure what you're referring to...)
... oh, you mean in the output of Makeconfig. Makes sense, agreed.
>> TARGETS =
>>
>> DTRACE ?= $(objdir)/dtrace
>> diff --git a/Makeconfig b/Makeconfig
>> index f3d47c086f4a..346078598624 100644
>> --- a/Makeconfig
>> +++ b/Makeconfig
>> @@ -218,7 +218,6 @@ $(eval $(call check-symbol-rule,ELF_GETSHDRSTRNDX,elf_getshdrstrndx,elf))
>> $(eval $(call check-symbol-rule,LIBCTF,ctf_open,ctf,t))
>> $(eval $(call check-symbol-rule,STRRSTR,strrstr,c))
>> $(eval $(call check-symbol-rule,PTHREAD_ATFORK,pthread_atfork,c))
>> -$(eval $(call check-symbol-rule,LIBSYSTEMD,sd_notify,systemd,t))
>> ifndef WANTS_LIBFUSE2
>> $(eval $(call check-symbol-rule,FUSE_LOG,fuse_set_log_func,fuse3))
>> $(eval $(call check-symbol-rule,LIBFUSE3,fuse_session_receive_buf,fuse3,t))
>> diff --git a/configure b/configure
>> index 4026a3eafcd3..42e496b97a7d 100755
>> --- a/configure
>> +++ b/configure
>> @@ -93,9 +93,13 @@ built locally, none of these should be needed):
>>
>> EOF
>> make help-overrides-header help-overrides-option
>> + cat >&2 <<'EOF'
>> +--with-systemd=[yes/no] Disable installation of the systemd unit files
>
> This makes no sense to me. How would '--with-systemd' mean that installation
> of the systemd unit files is to be disabled? Surely that is not the correct
> description? Maybe something like: "Enable or disable ..." or
> "Specify whether ..."?
... that's a really stupid description, isn't it! I kept on rephrasing
until I got something that was in <80 and ended up with gibberish.
Simply 'Install the systemd unit files (default: yes)' 45 chars, just
barely fits in 80.
>> + --with-systemd|--with-systemd=yes) write_make_var WITH_SYSTEMD "true";;
>
> "true" -> "y"
Ack.
I've also arranged that --with-systemd=y* turns it on, and n* turns it
off, entirely so yes and y turn it on, and n and no turn it off :)
--
NULL && (void)
next prev parent reply other threads:[~2024-10-28 16:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 11:37 [PATCH 00/14] gentoo, manpage, and assorted other small fixes Nick Alcock
2024-10-24 11:37 ` [PATCH 01/14] No longer depend on libsystemd Nick Alcock
2024-10-25 2:21 ` Kris Van Hees
2024-10-28 16:14 ` Nick Alcock [this message]
2024-10-24 11:37 ` [PATCH 02/14] pkgconfig: drop spaces in variable decls Nick Alcock
2024-10-25 2:22 ` Kris Van Hees
2024-10-28 16:16 ` Nick Alcock
2024-10-24 11:37 ` [PATCH 03/14] configure, build: make valgrind optional Nick Alcock
2024-10-25 2:30 ` Kris Van Hees
2024-10-28 16:38 ` Nick Alcock
2024-10-24 11:37 ` [PATCH 04/14] build: substitute LIBDIR in pkg-config files Nick Alcock
2024-10-25 2:32 ` Kris Van Hees
2024-10-24 11:37 ` [PATCH 05/14] probe: get the size of the hash-lookup key right Nick Alcock
2024-10-25 2:40 ` Kris Van Hees
2024-10-28 17:14 ` Nick Alcock
2024-10-24 11:37 ` [PATCH 06/14] configure: fix dreadful behaviour of MANDIR / --mandir Nick Alcock
2024-10-25 2:41 ` Kris Van Hees
2024-10-24 11:37 ` [PATCH 07/14] man: the synopsis is ended with .YS, not .SY Nick Alcock
2024-10-25 2:49 ` Kris Van Hees
2024-10-24 11:37 ` [PATCH 08/14] man: use \- for option dashes, not - Nick Alcock
2024-10-25 2:49 ` Kris Van Hees
2024-10-24 11:37 ` [PATCH 09/14] man: drop blank lines Nick Alcock
2024-10-25 2:50 ` Kris Van Hees
2024-10-24 11:37 ` [PATCH 10/14] man: fix blank line in environment variables list Nick Alcock
2024-10-25 2:50 ` Kris Van Hees
2024-10-24 11:37 ` [PATCH 11/14] dtprobed: fix parser child timeout Nick Alcock
2024-10-25 2:54 ` Kris Van Hees
2024-10-24 11:37 ` [PATCH 12/14] man: add manpage for dtprobed(8) Nick Alcock
2024-10-25 2:53 ` Kris Van Hees
2024-10-28 17:18 ` Nick Alcock
2024-10-24 11:37 ` [PATCH 13/14] man: drop double-\fB at the start of every option line Nick Alcock
2024-10-25 2:55 ` Kris Van Hees
2024-10-24 11:37 ` [PATCH 14/14] man: \fP-ize Nick Alcock
2024-10-25 2:55 ` Kris Van Hees
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=8734kgrypq.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=kris.van.hees@oracle.com \
--cc=sam@gentoo.org \
/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