mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Jeffrey Walton <noloader@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Problems with pthreads from a shared object?
Date: Thu, 8 Nov 2018 03:50:00 -0500	[thread overview]
Message-ID: <CAH8yC8mr34poqgYAP43akBOB4SUhHa7avYj2s_r3kgBVj5e+Lg@mail.gmail.com> (raw)
In-Reply-To: <20181108004312.GX5150@brightrain.aerifal.cx>

On Wed, Nov 7, 2018 at 7:43 PM Rich Felker <dalias@libc.org> wrote:
>
> On Wed, Nov 07, 2018 at 06:53:33PM -0500, Barry Flartus wrote:
> > >
> > > OK. Can you run strace -f ./launch (or whatever the launch program
> > > executable is called) and post the output?
> > > ...
> >
> > $ strace -f ./launch
> > execve("./launch", ["./launch"], [/* 22 vars */]) = 0
> > brk(NULL)                               = 0xe44000
> > access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or
>
> OK, this is a glibc program, not a musl one. That's your problem. How
> did you compile/link it?

Sorry to butt-in.

Alpine Linux uses musl. BF won't need anything special to use or
exercise musl (and certainly won't need to worry about
cross-pollination).

Jeff


  parent reply	other threads:[~2018-11-08  8:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 23:00 Barry Flartus
2018-11-07 23:31 ` Rich Felker
2018-11-07 23:40   ` Barry Flartus
2018-11-07 23:45     ` Rich Felker
2018-11-07 23:53       ` Barry Flartus
2018-11-08  0:43         ` Rich Felker
2018-11-08  1:02           ` Barry Flartus
2018-11-08  1:28             ` Rich Felker
2018-11-08  8:50           ` Jeffrey Walton [this message]
2018-11-08 14:53             ` Barry Flartus
2018-11-08 15:17               ` Rich Felker
2018-11-08 17:14                 ` Barry Flartus
2018-11-08 17:37                   ` Rich Felker
2018-11-08 17:56                     ` Barry Flartus

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=CAH8yC8mr34poqgYAP43akBOB4SUhHa7avYj2s_r3kgBVj5e+Lg@mail.gmail.com \
    --to=noloader@gmail.com \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).