dynamic compile issue

dynamic compile issue

[stephen Turner]

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

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
the chroot yet and im sure that this is caused by me but i just dont know
where or what to look for?  there is no ldconfig installed or running which
was mentioned as a possible issue referring to the wrong libs.

I greatly appreciate any help you can provide.

thanks,
stephen

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

Re: dynamic compile issue

[Isaac Dunham]

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

Re: dynamic compile issue

[stephen Turner]

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

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 <ibid.ag@gmail.com> 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
>
>

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

Re: dynamic compile issue

[Rich Felker]

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"
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

Re: dynamic compile issue

[stephen Turner]

[-- 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 --]