From: Didier Kryn <kryn@in2p3.fr>
To: musl@lists.openwall.com
Subject: Re: musl-cross-make doesn't install gcc binaries
Date: Wed, 4 Oct 2017 21:27:04 +0200 [thread overview]
Message-ID: <fae0f0d4-14c7-5f9c-85ae-fe7a70c0e0e6@in2p3.fr> (raw)
In-Reply-To: <20171004103502.GN15263@port70.net>
Le 04/10/2017 à 12:35, Szabolcs Nagy a écrit :
> * Didier Kryn <kryn@in2p3.fr> [2017-10-03 14:55:08 +0200]:
>> Le 03/10/2017 à 12:59, Szabolcs Nagy a écrit :
>>> i use custom OUTPUT dir and never had a problem
>>>
>>> (although i pass it as a make argument like
>>>
>>> make install TARGET=x86_64-linux-musl OUTPUT=/path
>>>
>>> and then i have
>>> /usr/bin/install -c xgcc /path/bin/x86_64-linux-musl-gcc
>>> in my build log)
>> OK, got it. I understood the install path as an install *prefix*. I
>> should have specified
>>
>> 'OUTPUT=/usr/pkg/x86_64-linux-musl'
>>
>> instead of
>>
>> 'OUTPUT=/usr/pkg'
>>
> no, it should be just /usr/pkg
>
>> And I didn't notice it created bin, include, lib, libexec and share and,
>> since it also created x86_64-linux-musl, which has the name I expected and
>> also contains bin, include and lib, I concentrated on this one which wasn't
>> as expected.
>>
> the x86_64-linux-musl directory is the sysroot for the target,
> it does not contain host binaries (executables for the cross
> toolchain)
>
>> Maybe worth mentionning the path is the base of the sysroot, not a
>> prefix. There must be other idiots like me.
>>
> no, it's not
>
>> Thanks for your patience.
>>
>> Didier
>>
>> Now it works. Thanks for your patience
>>
> you are probably still doing something wrong.
I have built the cross compiler with
TARGET = x86_64-linux-musl
OUTPUT= /usr/pkg/x86_64-linux-musl
After installation I have the following subdirs at the top of the tree:
/usr/pkg/x86_64-linux-musl/bin
/usr/pkg/x86_64-linux-musl/include
/usr/pkg/x86_64-linux-musl/lib
/usr/pkg/x86_64-linux-musl/libexec
/usr/pkg/x86_64-linux-musl/share
/usr/pkg/x86_64-linux-musl/x86_64-linux-musl
The first of these subdirs contains all the necessary executables
properly prefixed. And the last contains subdirs with the non-prefixed
executables, the libraries, including libc and the *crt*.o object files.
I have symlinked the prefixed binaries in /usr/bin and I am now
re-building all packages with my new gcc-6.3/musl-1.1.16 toolchain :-)
Didier
prev parent reply other threads:[~2017-10-04 19:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 10:05 C++ program with no dependencies except musl Paul Kaletta
2017-10-02 10:50 ` Szabolcs Nagy
2017-10-02 14:57 ` musl-cross-make doesn't install gcc binaries Didier Kryn
2017-10-02 15:57 ` Rich Felker
2017-10-03 8:11 ` Didier Kryn
2017-10-03 8:18 ` Didier Kryn
2017-10-03 9:37 ` Szabolcs Nagy
2017-10-03 10:38 ` Didier Kryn
2017-10-03 10:59 ` Szabolcs Nagy
2017-10-03 12:55 ` Didier Kryn
2017-10-04 10:35 ` Szabolcs Nagy
2017-10-04 19:27 ` Didier Kryn [this message]
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=fae0f0d4-14c7-5f9c-85ae-fe7a70c0e0e6@in2p3.fr \
--to=kryn@in2p3.fr \
--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).