mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: ld-musl-i386.so.1 disappear after gcc install
Date: Sun, 12 Feb 2017 22:26:28 -0500	[thread overview]
Message-ID: <20170213032628.GF1520@brightrain.aerifal.cx> (raw)
In-Reply-To: <000301d285a0$885689c0$99039d40$@binbones.com>

On Mon, Feb 13, 2017 at 03:26:07AM +0100, Romain wrote:
> Hello,
> 
> I try to create  a script to cross-build a small linux based on musl.
> (https://github.com/rom1nux/zydux-forge)
> 
> Basically I first create my cross toolchain in 3 steps
> 
> 1 – Build static gcc (first pass)
> 2 – Build musl
> 3 – Build dynamic gcc (second pass)
> 
> When I build musl, I can find the loader ld-musl-i386.so.1 this is a link to
> /lib/libc.so
> But when I do the second pass of gcc the ld-musl-i386.so.1 is removed at the
> gcc “make install”
> 
> I create a watch with “audit” to see what process remove the file, and it
> seem that /sbin/ldconfig.real remove the loader, I don’t understand why.
> (I fix this by creating my own link, and I can start my target, but I don’t
> understand what append)
> 
> My host :
> Ubuntu 16.04
> Arch : x86_64
> Kernel : 4.4.0
> Gcc : 5.4 (x86_64-linux-gnu-gcc)
> 
> My Cross/Target :
> Arch : x86
> Kernel : 4.9.7
> Gcc : 6.3.0 (i486-linux-musl-gcc)
> Musl : 1.1.16
> 
> Can you help  me to understand why the linker ld-musl-i386.so.1 is removed
> by /sbin/ldconfig.real, and how to avoid this ?

Where did ldconfig.real come from? If it's part of the Ubuntu system
you're compiling from, it shouldn't be getting run on the cross-target
at all; my guess would be that something in your build process is
unaware that you're cross-compiling. If it's part of the target musl
system then it should not even exist; ldconfig is a glibc thing.

Rich


  reply	other threads:[~2017-02-13  3:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13  2:26 Romain
2017-02-13  3:26 ` Rich Felker [this message]
2017-02-14 12:19   ` Romain

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=20170213032628.GF1520@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --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).