From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6729 Path: news.gmane.org!not-for-mail From: stephen Turner Newsgroups: gmane.linux.lib.musl.general Subject: Re: dynamic compile issue Date: Thu, 18 Dec 2014 13:47:49 -0500 Message-ID: References: <20141218184313.GA1783@newbook> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=20cf307ca3b65e3148050a820798 X-Trace: ger.gmane.org 1418928491 17657 80.91.229.3 (18 Dec 2014 18:48:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 18 Dec 2014 18:48:11 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-6742-gllmg-musl=m.gmane.org@lists.openwall.com Thu Dec 18 19:48:04 2014 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1Y1g7G-0003ck-IN for gllmg-musl@m.gmane.org; Thu, 18 Dec 2014 19:48:02 +0100 Original-Received: (qmail 21953 invoked by uid 550); 18 Dec 2014 18:48:01 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 21937 invoked from network); 18 Dec 2014 18:48:00 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=PYQ60BsskxRNgFSMKM0OR3mUvXFbmSMgKNp+cmq7hQA=; b=D4iz0QyB/VU8gpnbqyj0bxc793Lz9rwysGrzCmJIfajyLn6zrVdwDY/LDZBqatpEMR rD2xIpe2W51WEOLDWnsV3JhOJerdIOq5gNS9Hgajr6LwyBlOed0TYg6oQWj4P6aEf7rr rVL8qt6sVvVEt9V//eDjjkPD1iArYpCYfDqqN2hu6OLSxUtidk5aKHrEaJltdy6sOeQx 6EJEHio0qtIrR85zHDBn0La56i7TXL5pBctbZZdQ+MnN63pLqFll++cp5n7oAgjeFzLK trDrM8WK0fy/lnvq3ZZIeq8u4biOTF5iYHd7AJwIqVSOlPowdaLhWCdhvAhs3WBPDSPD nRxw== X-Received: by 10.52.36.13 with SMTP id m13mr961493vdj.55.1418928469191; Thu, 18 Dec 2014 10:47:49 -0800 (PST) In-Reply-To: <20141218184313.GA1783@newbook> Xref: news.gmane.org gmane.linux.lib.musl.general:6729 Archived-At: --20cf307ca3b65e3148050a820798 Content-Type: text/plain; charset=UTF-8 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. On Thu, Dec 18, 2014 at 1:43 PM, Isaac Dunham wrote: > On Thu, Dec 18, 2014 at 11:04:16AM -0500, stephen Turner wrote: > > I have no reason to believe this is a musl issue but seeing that your in > > the business of building a libc i was hoping someone could give me a > > pointer or something to assist. > > > > I have a pure musl libc chroot and when compiling static it links/works > > fine. im now on my 2nd-3rd gen applications being compiled in the chroot > > alone. when i go to do a dynamic compile however it always wants to link > to > > ld-linux.so.2. I do not have any kind of scripts or anything running in > > You failed to patch GCC or configured it for glibc inadvertently. > (ld-linux.so.2 is the glibc dynamic linker.) > The patch and build options should be documented in bootstrap-linux or > musl-cross, whichever has the patches you're using at the moment. > (Check that you applied the patches *and* used the target that the > scripts use.) > > HTH, > Isaac Dunham > > --20cf307ca3b65e3148050a820798 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
im using PCC as my compiler. it was initially built with g= cc 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 h= elp but think it is. regardless i will look into any advice/leads provided.=

On Thu, Dec= 18, 2014 at 1:43 PM, Isaac Dunham <ibid.ag@gmail.com> wrote= :
On Thu, Dec 18, 2014 a= t 11:04:16AM -0500, stephen Turner wrote:
> I have no reason to believe this is a musl issue but seeing that your = in
> the business of building a libc i was hoping someone could give me a > pointer or something to assist.
>
> I have a pure musl libc chroot and when compiling static it links/work= s
> fine. im now on my 2nd-3rd gen applications being compiled in the chro= ot
> alone. when i go to do a dynamic compile however it always wants to li= nk to
> ld-linux.so.2.=C2=A0 I do not have any kind of scripts or anything run= ning in

You failed to patch GCC or configured it for glibc inadvertently. (ld-linux.so.2 is the glibc dynamic linker.)
The patch and build options should be documented in bootstrap-linux or
musl-cross, whichever has the patches you're using at the moment.
(Check that you applied the patches *and* used the target that the
scripts use.)

HTH,
Isaac Dunham


--20cf307ca3b65e3148050a820798--