===> The following configuration options are available for c-lightning-26.06.9_1:
COMPATIBILITY=on: Compatibility mode, good to disable to see if your software breaks
DEBUG=off: Extra debug checks in the build, good for testing
RUST=on: Install cln-grpc and clnrest plugins (Rust dependent)
====> Options available for the multi STORAGE: you have to choose at least one of them
POSTGRESQL=off: Use PostgreSQL for storage
SQLITE=on: Use SQLite for storage
====> Options available for the radio TESTING: you can only select none or one of them
ASAN=off: Compile with address-sanitizer
VALGRIND=off: Run tests with Valgrind
===> Use 'make config' to modify these settings
all: drop support for expired FreeBSD 14.0
Simplify expressions for FreeBSD 13.X
Reviewed by: many
Differential Revision: https://reviews.freebsd.org/D46601
net-p2p/c-lightning: hook dependencies for the clnrest plugin
The clnrest plugin is already installed but it depends on a bunch of
Python packages. Add an option to net-p2p/c-lightning to install and
depend on those packages.
Further, 3 of those packages were not in the FreeBSD ports. Add them:
* net-p2p/pyln-bolt7 Lightning Network BOLT7 implementation
* net-p2p/pyln-client Python client library for lightningd (net-p2p/c-lightning)
* net-p2p/pyln-proto Lightning Network protocol implementation
To enable the plugin, add
clnrest-port=
clnrest-protocol=
clnrest-host=
to /usr/local/etc/lightningd-bitcoin.conf, see
https://docs.corelightning.org/docs/rest
Differential Revision: https://reviews.freebsd.org/D43863
net-p2p/c-lightning: attempt to unbreak on arm64
Since arm64 uses two's complement (char)0xff is the same as -1.
Changing to use the latter should silence this compiler error:
ccan/ccan/base64/base64.c:34:10: error: result of comparison of constant 255
with expression of type 'int8_t' (aka 'signed char') is always false
[-Werror,-Wtautological-constant-out-of-range-compare]
if (ret == (char)0xff) {
~~~ ^ ~~~~~~~~~~
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
net-p2p: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* Alexander Botero-Lowry <alex@foxybanana.com>
* Alexey Dokuchaev <danfe@FreeBSD.org>
* Andrew Pantyukhin <infofarmer@FreeBSD.org>
* Attila Nagy <bra@fsn.hu>
* Chad J. Milios <milios@ccsys.com>
* Damian Gerow <dgerow@afflictions.org>
* Daniel Morante <daniel@morante.net>
* Dave Cottlehuber <dch@skunkwerks.at>
* Dereckson <dereckson@gmail.com>
* Devin Teske <dteske@FreeBSD.org>
* Dmitriy Limonov
(Only the first 15 lines of the commit message are shown above )
net-p2p/c-lightning: fix on head and wait bitcoind
* Fix compilation on FreeBSD 13-CURRENT
* Instruct rc(8) to start lightningd after bitcoind, if the latter is to be
started on this host.
* Wait for bitcoind RPC to be available before starting lightningd because:
- even though bitcoind would start and its rc script exit, it will not serve
RPC requests immediately
- lightningd would not start if bitcoind RPC is not available
net-p2p/c-lightning: fix bitcoin-cli exec setup
lightningd does execute bitcoin-cli internally during runtime.
Fix two problems with that:
* The bitcoin-cli executable is usually located in
/usr/local/bin/bitcoin-cli but service(8) would remove /usr/local/bin
from PATH before executing our rc script /usr/local/etc/rc.d/lightningd
and so the lightningd daemon would inherit a PATH that does not contain
bitcoin-cli. To fix this give the full path to bitcoin-cli to lightningd.
* bitcoin-cli(1) tries to create its datadir when it starts if it does not
exist. By default that is ${HOME}/.bitcoin. service(8) would set HOME=/
and if / is mounted read-only, then this creation would fail. Because we
don't want this directory created (it is not necessary and remains empty)
tell lightningd to execute
bitcoin-cli --datadir=/some/directory/that/already/exists.
Also, append ${lightningd_extra_args} to the lightingd arguments. This was
forgotten in the initial commit and setting lightningd_extra_args would have
had no effect.
Reported by: https://github.com/bitcoin-software
net-p2p/c-lightning: Add a new port - Lightning Network implementation in C
A lighweight, highly customizable and standard compliant
implementation of the Lightning Network protocol.
https://github.com/ElementsProject/lightning
