This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] BZ#15711: Build syscall.h with -ffreestanding.
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: GNU C Library <libc-alpha at sourceware dot org>, "Joseph S. Myers" <joseph at codesourcery dot com>, David Miller <davem at davemloft dot net>
- Date: Mon, 15 Jul 2013 14:07:21 -0400
- Subject: Re: [PATCH] BZ#15711: Build syscall.h with -ffreestanding.
- References: <51D6B452 dot 30401 at redhat dot com> <mvm38rmuaxl dot fsf at hawking dot suse dot de> <51DD6FEA dot 7010707 at redhat dot com>
On 07/10/2013 10:30 AM, Carlos O'Donell wrote:
> On 07/10/2013 03:32 AM, Andreas Schwab wrote:
>> "Carlos O'Donell" <carlos@redhat.com> writes:
>>
>>> The loop is caused by a auto-generated prerequisite between
>>> /usr/include/stdc-predef.h and $BUILD/misc/bits/syscall.d.
>>
>> Why isn't the compiler seeing include/stdc-predef.h first?
The only headers included are $(sysincludes).
So the only headers the compiler searches are:
#include "..." search starts here:
#include <...> search starts here:
/usr/lib/gcc/x86_64-redhat-linux/4.7.2/include
/home/carlos/install-linux/include
End of search list.
This means the build never sees the internal
include/stdc-predef.h.
Is there any reason to want to add more internal include
paths as opposed to just using -ffreestanding.
The latter makes the most sense to me when generating
a header that effectively has no external dependencies.
Is that sufficient justification to use -ffreestanding?
Cheers,
Carlos.