mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Barry Flartus <barry.flartus@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Problems with pthreads from a shared object?
Date: Thu, 8 Nov 2018 12:14:39 -0500	[thread overview]
Message-ID: <CAHnO0JutizVnGrHVXW_E8JEg3NT-Bi436DQrepx0zz1w9uk0XQ@mail.gmail.com> (raw)
In-Reply-To: <20181108151715.GA5150@brightrain.aerifal.cx>

[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]

>
> I think it would be helpful to understand what you're trying to do.
>

Thanks for your help so far. Let me try and explain what I'm trying to
accomplish. I have a program that runs as an executable and uses pthreads.
I've compiled this program with musl statically with the end goal of it
being portable across older and newer systems. I want to also be able to
compile this program as a shared object so it may be loaded via dlopen()
inside of a glibc program. As mentioned previously, if I compile my shared
object with glibc, it loads via dlopen().

My lack of understanding is this: if I directly compile in musl's libc.a
(which contains its implementation of pthreads) into my shared object,
shouldn't it have the relevant pthreads functions compiled in, without
having runtime issues? That's what seems to work for my musl-compiled
static executable, so I'm trying to wrap my head around why it wouldn't
work for a shared object. In my case, I'm considering the shared object
just a different form-factor for the same program.

[-- Attachment #2: Type: text/html, Size: 1447 bytes --]

  reply	other threads:[~2018-11-08 17:14 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
2018-11-08 14:53             ` Barry Flartus
2018-11-08 15:17               ` Rich Felker
2018-11-08 17:14                 ` Barry Flartus [this message]
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=CAHnO0JutizVnGrHVXW_E8JEg3NT-Bi436DQrepx0zz1w9uk0XQ@mail.gmail.com \
    --to=barry.flartus@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).