mailing list of musl libc
 help / color / mirror / code / Atom feed
From: stephen Turner <stephen.n.turner@gmail.com>
To: musl@lists.openwall.com
Subject: Re: dynamic compile issue
Date: Thu, 18 Dec 2014 15:13:12 -0500	[thread overview]
Message-ID: <CAA7aPHiRNyCK0UVC-z306pj6P7ipBWNzMiEfCgCou0aeC_0ixQ@mail.gmail.com> (raw)
In-Reply-To: <20141218191412.GT4574@brightrain.aerifal.cx>

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

On Thu, Dec 18, 2014 at 2:14 PM, Rich Felker <dalias@libc.org> wrote:

> On Thu, Dec 18, 2014 at 01:47:49PM -0500, stephen Turner wrote:
> > im using PCC as my compiler. it was initially built with gcc but since
> has
> > recompiled itself several times. 2 at least in the chroot musl only
> > environment alone. would this advice still apply? If i understood the pcc
> > group correctly it should not be responsible for this but i cant help but
> > think it is. regardless i will look into any advice/leads provided.
>
> PCC probably just has /lib/ld-linux.so.2 hard-coded for the "linux"
>

this was my assumption as well. I only found ref of the ld-linux.so.2 in a
header however and correcting the header code (adding a relevant entry for
musl) didn't seem to change the outcome.

target. You just need to change this when building it for a musl-based
> system or pass -Wl,-dynamic-linker,/lib/ld-musl-i386.so.1 (or whatever
> your arch is) on the command line.
>
> Rich
>

Thanks again rich, im going to give this a run and if it resolves the
issue, see what the PCC community says is responsible linker-vs-pcc.

thanks
stephen

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

      reply	other threads:[~2014-12-18 20:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18 16:04 stephen Turner
2014-12-18 18:43 ` Isaac Dunham
2014-12-18 18:47   ` stephen Turner
2014-12-18 19:14     ` Rich Felker
2014-12-18 20:13       ` stephen Turner [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=CAA7aPHiRNyCK0UVC-z306pj6P7ipBWNzMiEfCgCou0aeC_0ixQ@mail.gmail.com \
    --to=stephen.n.turner@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).