[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGw6cBtoY2YnSCFpHOBy5MqzsjSANhYfQknrgr6vDacuB3LFuw@mail.gmail.com>
Date: Wed, 19 Aug 2020 14:00:13 -0700
From: Michael Forney <mforney@...rney.org>
To: Rich Felker <dalias@...c.org>
Cc: musl@...ts.openwall.com
Subject: Re: Re: [musl-cross-make] [PATCH v2] litecross: Fix system
header dir when building native toolchains
On 2020-05-10, Rich Felker <dalias@...c.org> wrote:
> I'll try to get back to this sometime soon, but at the moment my focus
> is already split several ways between mallocng, initial entropy source
> and csprng issues for musl (was considered a prereq for merging
> mallocng but I think it's turning out to be mostly separate which may
> mean I can punt on this for a while), bringing this all together for
> next musl release, and paid work independent from musl.
Now that musl 1.2.1 is out, can we revisit this?
To make sure we're on the same page, do you agree that if I build a
musl-cross-make toolchain with NATIVE=1, and install it to some
arbitrary directory $TOOLCHAIN, then the following is true?
1. The musl headers are located in $TOOLCHAIN/include.
2. $TOOLCHAIN/bin/gcc should include the directory containing musl
headers somewhere in its header search path.
3. $TOOLCHAIN/usr does not exist, so it is not useful to search for
headers in $TOOLCHAIN/usr/include
The only effect of my patch is to add $TOOLCHAIN/include to the header
search path of $TOOLCHAIN/bin/gcc and remove $TOOLCHAIN/usr/include
from the header search path of $TOOLCHAIN/bin/gcc, correcting points 2
and 3 above.
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.
