On 12/04/2017 01:11 PM, Marek wrote:
looking at config.log i see theses errors:
Configure does a number of feature tests to see what features are
available for use. It is expected that some of these feature tests will
fail. Some features are optional, and if that feature test fails there
is no problem; we just use an alternative feature. Some features are
required, and if that feature test fails then configure exits with an
error. If you get one of these, it will be the very last feature test
in the config.log file, and will have some kind of error message that
indicates that configure can not continue after this failure.
But this doesn't seem relevant to your problem, as Kai Ruottu already
pointed out what is wrong...
On Fri, Dec 1, 2017 at 11:23 AM, Kai Ruottu <kai.ruo...@wippies.com> wrote:
Kai Ruottu kirjoitti 1.12.2017 klo 12:02:
Answering to my own question... Yes, it should include this :
https://git.musl-libc.org/cgit/musl/tree/include
Maybe there is another target name one should use like
'x86_64-lfs-linux-musl' in your case?
The docs for musl are telling just this, one should use the
'<arch>-linux-musl' triplet!
Gcc assumes glibc for for a linux target. If you want to use musl, you
must include musl in the target triplet that you configure for. See the
gcc/config.gcc file, and look at the places where it checks the target
triplet for musl to enable musl support.
Jim
