On 02/19/13 10:39, Daniel Nebdal wrote:
The obvious issue is apparently that there's not an "-linotify" in
that argument list (or, alternatively, that is uses inotify functions
when it shouldn't) - though I'm far from sure why that would happen.
Do you have devel/libinotify installed? What does "grep inotify
work/Window*/config.log " say?
--
Daniel Nebdal
configure:12047: checking sys/inotify.h usability
configure:12047: gcc -c -O2 -pipe -fno-strict-aliasing -Wall -Wextra
-Wno-sign-compare -Wno-unused-parameter -D_XOPEN_SOURCE=600 -DFREEBSD
-I/usr/local/include conftest.c >&5
configure:12047: $? = 0
configure:12047: result: yes
configure:12047: checking sys/inotify.h presence
configure:12047: gcpp -I/usr/local/include conftest.c
configure:12047: $? = 0
configure:12047: result: yes
configure:12047: checking for sys/inotify.h
configure:12047: result: yes
...
ac_cv_header_sys_inotify_h=yes
--
Yours in Christ,
Joseph A Nagy Jr
"Whoever loves instruction loves knowledge, But he who hates correction
is stupid." -- Proverbs 12:1
Emails are not formal business letters, whatever businesses may want.
Original content CopyFree (F) under the OWL
http://copyfree.org/licenses/owl/license.txt
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
