Re: [Dnsmasq-discuss] Failed to compile dnsmasq latest git version with `-DHAVE_LUASCRIPT' on Manjaro.
On Sat, Nov 09, 2019 at 02:27:49PM +0800, Hongyi Zhao wrote: > Hi, > > See the following: > > $ uname -a > Linux Manjaro 5.3.7-2-MANJARO #1 SMP PREEMPT Tue Oct 22 18:56:05 UTC > 2019 x86_64 GNU/Linux > > $ yay -S lua52 > > $ make COPTS="-DHAVE_DBUS -DHAVE_IDN -DHAVE_LUASCRIPT -DHAVE_CONNTRACK > -DHAVE_DNSSEC" -j24 > Package lua5.2 was not found in the pkg-config search path. > Perhaps you should add the directory containing `lua5.2.pc' > to the PKG_CONFIG_PATH environment variable > Package 'lua5.2', required by 'virtual:world', not found > Package lua5.2 was not found in the pkg-config search path. > Perhaps you should add the directory containing `lua5.2.pc' > to the PKG_CONFIG_PATH environment variable > Package 'lua5.2', required by 'virtual:world', not found > make[1]: Entering directory ... > make[1]: *** [/home/data/software/dnsmasq.git/Makefile:164: dnsmasq] Error 1 > make[1]: Leaving directory '/home/data/software/dnsmasq.git/src' > make: *** [Makefile:86: all] Error 2 > > > How to solve this issue? Install the Manjaro equivalent of the Debian package `liblua5.2-dev` AFAIK has Manjaro the yellowdog update manager so start with yum search lua to find the actual package name, then install that package. Yes, it is appricated to report milage. Groeten Geert Stappers -- Leven en laten leven ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] Failed to compile dnsmasq latest git version with `-DHAVE_LUASCRIPT' on Manjaro.
Hi, See the following: $ uname -a Linux Manjaro 5.3.7-2-MANJARO #1 SMP PREEMPT Tue Oct 22 18:56:05 UTC 2019 x86_64 GNU/Linux $ yay -S lua52 $ make COPTS="-DHAVE_DBUS -DHAVE_IDN -DHAVE_LUASCRIPT -DHAVE_CONNTRACK -DHAVE_DNSSEC" -j24 Package lua5.2 was not found in the pkg-config search path. Perhaps you should add the directory containing `lua5.2.pc' to the PKG_CONFIG_PATH environment variable Package 'lua5.2', required by 'virtual:world', not found Package lua5.2 was not found in the pkg-config search path. Perhaps you should add the directory containing `lua5.2.pc' to the PKG_CONFIG_PATH environment variable Package 'lua5.2', required by 'virtual:world', not found make[1]: Entering directory '/home/data/software/anti-gfw/dns/dnsmasq/dnsmasq.git/src' cc -o dnsmasq cache.o rfc1035.o util.o option.o forward.o network.o dnsmasq.o dhcp.o lease.o rfc2131.o netlink.o dbus.o bpf.o helper.o tftp.o log.o conntrack.o dhcp6.o rfc3315.o dhcp-common.o outpacket.o radv.o slaac.o auth.o ipset.o domain.o dnssec.o blockdata.o tables.o loop.o inotify.o poll.o rrfilter.o edns0.o arp.o crypto.o dump.o ubus.o metrics.o -ldbus-1-lidn -lnetfilter_conntrack -lnfnetlink -lnettle -lhogweed -lgmp /usr/bin/ld: helper.o: in function `grab_extradata_lua.part.0': helper.c:(.text+0x3e): undefined reference to `lua_pushstring' /usr/bin/ld: helper.c:(.text+0x52): undefined reference to `lua_setfield' /usr/bin/ld: helper.o: in function `create_helper': helper.c:(.text+0x308): undefined reference to `luaL_newstate' /usr/bin/ld: helper.c:(.text+0x317): undefined reference to `luaL_openlibs' /usr/bin/ld: helper.c:(.text+0x333): undefined reference to `luaL_loadfilex' /usr/bin/ld: helper.c:(.text+0x352): undefined reference to `lua_pcallk' /usr/bin/ld: helper.c:(.text+0x36d): undefined reference to `lua_tolstring' /usr/bin/ld: helper.c:(.text+0x3b1): undefined reference to `lua_settop' /usr/bin/ld: helper.c:(.text+0x3c4): undefined reference to `lua_getglobal' /usr/bin/ld: helper.c:(.text+0x3d5): undefined reference to `lua_type' /usr/bin/ld: helper.c:(.text+0x3ef): undefined reference to `lua_settop' /usr/bin/ld: helper.c:(.text+0x6e3): undefined reference to `lua_getglobal' /usr/bin/ld: helper.c:(.text+0x6f4): undefined reference to `lua_type' /usr/bin/ld: helper.c:(.text+0x70e): undefined reference to `lua_settop' /usr/bin/ld: helper.c:(.text+0xbb0): undefined reference to `lua_getglobal' /usr/bin/ld: helper.c:(.text+0xbc1): undefined reference to `lua_pushstring' /usr/bin/ld: helper.c:(.text+0xbd1): undefined reference to `lua_createtable' /usr/bin/ld: helper.c:(.text+0xc0a): undefined reference to `lua_pushnumber' /usr/bin/ld: helper.c:(.text+0xc22): undefined reference to `lua_setfield' /usr/bin/ld: helper.c:(.text+0xc3b): undefined reference to `lua_pushstring' /usr/bin/ld: helper.c:(.text+0xc53): undefined reference to `lua_setfield' /usr/bin/ld: helper.c:(.text+0xc6c): undefined reference to `lua_pushstring' /usr/bin/ld: helper.c:(.text+0xc84): undefined reference to `lua_setfield' /usr/bin/ld: helper.c:(.text+0xe7c): undefined reference to `lua_pushstring' /usr/bin/ld: helper.c:(.text+0xe94): undefined reference to `lua_setfield' /usr/bin/ld: helper.c:(.text+0xebd): undefined reference to `lua_pushstring' /usr/bin/ld: helper.c:(.text+0xed5): undefined reference to `lua_setfield' /usr/bin/ld: helper.c:(.text+0xeef): undefined reference to `lua_pushstring' /usr/bin/ld: helper.c:(.text+0xf07): undefined reference to `lua_setfield' /usr/bin/ld: helper.c:(.text+0xf1f): undefined reference to `lua_callk' /usr/bin/ld: helper.c:(.text+0xf92): undefined reference to `lua_getglobal' /usr/bin/ld: helper.c:(.text+0xfa3): undefined reference to `lua_type' /usr/bin/ld: helper.c:(.text+0xfbd): undefined reference to `lua_pushstring' /usr/bin/ld: helper.c:(.text+0xfcd): undefined reference to `lua_createtable' /usr/bin/ld: helper.c:(.text+0xfe7): undefined reference to `lua_pushstring' /usr/bin/ld: helper.c:(.text+0xfff): undefined reference to `lua_setfield' /usr/bin/ld: helper.c:(.text+0x1010): undefined reference to `lua_pushstring' /usr/bin/ld: helper.c:(.text+0x1028): undefined reference to `lua_setfield' /usr/bin/ld: helper.c:(.text+0x104a): undefined reference to `lua_pushstring' /usr/bin/ld: helper.c:(.text+0x127d): undefined reference to `lua_getglobal' /usr/bin/ld: helper.c:(.text+0x128e): undefined reference to `lua_type' /usr/bin/ld: helper.c:(.text+0x12ac): undefined reference to `lua_callk' /usr/bin/ld: helper.c:(.text+0x13d0): undefined reference to `lua_pushstring' /usr/bin/ld: helper.c:(.text+0x13e0): undefined reference to `lua_createtable' /usr/bin/ld: helper.c:(.text+0x13fa): undefined reference to `lua_pushstring' /usr/bin/ld: helper.c:(.text+0x1412): undefined reference to `lua_setfield' /usr/bin/ld: helper.c:(.text+0x142c): undefined reference to `lua_pushstring' /usr/bin/ld: helper.c:(.text+0x15bd): undefined reference to `lua_pushstring' /usr/bin/ld: helper.c:(.text+0x15d5): undefined reference to
Re: [Dnsmasq-discuss] dhcp-name-match ?
On 07/11/2019 03:52, James Feeney wrote: > Hey Simon > > On 10/30/19 3:32 PM, Simon Kelley wrote: >> The question is, [if] the client-provided name and the dhcp-host name >> differ, which one should be matched? Since this is broken, there's no >> pre-existing behaviour to consider. Any configurations relying on one or >> the other are currently broken [by] definition. >> >> I've decided that if both exist, then the name from dhcp-host should be >> matched. It seems that if the config explicitly nails a MAC address or >> client-id to a name, that's the one that should be used. > > Hmm - if you would, let me make sure I understand, then, how this will work. > > I would have thought to make "dhcp-name-match" match against the client > provided name, since there is nothing that will assure that the client > provided name is anything different from what the client wants to provide. > The client is not, necessarily, going to adopt the hostname provided by the > dhcp server. > > So then, does the "new" behavior mean that, effectively, "dhcp-name-match" is > really a kind of "MAC-address-match", or "DUID-match", by way of the > dhcp-host specified hostname? > > I should, then, simply write "dhcp-name-match=", where the > name is just the name associated with the dhcp-host MAC address, or with the > DUID? > > Also, then, if there is *no* dhcp-host hostname specified, will > "dhcp-name-match" still match the client provided name? Or, will that no > longer work, at all? > > A difficulty I see here, is that, if the client DUID or MAC address is *not* > known, and only the persistent client provided name is offered by the client, > then there will be no way to actually tag the client, unless every client > DUID or MAC address is first discovered and manually configured with a > hostname. > > And then, why not simply have a "dhcp-DUID-match" or a "dhcp-MAC-addr-match", > instead? > > James > If there's no name configured in the dnsmasq configuration, then the client-provided name will be matched. However if there is a name configured in the dnsmasq configuration, selected by MAC address or client-id, then that will be used in preference. To an extent, what the client chooses to use as its name is secondary: dnsmasq determines the client's name so that it can be inserted into the DNS. If the configuration specifies that name, then that's what dnsmasq puts in the DNS, and it's what dnsmasq uses with dhcp-name-match. Simon ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
