# \[Bro-Commits\] \[git/bro\] topic/jsiwek/broker: Add support for building/linking broker within bro (7120098) **URL:** \ **Category:** Development\ **Tags:** development\ **Created:** [January 9, 2015, 3:55pm UTC](https://community.zeek.org/t/bro-commits-git-bro-topic-jsiwek-broker-add-support-for-building-linking-broker-within-bro-7120098/3420 "2015-01-09T15:55:22Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![robin](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/robin/32/599_2.png) [@robin](https://community.zeek.org/u/robin)\ **Post date:** [January 9, 2015, 3:55pm UTC](https://community.zeek.org/t/bro-commits-git-bro-topic-jsiwek-broker-add-support-for-building-linking-broker-within-bro-7120098/3420/1 "2015-01-09T15:55:22Z")
We should probably make the C++11 dependency more explicit, in particular given that we want to prepare people for requiring it after 2.4. One idea would be an explicit --enable-C++11 configure switch, which --enable-broker would then either require, or activate automatically along with itself. That would then also allow us to generally test Bro compilation in C++11 mode. In addition, it would be good to check at configure time that the compiler indeed supports C++11; and if not, give an explicit erorr message stating so (rather than failing compiling later). Maybe even do that check without --enable-C++11 and warn people with older compilers that Bro in the future won't compile for them anymore. Nothing to do immediately, but to keep in mind as we get closer to the next release. Robin ---
**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\ **Post date:** [May 6, 2022, 3:42pm UTC](https://community.zeek.org/t/bro-commits-git-bro-topic-jsiwek-broker-add-support-for-building-linking-broker-within-bro-7120098/3420/2 "2022-05-06T15:42:20Z")