Bug ID |
13018
|
Summary |
abi-compliance-checker isn't finding glib in the "check abi" step
|
Product |
Wireshark
|
Version |
Git
|
Hardware |
x86-64
|
OS |
Debian
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Low
|
Component |
Build process
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Build Information:
Current master, 2.2, and 2.0 branches
--
The "check abi" step is failing with:
rm -rf abi-check-headers abi_dumps .libs/*.abi.tar.gz
mkdir abi-check-headers
cp *.h ../ws_symbol_export.h abi-check-headers/
abi-compliance-checker -log-path abi_logs/log.txt -l libwiretap -v1 `readlink
.libs/libwiretap.so | sed 's/.*\.so\.//'` \
-relpath
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/build/wiretap
-dump-abi abi-descriptor.xml || \
cat abi_logs/log.txt
Using GCC 5.4.0 (x86_64-linux-gnu, target: x86_64)
checking header(s) 0.0.0 ...
ERROR: some errors occurred when compiling headers
ERROR: see log for details:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/build/wiretap/abi_logs/log.txt
ERROR: can't compile header(s)
Temporary header file '/tmp/gDlYQSHa01/dump1.h' with the following content will
be compiled to create GCC translation unit dump:
// add includes
#include
"/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/build/config.h"
#include
"/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/build/wiretap/abi-check-headers/libpcap.h"
...
The GCC parameters:
gcc -fdump-translation-unit -fkeep-inline-functions -c -x c++-header
-fpermissive -w -D_U_="__attribute((unused))" "/tmp/gDlYQSHa01/dump1.h"
-I/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/build
-I/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/build/wiretap
In file included from /tmp/gDlYQSHa01/dump1.h:4:0:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/build/wiretap/abi-check-headers/libpcap.h:24:18:
fatal error: glib.h: No such file or directory
compilation terminated.
Do we need to pass some flag to the ABI checker to tell it where to look for
GLib headers, or something such as that?
You are receiving this mail because:
- You are watching all bug changes.