... | ... | @@ -2,6 +2,10 @@ |
|
|
|
|
|
You can see all Kea issues with the `bug` label at [this link](https://gitlab.isc.org/isc-projects/kea/issues?label_name[]=bug). The following is a list of some of the more significant known issues in current and previous versions of Kea.
|
|
|
|
|
|
## Unicode Environments
|
|
|
|
|
|
* On some exotic systems, unicode may be enabled by default. When compiling from sources, it is known to cause linking errors such as `undefined reference to `log4cplus::Logger::getInstance(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)'`. This is caused by Kea not supporting unicode strings / wide-character strings. Configuring the Kea sources with `CXXFLAGS='-UUNICODE' ./configure` is known to solve the issue. If you compile other dependencies from sources e.g. googletest, they may also need tweaking e.g. `CXXFLAGS='-UUNICODE' cmake .` respectively.
|
|
|
|
|
|
## New Systems
|
|
|
|
|
|
* On systems that have python version 3.12 or newer installed, e.g. Fedora 39, if Kea is built from tarball, if the `autoreconf -i` step is omitted, and if kea-shell is enabled through `--enable-shell`, installation will fail for `kea-shell` and the user will be greeted with error message `ModuleNotFoundError: No module named 'imp'`. This is because of the removal in python 3.12 of the previously deprecated `imp` python module. `kea-shell` does not directly or indirectly use this module. However the `py-compile` which is provided with the tarball, and is required to install python modules does. A new version of `py-compile` that does not use the `imp` module needs to be pulled. That can be done by running `autoreconf -i` before `./configure` as the Kea ARM recommends. This needs to be done on the same machine that requires `kea-shell` to be installed, or at least on another machine that has python 3.12 or newer.
|
... | ... | |