[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171004103502.GN15263@port70.net>
Date: Wed, 4 Oct 2017 12:35:03 +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 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.
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.
