libglib2: don't try to use DTrace/GCov/SystemTap for host build
PATCH 1/1 libglib2: don't try to use DTrace/GCov/SystemTap for host build
We really only need the host build of libglib2 for a few helper programs that are used for the target build of libglib2. Therefore, trying to use bells and whistles like DTrace, GCov and SystemTap is useful.
And it is actually harmful, since it is causing build failures on the gcc110 PowerPC-based autobuilder that apparently has some DTrace-feature installed. This commit therefore fixes:
http://autobuild.buildroot.org/results/1c62d1ce10937bd21f5afcb73782b939d10c2038/build-end.log
Which has been polluting our autobuilder logs since several weeks now.
--- package/libglib2/libglib2.mk | 3 +++ 1 file changed, 3 insertions(+)
package/libglib2/libglib2.mk +3 -0
@@ -53,6 +53,9 @@ endif HOST_LIBGLIB2_CONF_OPT = \ --disable-gtk-doc \ --enable-debug=no \ + --disable-dtrace \ + --disable-systemtap \ + --disable-gcov LIBGLIB2_DEPENDENCIES = host-pkgconf host-libglib2 libffi zlib $(if $(BR2_NEEDS_GETTEXT),gettext)
Signature · 1 line
1.7.9.5
PATCH 1/1 libglib2: don't try to use DTrace/GCov/SystemTap for host build
Hi Thomas,
Quoted 4 lines · Thomas Petazzoni
We really only need the host build of libglib2 for a few helper programs that are used for the target build of libglib2. Therefore, trying to use bells and whistles like DTrace, GCov and SystemTap is useful.
Not?
Quoted 18 lines
And it is actually harmful, since it is causing build failures on the gcc110 PowerPC-based autobuilder that apparently has some DTrace-feature installed. This commit therefore fixes:
http://autobuild.buildroot.org/results/1c62d1ce10937bd21f5afcb73782b939d10c2038/build-end.log
Which has been polluting our autobuilder logs since several weeks now.
Signed-off-by Thomas Petazzoni <[email protected]>--- package/libglib2/libglib2.mk | 3 +++ 1 file changed, 3 insertions(+)package/libglib2/libglib2.mk +0
-0
package/libglib2/libglib2.mk endif · line 60
Quoted 8 lines
package/libglib2/libglib2.mk +3
-0@@ -53,6 +53,9 @@ endif HOST_LIBGLIB2_CONF_OPT = \ --disable-gtk-doc \ --enable-debug=no \ + --disable-dtrace \ + --disable-systemtap \ + --disable-gcov LIBGLIB2_DEPENDENCIES = host-pkgconf host-libglib2 libffi zlib $(if $(BR2_NEEDS_GETTEXT),gettext)
baruch
Signature · 3 lines
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -PATCH 1/1 libglib2: don't try to use DTrace/GCov/SystemTap for host build
Dear Baruch Siach,
Quoted 7 lines · Baruch Siach
Quoted 4 lines · Thomas Petazzoni
We really only need the host build of libglib2 for a few helper programs that are used for the target build of libglib2. Therefore, trying to use bells and whistles like DTrace, GCov and SystemTap is useful.
Not?
Yes, thanks, I've sent a v2 that fixes that.
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com