[Buildroot] wireshark failure
Peter Korsgaard
peter at korsgaard.com
Fri Jun 1 14:23:48 UTC 2018
>>>>> "Arnout" == Arnout Vandecappelle <arnout at mind.be> writes:
> Hi all,
> On 30-05-18 08:00, Thomas Petazzoni wrote:
>> arm | wireshark-2.2.14 | NOK |
>> http://autobuild.buildroot.net/results/7384adae1e15ef8361fe60d6119f9c0bf925b26b
>> | ORPH
> wireshark + qt5 + gcc6+ has been failing since November 11 last year
> http://autobuild.buildroot.net/results/6326b6fdebc5ed56b60f45c231edce07b3ac801e
> with
> In file included from
> /accts/mlweber1/instance-2/output/host/opt/ext-toolchain/x86_64-amd-linux-gnu/include/c++/6.2.0/bits/stl_algo.h:59:0,
> ...
> /accts/mlweber1/instance-2/output/host/opt/ext-toolchain/x86_64-amd-linux-gnu/include/c++/6.2.0/cstdlib:75:25:
> fatal error: stdlib.h: No such file or directory
> #include_next <stdlib.h>
> This is because gcc 6 has started providing stdlib.h itself, but wireshark
> changes all -I options into -isystem which makes the include_next not find
> stdlib.h any more. (Note, I have not found out why it didn't fail before
> November 11; the autobuilders were already using GCC6, and wireshark itself was
> bumped months before...).
> There are two possible solutions for this:
> 1. Revert upstream commit 67d9daa65b9d "autotools: Fix extra-compiler-warnings
> for system headers". It's a rather big commit, though, and it doesn't revert
> cleanly.
> 2. Switch to CMake, which anyway has to happen at some point since newer
> releases have dropped autotools.
> I've started doing the latter, but it turns out that the CMake infrastructure
> no longer supports GTK2. So, that would also imply removing GTK2 support from
> wireshark.
> Since we're just before the 2018.05 release, and since this should also be
> backported to 2018.02, I wasn't sure whether that was acceptable...
> Basically, it's choosing between supporting GTK2, or supporting QT5 + GCC6, or
> a possibly very complicated configure.ac + Makefile.am patch.
Hmm, neither of which sounds very appealing. I think dropping gtk2
support is probably the least bad option, so lets go for cmake.
It will be too late for 2018.05, but as this has been failing since
November I guess that isn't such a big deal.
--
Bye, Peter Korsgaard
More information about the buildroot
mailing list