Older GCC versions (e.g. < 4.9) may complain about inline functions that
cannot be inlined (growing the generated code). It is not really a
problem for us, so just suppress again the warning.
Followup of commit c37c554fc56151b709882b382bb5fa26d9083449.
---
m4/guestfs_c.m4 | 1 +
1 file changed, 1 insertion(+)
diff --git a/m4/guestfs_c.m4 b/m4/guestfs_c.m4
index 7250294..ea26202 100644
--- a/m4/guestfs_c.m4
+++ b/m4/guestfs_c.m4
@@ -48,6 +48,7 @@ nw="$nw -Wtraditional" # Warns on #elif which
we use often
nw="$nw -Wsystem-headers" # Don't let system headers trigger
warnings
nw="$nw -Wpadded" # Our structs are not padded
nw="$nw -Wvla" # Allow variable length arrays.
+nw="$nw -Winline" # inline functions in Python binding
nw="$nw -Wshadow" # Not useful, as it applies to global vars
nw="$nw -Wunsafe-loop-optimizations" # just a warning that an optimization
# was not possible, safe to ignore
--
2.1.0
_______________________________________________
Libguestfs mailing list
Libguestfs@redhat.com
https://www.redhat.com/mailman/listinfo/libguestfs
