On 10/11/2010 07:39 PM, Gary V. Vaughan wrote:
There are only two options to make both cases behave the same -1. always hardcode the full path to the system header, even on machines with include_next support;
(1) is not viable. If a system header itself uses include_next, then we MUST include that header via system_include, or the nested include_next tries to include the same absolute name (itself) instead of its intended target. That's why we had to start using include_next throughout gnulib in the first place.
-- Eric Blake [email protected] +1-801-349-2682 Libvirt virtualization library http://libvirt.org
