Re: [Burp-users] Burp 2.2.x Build From Source on Linux/Unix

[Iznohak <xst...@ya...>]

Yes I can do patches. In what format do you prefer to get them?

No worries about your speed or response time. I appreciate yet your taking the time to read and respond.

Xavier S.



 On Wednesday, June 13, 2018, 9:44:10 AM GMT+2, Graham Keeling <gr...@gr...> wrote: 


On Mon, Jun 11, 2018 at 10:33:31PM +0000, Iznohak via Burp-users wrote:
> Two minor issues to report:
> 
> 1. The config.sub and config.guess autoconf scripts provided in release tarballs (off Github) are outdated. In particular config.sub doesn't accept config triplets for systems that have become common in the past few years.
> 
> For example, in my case:
> 
> $ ./burp-2.2.4/autoconf/config.sub x86_64-linux-musl
> Invalid configuration `x86_64-linux-musl': system `musl` not recognized
> 
> The Burp build may not actually care what config triplet it's actually built on, I haven't looked into it. But ./configure accepting --build=x86_64-linux-musl would make it easier to build Burp on more Linux distributions like Alpine or Sabotage, which are based on musl libc.
> 
> You can grab the latest versions of config.sub and config.guess from the offical repository here:
> http://git.savannah.gnu.org/cgit/config.git/tree/
> 
> In case this is news to you, you may be interested to know that Burp builds and runs fine, without any change apart from the autoconf stuff, with musl libc (a replacement for glibc) and with LibreSSL (a replacement for OpenSSL).
> 
> 2. The README states that building Burp requires yajl, but yajl is actually included in the burp source tree. The README should be updated to remove the requirement if indeed it is no longer needed.
> 
> I had thoroughly followed the instructions and built yajl separately, but while troubleshooting something else, I noticed that the burp binary wasn't actually linked to the yajl dynlib. And while rebuilding burp, I saw that the configure phase doesn't actually look for yajl at all.
> 
> I guess the requirement for yajl was in an older burp version and the README wasn't updated?
> 
> If you confirm one or both of these issues, let me know if you'd like me to log them on GitHub so you can track them.


1.
Cool, that is nice news.

2.
You are correct, the information is probably outdated.

Two issues on github are fine. You are also welcome to push patches if you
want to speed some of these things up, as I am very slow right now.