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 linux-m68k dot org>
- 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 18:11:34 -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> <51E43A59 dot 60801 at redhat dot com> <87ehaza8cd dot fsf at igel dot home>
On 07/15/2013 04:14 PM, Andreas Schwab wrote:
> "Carlos O'Donell" <carlos@redhat.com> writes:
>
>> Is there any reason to want to add more internal include
>> paths as opposed to just using -ffreestanding.
>
> Adding -I../include should be enough.
Is there any reason to do that?
What's the downside of using -ffreestanding?
It seems like adding more includes can only slow
down the building of that file or get us into more
problems in the future.
What am I missing?
Cheers,
Carlos.