Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Aug 2021 19:39:55 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 257952] net-im/prosody: fix failure when using libevent
Message-ID:  <bug-257952-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257952

            Bug ID: 257952
           Summary: net-im/prosody: fix failure when using libevent
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: thomas@beingboiled.info
 Attachment #227330 maintainer-approval+
             Flags:
             Flags: merge-quarterly?

Created attachment 227330
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D227330&action=
=3Dedit
remove preproc defines that break libevent usage

net-im/prosody: fix failure when using libevent

* Restore libevent support by removing _POSIX_C_SOURCE defines.
* Remove redundant compiler requirements, defaults are fine.

QA:

  * portlint: OK (1 warning regarding the use of /var/db)
  * testport: OK (poudriere: 11.4-i386, 11.4-amd64, 12.2-i386,
                  12.2-amd64, 13.0-amd64, 13.0-arm64)

Prosody supports libevent for better performance on busy servers, but
setting "use_libevent =3D true" makes Prosody fail immediately on startup.

On FreeBSD Prosody needs a workaround for daemonizing with libevent
enabled. This workaround is rendered useless by the _POSIX_C_SOURCE
defines which disable __BSD_VISIBLE and the required rfork() flag.

Actually there's no need for the _POSIX_C_SOURCE defines on FreeBSD
and by simply removing them the libevent feature is working again.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-257952-7788>