From: Daniel Wagner <wagi@monom.org>
To: matthias.gerstner@suse.de
Cc: connman@lists.linux.dev
Subject: Re: [PATCH] dnsproxy: add standalone test version of dnsproxy and a test script for it
Date: Fri, 4 Mar 2022 09:50:32 +0100 [thread overview]
Message-ID: <20220304085032.ye5te4lxomj7yup5@beryllium.lan> (raw)
In-Reply-To: <20220228131921.5573-2-matthias.gerstner@suse.de>
Hi Matthias,
On Mon, Feb 28, 2022 at 02:19:21PM +0100, matthias.gerstner@suse.de wrote:
> if TEST
> testdir = $(pkglibdir)/test
> test_SCRIPTS = $(test_scripts)
> +
> +tools_dnsproxy_standalone_CFLAGS = $(src_connmand_CFLAGS) -I$(srcdir)/src
> +tools_dnsproxy_standalone_SOURCES = tools/dnsproxy-standalone.c $(src_connmand_SOURCES)
> +# for EXTRA_PROGRAMS the BUILT_SOURCES aren't automatically added as
> +# dependency, so let's do it explicitly
> +tools/dnsproxy-standalone.c: $(BUILT_SOURCES)
> +tools_dnsproxy_standalone_LDADD = $(src_connmand_LDADD)
> +# pass -zmuldefs to let the linker tolerate the duplicate definition of
> +# main(), the first definition from dnsproxy-standalone should be used
> +tools_dnsproxy_standalone_LDFLAGS = $(src_connmand_LDFLAGS) -Wl,-zmuldefs
> +
> +noinst_PROGRAMS += tools/dnsproxy-standalone
> +
I wrapped this section into an addition 'if INTERNAL_DNS_BACKEND'
because it would fail to build for SYSTEMD_RESOLVED_DNS_BACKEND
> + // we need to trick a bit to make the server entry enter "enabled"
> + // state in dnsproxy. Appending and removing an arbitrary entry causes
> + // "enable_fallback()" to be called which does what we want. Doesn't
> + // make much sense but it is good enough for the standalone server at
> + // the moment.
Changed this to /* ... */
Patch applied.
Thanks
Daniel
next prev parent reply other threads:[~2022-03-04 8:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 11:31 dnsproxy: some initial refactoring and integration test matthias.gerstner
2022-02-17 11:31 ` [PATCH 1/7] dnsproxy: remove unused domain parameter from `remove_server()` matthias.gerstner
2022-02-17 11:31 ` [PATCH 2/7] dnsproxy: remove unnecessarily shadowed variable matthias.gerstner
2022-02-17 11:31 ` [PATCH 3/7] dnsproxy: protocol_offset: remove error return case and return size_t matthias.gerstner
2022-02-21 8:49 ` Daniel Wagner
2022-02-17 11:31 ` [PATCH 4/7] .gitignore: also ignore backup configure script matthias.gerstner
2022-02-21 8:49 ` Daniel Wagner
2022-02-17 11:31 ` [PATCH 5/7] dnsproxy: support programmatic configuration of the default listen port matthias.gerstner
2022-02-17 11:31 ` [PATCH 6/7] dnsproxy-test: support command line specification of dnsproxy port matthias.gerstner
2022-02-17 11:31 ` [PATCH 7/7] dnsproxy: add standalone test version of dnsproxy and a test script for it matthias.gerstner
2022-02-21 8:48 ` Daniel Wagner
2022-02-28 13:19 ` dnsproxy: some initial refactoring and integration test matthias.gerstner
2022-02-28 13:19 ` [PATCH] dnsproxy: add standalone test version of dnsproxy and a test script for it matthias.gerstner
2022-03-04 8:50 ` Daniel Wagner [this message]
2022-02-21 8:51 ` dnsproxy: some initial refactoring and integration test Daniel Wagner
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=20220304085032.ye5te4lxomj7yup5@beryllium.lan \
--to=wagi@monom.org \
--cc=connman@lists.linux.dev \
--cc=matthias.gerstner@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).