On 29/05/13 15:12, William Harrington wrote:
On May 29, 2013, at 8:28 AM, bvl wrote:
As 'header' and 'include' generally go together
However,
The search list is including /tools/include when using
--with-system-native-header-dir=/tools
#include "..." search starts here:
#include <...> search starts here:
/tools/lib/gcc/x86_64-unknown-linux-gnu/4.8.0/include
/tools/include
/tools/lib/gcc/x86_64-unknown-linux-gnu/4.8.0/include-fixed
/usr/include
End of search list.
Sincerely,
William Harrington
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
Just had a quick look into this, i don't think it matters in our
context it seems to set an environment variable NATIVE_SYSTEM_HEADERS,
but CROSS_SYSTEM_HEADERS is always set to /tools/include which ever way
the switch is set
i suppose it won't hurt --with-system-native-header-dir=/tools/include
for consistency
opinions ?
Martin
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
