security/opie that
has now been removed. If security/cyrus-sasl2 has an optional
dependency on security/opie, it should be reflected in OPTIONS or have
it as a mandatory requirement.
I've added OPIE option for FreeBSD 14 and later, default to off.
https://cgit.freebsd.org/ports/commi
On 19/01/24 23:50, Hajimu UMEMOTO wrote:
Hi,
On Fri, 19 Jan 2024 03:52:53 +0900, j...@chen.org.nz wrote:
I've started seeing the following in my system logs on my recently built
cyrus-sasl
2.1.28_3:
unable to dlopen /usr/local/lib/sasl2/libotp.so.3: Shared object "libopie.so.8"
not
found, re
Hi,
On Fri, 19 Jan 2024 08:56:04 +0900, Jonathan Chen wrote:
> It looks like there was a implicit dependency on security/opie that
> has now been removed. If security/cyrus-sasl2 has an optional
> dependency on security/opie, it should be reflected in OPTIONS or have
> it as
Hi,
On Fri, 19 Jan 2024 03:52:53 +0900, j...@chen.org.nz wrote:
> I've started seeing the following in my system logs on my recently built
> cyrus-sasl
> 2.1.28_3:
> unable to dlopen /usr/local/lib/sasl2/libotp.so.3: Shared object
> "libopie.so.8" not
> found, required by "libotp.so.3"
>
> Doe
.so.8" not
found, required by "libotp.so.3"
Does cyrus-sasl2 required a dependency declaration on security/opie?
Did you run 'make delete-old-libs' after upgrading to stable/14 or main?
Have you tried to rebuild security/cyrus-sasl2 after removing
libopie.so.8? How did you
not found, required by "libotp.so.3"
>
> Does cyrus-sasl2 required a dependency declaration on security/opie?
Did you run 'make delete-old-libs' after upgrading to stable/14 or main?
Have you tried to rebuild security/cyrus-sasl2 after removing
libopie.so.8? How did you build
Hi,
I've started seeing the following in my system logs on my recently built
cyrus-sasl 2.1.28_3:
unable to dlopen /usr/local/lib/sasl2/libotp.so.3: Shared object
"libopie.so.8" not found, required by "libotp.so.3"
Does cyrus-sasl2 required a dependency declaration on security/opie?
Cheers
--
