coredhcp build error

[wuxiao-ling197]

when I go build coredhcp,there is always an error that "could not setup lease storage: failed to open lease database leases.txt: table creation failed: Binary was compiled with 'CGO_ENABLED=0', go-sqlite3 requires cgo to work. This is a stub",how could deal with it?

[Natolumin]

I can't reproduce this build error. The message you quote looks like a runtime error to me? specifically it would come from

coredhcp/plugins/range/plugin.go

Line 129 in 12a2f40

return nil, fmt.Errorf("could not setup lease storage: %w", err)

You have 2 options here:

• Enable cgo (build with CGO_ENABLED=1) to use sqlite if you're using the range plugin
• Change your configuration to not load the range plugin if not using it

I'm keeping this open, as I think we should make it an actual build failure if the range plugin (which requires cgo) is built with cgo disabled

[wuxiao-ling197]

Thank your answer! I resolved this problem following the second way. and I chose the DHCPv4 but its can`t run the client with " FATAL main: short hardware addrss: less than 4 bytes " , is the client progrom not support v4 server ?

[Natolumin]

The client in this repository is only a debugging tool and not meant to be used as a general client; It indeed only supports DHCPv6.
You could try the DHCPv4 client maintained by upstream: https://github.com/insomniacslk/dhcp/tree/master/dhcpv4/nclient4

[wuxiao-ling197]

ok,got it!thank you~  

…

------------------ 原始邮件 ------------------ 发件人: "coredhcp/coredhcp" ***@***.***>; 发送时间: 2024年3月13日(星期三) 下午5:43 ***@***.***>; ***@***.******@***.***>; 主题: Re: [coredhcp/coredhcp] coredhcp build error (Issue #176) The client in this repository is only a debugging tool and not meant to be used as a general client; It indeed only supports DHCPv6. You could try the DHCPv4 client maintained by upstream: https://github.com/insomniacslk/dhcp/tree/master/dhcpv4/nclient4 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>