[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171003105951.GM15263@port70.net>
Date: Tue, 3 Oct 2017 12:59:51 +0200
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Subject: Re: musl-cross-make doesn't install gcc binaries
* Didier Kryn <kryn@...p3.fr> [2017-10-03 12:38:49 +0200]:
> Le 03/10/2017 à 11:37, Szabolcs Nagy a écrit :
> > it's a cross compiler, so you won't have gcc, but x86_64-linux-musl-gcc
> But it isn't installed and, BTW, the installed binutils executables
> aren't prefixed with x86_64-linux-musl-
>
> When I remove the line 'OUTPUT = /usr/pkg' in config.mak, to leave it
> use the default, then the installation occurs in subdir 'output' of the
> source tree, and it seems much more familiar to me, with more subdirs, such
> as libexec, share and x86_64-linux-musl, which are not present otherwise.
> And all the executables are correctly prefixed.
>
> Therefore the problem is restricted to the processing of the custom
> install dir. Given the cross-compiler is sysrooted, this isn't a big deal,
> but better to know.
>
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)
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.
