[
https://bro-tracker.atlassian.net/browse/BIT-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25709#comment-25709
]
Matthias Vallentin commented on BIT-1554:
-----------------------------------------
Fixing this "soon" would probably only be possible via a hotfix release. But
since this is not a Bro issue, it doesn't seem to be the right path. We
currently have major refactoring of Broker underway. In this scope, we can also
convert the current bindings to Python 3.
What should we do with Python 2 support? From a maintaining point of view, I'd
say we should go with one version only, but I know too little about the
deployment of Python 2.
> broker (bro 2.4.1) fails to build against Python 3.{3,4,5}
> ----------------------------------------------------------
>
> Key: BIT-1554
> URL: https://bro-tracker.atlassian.net/browse/BIT-1554
> Project: Bro Issue Tracker
> Issue Type: Problem
> Components: Broker
> Affects Versions: 2.4
> Environment: Trying to compile Bro 2.4.1 on Gentoo Linux (x86_64)
> with broker enabled, against CAF 0.13.2, with python, using GCC support.
> Reporter: M.B.
> Priority: High
> Labels: build
> Fix For: 2.5
>
> Attachments: bro-2.4.1.ebuild, build.log
>
>
> Bro fails to build. Details (in particular the options cmake gets called
> with) can be seen from the build.log.
> For completeness I included the .ebuild.
--
This message was sent by Atlassian JIRA
(v7.2.0-OD-05-030#72002)
_______________________________________________
bro-dev mailing list
[email protected]
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
