Forwarding to freebsd-ports in case someone else finds it useful.
On Tuesday, 10 June 2014, 13:35, Kostas Peletidis <[email protected]> wrote: > > >Hi, > > >The following is a summary of a little adventure I had recently with the >spdylay port. I post it here in the hope that other users might find it >helpful. If any ports experts could help identify the root problem and maybe >the best solution that would be great. > > >======== > >PROBLEM: >---------------- > >Port www/spdylay breaks if devel/libevent is installed. > > >SOLUTION: >---------------- >No clean solution is available yet. A partial solution that involves the >removal of devel/libevent is described in the workaround section. > > > >WORKAROUND: >---------------- >Deinstall devel/libevent (make deinstall) and rebuild www/spdylay (make clean >&& make). >======== > > >DETAILS: >---------------- >I noticed that www/spdylay "suddenly" wouldn't build correctly, complaining >about unknown data types: > > >In file included from shrpx_config.cc:25: >./shrpx_config.h:151:3: error: unknown type name 'ev_token_bucket_cfg' > ev_token_bucket_cfg *rate_limit_cfg; > ^ >./shrpx_config.h:153:3: error: unknown type name 'ev_token_bucket_cfg' > ev_token_bucket_cfg *worker_rate_limit_cfg; > ^ >In file included from shrpx_config.cc:42: >./shrpx_ssl.h:50:2: error: unknown type name 'bufferevent_rate_limit_group' > bufferevent_rate_limit_group *rate_limit_group, > ^ >./shrpx_ssl.h:52:2: error: unknown type name 'evutil_socket_t' > evutil_socket_t fd, > ^ >4 errors generated. >*** [shrpx_config.o] Error code 1 > > >Note that these are libevent data types. Spdylay depends on devel/libevent2. > > >After digging around I found that another port, security/stegdetect, installed >devel/libevent as a dependency and www/spdylay stopped building since then. > > >In my case removing devel/libevent and the port that depended on it was >acceptable since I don't really use it. However, there is still the issue of >what seems to be a conflict between libevent and libevent2. Also, I am not >sure if my workaround broke something else. > > >Any comments on what needs to be fixed and how would be appreciated. Thanks. > > > >Regards, >Kostas > > > _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
