From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.2 Received: from mother.openwall.net (mother.openwall.net [195.42.179.200]) by inbox.vuxu.org (OpenSMTPD) with SMTP id d8bbde5c for ; Wed, 22 Jan 2020 10:34:16 +0000 (UTC) Received: (qmail 19860 invoked by uid 550); 22 Jan 2020 10:34:15 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 19824 invoked from network); 22 Jan 2020 10:34:14 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=UrIhlqkIhjoJ8tJk10VVX/T/PMQXHy0gS9AmYB3STTE=; b=o0N62YXyyQTpzGBtazqcz9fqOGUzD5kGoKjTfwvrNyljBEldBXZEtJNeE/k8NR70zS mwqOF1hcV9lYSAfbSt/YYC/RbkLvdvsOi7WCPExRmSGm5RXYPE8DNFNr8hyet2mbCQm5 3ft81+vEUgQPX01JYAAuzSC354cf2QcjSizLefTiBlpFgV3ZDDPbX8a9aKyoCfYpGumZ /5eGcZ29+YinJe0ZLOes3Kkwi99VKN4ifDkKMYwUTO0LO3YrViB3MEPW94FH/tgzaE4k 4Gzyt0qpNOjxBnz/VWT7ZF5dYgGEZFmlHXccx3/KkbKGVI+1jfbk/mmXEewekavn4Cgv zt4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=UrIhlqkIhjoJ8tJk10VVX/T/PMQXHy0gS9AmYB3STTE=; b=tOOxq9OxMY+mhjw2cDHJevZ/+LQn1ywcOTEJEgMguai57ZyJZnlEBKqBzV0ILx49nh 3m9NX8dgpJF+sgFjQ2tzUgrExW/TUCELB/SMGA4b+iOaOc0qMasBqlRXCkBvJCbcmcuo tO66lVUY+ras7xSKSyQ+z48Gkw0zl9kmfXLzR9S6QGGn3snoBaX/QoqeKJ8tA4Vc5kNA wUOUdpdrxgI7z2IE0l7ygiZiCmIWwRs+mO5ubZXvTsR0Pof5OY+MNY9qSbsVGfWJxdL2 rj3JvKAT9on09Uhc5L8wGQ1jCvJVksmW9vmER5xsG/Mu92PGpP8oJTqpk6LyVdj/g0mm z2nw== X-Gm-Message-State: APjAAAUE7+dcONwK7jlSC4CRAV4iiARbRInIR1H96yIvKqdvTf2ItBgJ oqibCKFTPz6wX+D1MH8yBqSLMaT8vOuiwGlYe+HlrYM4 X-Google-Smtp-Source: APXvYqwquQFdlE8EBuDbtsTMVzCzJPJ5AIR+WzVh7bHGjf6hvo12ojz0Jq/dIcPvKC1wgwMPIJvTkywHQkXkrRiTxLk= X-Received: by 2002:a05:651c:2046:: with SMTP id t6mr19335489ljo.180.1579689243260; Wed, 22 Jan 2020 02:34:03 -0800 (PST) MIME-Version: 1.0 From: =?UTF-8?B?0JDQvdC00YDQtdC5INCQ0LvQsNC00YzQtdCy?= Date: Wed, 22 Jan 2020 13:33:52 +0300 Message-ID: To: musl@lists.openwall.com Content-Type: multipart/alternative; boundary="000000000000333d0d059cb81011" Subject: [musl] Re: Absolute symlink breaks cross compilation --000000000000333d0d059cb81011 Content-Type: text/plain; charset="UTF-8" Hello Khem Raj and Rich Felker. > 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 > needed. > Could you could explain what specifically you're trying to do that's > not working as desired? I am doing musl cross compilation using "x86_64-pc-linux-musl-emerge -v1 sys-libs/musl". It cross compiles it and copies everything into the folder "/usr/x86_64-pc-linux-musl". For example "./usr/lib/libc.so" becomes "/usr/x86_64-pc-linux-musl/usr/lib/libc.so". "./lib/ld-musl-x86_64.so.1" becomes "/usr/x86_64-pc-linux-musl/lib/ld-musl-x86_64.so.1". So this installation breaks all absolute symlinks. I think the easiest way to fix it will be to keep all symlinks in musl relative. Now I have "ld-musl-x86_64.so.1 -> ../usr/lib/libc.so" and it works perfect. Thank you. --000000000000333d0d059cb81011 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello=C2=A0Khem Raj and=C2=A0Rich Felker.

>=C2=A0I don= 9;t understand what you mean by it "breaks cross compilation". Th= e
>=C2=
=A0ldso link produced is not used for compiling anything; it's only use=
d
>=C2=A0for executing programs, which you don't do when cross compili=
ng musl
>=C2=A0or cross compiling applications against it. The link is setup to =
be
>=C2=A0installed on the $host, not to be used on the $build where it'=
;s not
>=C2=A0needed.

>=C2=A0Could you could explain what specifically you're trying to do=
 that's
>=C2=A0not working as desired?
I am doing musl cross compilation using "x86_64-pc-li=
nux-musl-emerge -v1 sys-libs/musl". It cross compiles it and copies ev=
erything into the folder "/usr/x86_64-pc-linux-musl".

For example "./usr/lib/libc.so"=
; becomes "/usr/x86_64-pc-linux-musl/usr/lib/libc.so". "./li=
b/ld-musl-x86_64.so.1" becomes "/usr/x86_64-pc-linux-musl/lib/ld-=
musl-x86_64.so.1". So this installation breaks all absolute symlinks.<=
/pre>

I think the easiest way to fi=
x it will be to keep all symlinks in musl relative. Now I have "ld-mus=
l-x86_64.so.1 -> ../usr/lib/libc.so" and it works perfect. Thank yo=
u.


--000000000000333d0d059cb81011--