From Newsgroup: muc.lists.freebsd.ports

Hi,
building maildrop 4.0.4 with the inotify option (to support IDLE) fails:
ld: error: undefined symbol: inotify_init1

referenced by maildirwatch.C
maildirwatch.o:(maildir::watch::fd()) in archive ./.libs/libmdcommon.a
referenced by maildirwatch.C
maildirwatch.o:(maildir::watch::poll_inotify()) in archive ./.libs/libmdcommon.a
referenced by maildirwatch.C
maildirwatch.o:(maildir::watch::unlock(int)) in archive ./.libs/libmdcommon.a
referenced 7 more times

ld: error: undefined symbol: inotify_add_watch

referenced by maildirwatch.C
maildirwatch.o:(maildir::watch::unlock(int)) in archive ./.libs/libmdcommon.a
referenced by maildirwatch.C
maildirwatch.o:(maildir::watch::start(maildirwatch_contents_filehandles&)) in archive ./.libs/libmdcommon.a
referenced by maildirwatch.C
maildirwatch.o:(maildir::watch::start(maildirwatch_contents_filehandles&)) in archive ./.libs/libmdcommon.a
referenced 2 more times

ld: error: undefined symbol: inotify_rm_watch

referenced by maildirwatch.C
maildirwatch.o:(maildir::watch::unlock(int)) in archive ./.libs/libmdcommon.a
referenced by maildirwatch.C
maildirwatch.o:(maildir::watch::end_unwatch(maildirwatch_contents_filehandles&)) in archive ./.libs/libmdcommon.a

c++: error: linker command failed with exit code 1 (use -v to see invocation) *** [maildrop] Error code 1
make[2]: stopped in /usr/ports/mail/maildrop/work/maildrop-4.0.4/libs/maildrop 1 error
Is this a mialdrop issue or a libinotify issue?
with best regards,
Ewout Boks
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On 9/18/26 12:05, E.J Boks wrote:

Hi,

building maildrop 4.0.4 with the inotify option (to support IDLE) fails:

ld: error: undefined symbol: inotify_init1

referenced by maildirwatch.C
maildirwatch.o:(maildir::watch::fd()) in archive ./.libs/libmdcommon.a
referenced by maildirwatch.C
maildirwatch.o:(maildir::watch::poll_inotify()) in archive ./.libs/libmdcommon.a
referenced by maildirwatch.C
maildirwatch.o:(maildir::watch::unlock(int)) in archive ./.libs/libmdcommon.a
referenced 7 more times

ld: error: undefined symbol: inotify_add_watch

referenced by maildirwatch.C
maildirwatch.o:(maildir::watch::unlock(int)) in archive ./.libs/libmdcommon.a
referenced by maildirwatch.C
maildirwatch.o:(maildir::watch::start(maildirwatch_contents_filehandles&)) in archive ./.libs/libmdcommon.a
referenced by maildirwatch.C
maildirwatch.o:(maildir::watch::start(maildirwatch_contents_filehandles&)) in archive ./.libs/libmdcommon.a
referenced 2 more times

ld: error: undefined symbol: inotify_rm_watch

referenced by maildirwatch.C
maildirwatch.o:(maildir::watch::unlock(int)) in archive ./.libs/libmdcommon.a
referenced by maildirwatch.C
maildirwatch.o:(maildir::watch::end_unwatch(maildirwatch_contents_filehandles&)) in archive ./.libs/libmdcommon.a

c++: error: linker command failed with exit code 1 (use -v to see invocation) *** [maildrop] Error code 1

make[2]: stopped in /usr/ports/mail/maildrop/work/maildrop-4.0.4/libs/maildrop
1 error

Is this a mialdrop issue or a libinotify issue?

I need to investigate, which I will do as soon as I can.

In the while there is some information you can provide which could turn
up to be useful:

- FreeBSD version
- If using latest or weekly branch?
- If building using poudriere on on live machine?
--
Guido Falsi <madpilot@FreeBSD.org>


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

Sep 18, 2026 21:47:44 Guido Falsi <madpilot@FreeBSD.org>:

On 9/18/26 18:48, Guido Falsi wrote:

