Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/valgrind: Fix musl build
Date: Tue, 26 Jan 2016 21:24:34 +0100	[thread overview]
Message-ID: <20160126212434.1e2af98b@free-electrons.com> (raw)
In-Reply-To: <1453837585-4799-1-git-send-email-bernd.kuhls@t-online.de>

Dear Bernd Kuhls,

On Tue, 26 Jan 2016 20:46:25 +0100, Bernd Kuhls wrote:

> diff --git a/package/valgrind/0004-musl.patch b/package/valgrind/0004-musl.patch
> new file mode 100644
> index 0000000..e1eb0a9
> --- /dev/null
> +++ b/package/valgrind/0004-musl.patch
> @@ -0,0 +1,51 @@
> +Fix musl build
> +
> +Patch suggested by Thomas: http://patchwork.ozlabs.org/patch/538683/

Did I ? I don't think I suggested this patch, only pointed some
existing ones.

> +diff -upr valgrind-3.11.0.orig/include/pub_tool_redir.h valgrind-3.11.0/include/pub_tool_redir.h
> +--- valgrind-3.11.0.orig/include/pub_tool_redir.h	2015-10-03 02:28:18.304309107 +0200
> ++++ valgrind-3.11.0/include/pub_tool_redir.h	2015-10-03 02:28:37.745672152 +0200
> +@@ -242,7 +242,7 @@
> + /* --- Soname of the standard C library. --- */
> + 
> + #if defined(VGO_linux) || defined(VGO_solaris)
> +-#  define  VG_Z_LIBC_SONAME  libcZdsoZa              // libc.so*
> ++#  define  VG_Z_LIBC_SONAME  libcZdZa                // libc.*
> + 
> + #elif defined(VGO_darwin) && (DARWIN_VERS <= DARWIN_10_6)
> + #  define  VG_Z_LIBC_SONAME  libSystemZdZaZddylib    // libSystem.*.dylib
> +@@ -274,7 +274,7 @@
> + /* --- Soname of the pthreads library. --- */
> + 
> + #if defined(VGO_linux)
> +-#  define  VG_Z_LIBPTHREAD_SONAME  libpthreadZdsoZd0     // libpthread.so.0
> ++#  define  VG_Z_LIBPTHREAD_SONAME  libcZdZa              // libc.*

I don't quite understand this one. While indeed with musl everything is
in libc.so, it's not the case for glibc and uClibc. Doesn't this break
stuff for glibc and uClibc ?

Any chance to submit this upstream so that we get some kind of review
from the valgrind maintainers ?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2016-01-26 20:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26 19:46 [Buildroot] [PATCH 1/1] package/valgrind: Fix musl build Bernd Kuhls
2016-01-26 20:24 ` Thomas Petazzoni [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160126212434.1e2af98b@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox