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 v2] sdl_mixer: fix static linking issue
Date: Fri, 9 Dec 2016 10:55:07 +0100	[thread overview]
Message-ID: <20161209105507.4d3d7910@free-electrons.com> (raw)
In-Reply-To: <20161209042718.GC15584@waldemar-brodkorb.de>

Hello,

On Fri, 9 Dec 2016 05:27:18 +0100, Waldemar Brodkorb wrote:

> > musl is also using a "everything in libc" policy. Does this problem
> > also occurs with musl? If not, why?  
> 
> It does not happen with musl because musl does not use libgcc
> unwinding functionality for pthread_cancel implementation.
> If anyone want to hack on uClibc-ng, I would love to get the libgcc
> dependency out. Old linuxthreads didn't use it, so this would
> be a good starting point to look at :)
> 
> If you would allow to use glibc for static linking, which is
> technically possible, you would see the same issue.

OK. Thanks a lot for this explanation. This clarifies why we're seeing
this with uClibc-ng only, which is what I wanted to understand.

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

  reply	other threads:[~2016-12-09  9:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 17:23 [Buildroot] [PATCH v2] sdl_mixer: fix static linking issue Waldemar Brodkorb
2016-12-08 21:06 ` Thomas Petazzoni
2016-12-09  4:27   ` Waldemar Brodkorb
2016-12-09  9:55     ` Thomas Petazzoni [this message]
2016-12-10 15:00 ` Thomas Petazzoni

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=20161209105507.4d3d7910@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