On 9/18/26 12:05, E.J Boks wrote:

Hi,

building maildrop 4.0.4 with the inotify option (to support IDLE) fails: >>>
ld: error: undefined symbol: inotify_init1

rCa

ld: error: undefined symbol: inotify_add_watch

rCa

ld: error: undefined symbol: inotify_rm_watch

rCa

c++: error: linker command failed with exit code 1 (use -v to see invocation)
*** [maildrop] Error code 1

make[2]: stopped in /usr/ports/mail/maildrop/work/maildrop-4.0.4/libs/ maildrop
1 error


Is this a mialdrop issue or a libinotify issue?

I need to investigate, which I will do as soon as I can.
In the while there is some information you can provide which could turn up to be useful:
- FreeBSD version
- If using latest or weekly branch?
- If building using poudriere on on live machine?

I launched a quick poudriere test, enabling INOTIFY, and the port compiles fine.

The test makes me suspect the way we link to libinotify is sub-optimal, and I need to take a better look, but unluckily I'm unable to reprouce right now.

Can you give some more information, and maybe provide a log of the failed build?

14.4 has inotify from the ports (but stub includes in the base).
All other branches/releases have it in base libc.
Hope it helps!
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

Hello Guido and other,
I reported the issue using FreeBSD 14.3. I gather from your answer that my port version (in 14.3) was not sufficient anymore and resulted in linking errors.
Since then, I upgrade to 15.1, and the errors disappeared.
The issue is therefore resolved.
Thanks everyone!
Ewout Boks

Op 20 sep 2026, om 11:38 heeft Guido Falsi <madpilot@FreeBSD.org> het volgende geschreven:

On 9/20/26 02:09, Bugs Beastie wrote:

Sep 18, 2026 21:47:44 Guido Falsi <madpilot@FreeBSD.org>:

On 9/18/26 18:48, Guido Falsi wrote:

On 9/18/26 12:05, E.J Boks wrote:

Hi,

building maildrop 4.0.4 with the inotify option (to support IDLE) fails: >>>>>
ld: error: undefined symbol: inotify_init1

rCa

ld: error: undefined symbol: inotify_add_watch

rCa

ld: error: undefined symbol: inotify_rm_watch

rCa

c++: error: linker command failed with exit code 1 (use -v to see invocation)
*** [maildrop] Error code 1

make[2]: stopped in /usr/ports/mail/maildrop/work/maildrop-4.0.4/libs/ maildrop
1 error


Is this a mialdrop issue or a libinotify issue?

I need to investigate, which I will do as soon as I can.
In the while there is some information you can provide which could turn up to be useful:
- FreeBSD version
- If using latest or weekly branch?
- If building using poudriere on on live machine?

I launched a quick poudriere test, enabling INOTIFY, and the port compiles fine.

The test makes me suspect the way we link to libinotify is sub-optimal, and I need to take a better look, but unluckily I'm unable to reprouce right now.

Can you give some more information, and maybe provide a log of the failed build?

14.4 has inotify from the ports (but stub includes in the base).
All other branches/releases have it in base libc.
Hope it helps!

14.4 is really near EOL and the port used to compile fine there, I don't think anything has changed there.

Unless the reporter gives some more information there is little I can do at this point. Anyway I'll run a poudriere test on 14.4, just in case.

--
Guido Falsi <madpilot@FreeBSD.org>

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On 9/20/26 16:10, Ewout1 (Excite/BlueTie) wrote:

Hello Guido and other,

I reported the issue using FreeBSD 14.3. I gather from your answer that my port version (in 14.3) was not sufficient anymore and resulted in linking errors.

Since then, I upgrade to 15.1, and the errors disappeared.

The issue does not appear on 14.4 and up.

There is anyway an issue, since the port links to a static library where
a dynamic one should be used.

Also, the version check in the port is the fix must be applied needs
updating. The port is installing libinotify from ports in cases where it
is not needed.

I'm going to fix these issues shortly.


Regarding versions, 14.3 has been EOL for a while and is not supported.
14.4 will be EOL in December if I remember correctly.
--
Guido Falsi <madpilot@FreeBSD.org>


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.22a-Linux NewsLink 1.2