Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 18 Jan 2020 00:14:47 -0500
From: Rich Felker <>
Subject: Re: Absolute symlink breaks cross compilation

On Sat, Jan 18, 2020 at 02:24:49AM +0300, Андрей Аладьев wrote:
> Hello. Gentoo users find that it is not possible to cross compile musl. See
> here more details.
> I am sending to you proposed patch that is related to upstream. Please keep
> all installed symlinks relative. Thank you.

> diff --git a/Makefile b/Makefile
> index bd8f5c38..81bf33d5 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -209,7 +209,7 @@ $(DESTDIR)$(includedir)/%: $(srcdir)/include/%
>  	$(INSTALL) -D -m 644 $< $@
> -	$(INSTALL) -D -l $(libdir)/ $@ || true
> +	$(INSTALL) -D -l $$(realpath --no-symlinks --relative-to=$$(dirname $@) $(DESTDIR)$(libdir)/ $@ || true
>  install-libs: $(ALL_LIBS:lib/%=$(DESTDIR)$(libdir)/%) $(if $(SHARED_LIBS),$(DESTDIR)$(LDSO_PATHNAME),)

I don't understand what you mean by it "breaks cross compilation". The
ldso link produced is not used for compiling anything; it's only used
for executing programs, which you don't do when cross compiling musl
or cross compiling applications against it. The link is setup to be
installed on the $host, not to be used on the $build where it's not

Could you could explain what specifically you're trying to do that's
not working as desired?


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.