libsvg-cairo: explicitly disable X support
PATCH 1/1 libsvg-cairo: explicitly disable X support
Our libsvg-cairo package doesn't have any dependency on X, and the source code doesn't seem to be using X. However, the configure script checks for X headers and libraries. If they are found on the host, /usr/lib and /usr/include get added to the library/header paths causing weird build failures. This commit should fix this problem by explicitly disabling the X support.
Should fix:
http://autobuild.buildroot.org/results/d0f/d0fc233bb97c2ea18344746a5b7c63c8de65330a/
http://autobuild.buildroot.org/results/0b3/0b3fb2ee9916aa265df5b6e4f04f6dfa25d1fc84/
--- package/libsvg-cairo/libsvg-cairo.mk | 2 ++ 1 file changed, 2 insertions(+)
package/libsvg-cairo/libsvg-cairo.mk +2 -0
@@ -11,4 +11,6 @@ LIBSVG_CAIRO_INSTALL_STAGING = YES LIBSVG_CAIRO_LICENSE = LGPLv2.1+ LIBSVG_CAIRO_LICENSE_FILES = COPYING +LIBSVG_CAIRO_CONF_OPT = --without-x + $(eval $(autotools-package))
Signature · 1 line
2.0.0
PATCH 1/1 libsvg-cairo: explicitly disable X support
Quoted 9 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Thomas" == Thomas Petazzoni <[email protected]> writes:
Our libsvg-cairo package doesn't have any dependency on X, and the source code doesn't seem to be using X. However, the configure script checks for X headers and libraries. If they are found on the host,
/usr/liband/usr/includeget added to the library/header paths causing weird build failures. This commit should fix this problem by explicitly disabling the X support.
Quoted 6 lines
Should fix:
http://autobuild.buildroot.org/results/d0f/d0fc233bb97c2ea18344746a5b7c63c8de65330a/
http://autobuild.buildroot.org/results/0b3/0b3fb2ee9916aa265df5b6e4f04f6dfa25d1fc84/Signed-off-by Thomas Petazzoni <[email protected]>
Committed, thanks.
Signature · 1 line
Bye, Peter Korsgaard