Actions
Bug #4114
closedosmo-ggsn fails to compile on openSUSE Tumbleweed (gcc 9.1 with LTO enabled)
Start date:
07/17/2019
Due date:
% Done:
0%
Spec Reference:
Description
here's the problematic compiler warning:
[ 25s] libtool: link: gcc -O2 -D_GNU_SOURCE -fno-builtin -Wall -DSBINDIR=\"/usr/sbin\" -ggdb -I/usr/include/libosmocore/ -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-s trong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -flto=4 -g -o .libs/sgsnemu sgsnemu.o cmdline.o /home/abuild/rpmbuild/BUILD/osmo-ggsn-1.3.0.46/ gtp/.libs/libgtp.so -L../gtp ../lib/libmisc.a -ltalloc -losmocore -Wl,-rpath -Wl,/usr/lib64 [ 26s] In function 'memset', [ 26s] inlined from 'in46a_from_eua' at in46_addr.c:344:5, [ 26s] inlined from 'create_pdp_conf' at sgsnemu.c:1405:6, [ 26s] inlined from 'conf' at sgsnemu.c:1511:10: [ 26s] /usr/include/bits/string_fortified.h:71:10: warning: '__builtin___memset_chk' writing 16 bytes into a region of size 0 overflows the destination [-Wstringop-overflow=] [ 26s] 71 | return __builtin___memset_chk (__dest, __ch, __len, __bos0 (__dest)); [ 26s] | ^
OBS build fails because the above mentioned compiler warning the turns into an error by on of the RPM post build checks:
[ 31s] I: Statement might potentially overflow a destination buffer, where a size larger [ 31s] than the actual buffer was specified [ 31s] E: osmo-ggsn destbufferoverflow /usr/include/bits/string_fortified.h:71, 34
I have attatched the full buildlog.
Files
Related issues
Updated by laforge over 4 years ago
- Related to Bug #4113: osmo-bsc fails to compile on openSUSE Tumbleweed (gcc 9.1 with LTO enabled) added
Updated by laforge over 4 years ago
- Project changed from Cellular Network Infrastructure to OsmoGGSN (former OpenGGSN)
- Assignee set to Hoernchen
Updated by Hoernchen over 4 years ago
- Related to Bug #4123: gcc & LTO related issues added
Actions