Attachment 79926 Details for Bug 65103 – mesa: fix build on uclibc system

mesa: fix build on uclibc system

0001-mesa-fix-build-on-uclibc-system.patch (text/plain), 1.44 KB, created by Anthony G. Basile on 2013-05-28 23:05:05 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Anthony G. Basile

Created: 2013-05-28 23:05:05 UTC

Size: 1.44 KB

patch

obsolete

>From 7d470385f356059a8ed5d090a32e3e6a494e7c81 Mon Sep 17 00:00:00 2001
>From: "Anthony G. Basile" <blueness@gentoo.org>
>Date: Tue, 28 May 2013 22:58:10 +0000
>Subject: [PATCH] mesa: fix build on uclibc system
>
>execinfo.h and debug_symbol_name_glibc() are pure GNU-isms and do not
>build on uclibc systems.  A previous patch addressed this issue, but
>there was an error.  This patch corrects that error.  See
>
>  https://bugs.freedesktop.org/show_bug.cgi?id=51782
>  https://bugs.gentoo.org/show_bug.cgi?id=469768
>
>Signed-off-by: Anthony G. Basile <blueness@gentoo.org>
>---
> src/gallium/auxiliary/util/u_debug_symbol.c |    6 ++----
> 1 files changed, 2 insertions(+), 4 deletions(-)
>
>diff --git a/src/gallium/auxiliary/util/u_debug_symbol.c b/src/gallium/auxiliary/util/u_debug_symbol.c
>index 3d2f8eb..0ef111c 100644
>--- a/src/gallium/auxiliary/util/u_debug_symbol.c
>+++ b/src/gallium/auxiliary/util/u_debug_symbol.c
>@@ -151,10 +151,8 @@ debug_symbol_name_dbghelp(const void *addr, char* buf, unsigned size)
> }
> #endif
> 
>-#ifdef __GLIBC__
>-#ifndef __UCLIBC__
>+#if defined(__GLIBC__) && !defined(__UCLIBC__)
> #include <execinfo.h>
>-#endif
> 
> /* This can only provide dynamic symbols, or binary offsets into a file.
>  *
>@@ -179,7 +177,7 @@ debug_symbol_name(const void *addr, char* buf, unsigned size)
>       return;
> #endif
> 
>-#ifdef __GLIBC__
>+#if defined(__GLIBC__) && !defined(__UCLIBC__)
>    debug_symbol_name_glibc(addr, buf, size);
>    if(buf[0])
>       return;
>-- 
>1.7.8.6
>

Actions: View

Attachments on bug 65103: 79926

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.