This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: A question about newlib/libc/include/newlib.h.

From: Jeff Johnston <jjohnstn at redhat dot com>
To: Kazu Hirata <kazu at codesourcery dot com>
Cc: newlib at sources dot redhat dot com
Date: Mon, 11 Dec 2006 14:28:57 -0500
Subject: Re: A question about newlib/libc/include/newlib.h.
References: <200612111655.kBBGtuMp003622@sparrowhawk.codesourcery.com>

Kazu Hirata wrote:

Hi Jeff,

I see:

2002-08-28 Jeff Johnston <jjohnstn@redhat.com>
        * libc/include/newlib.h: New file for tools that use newlib
        headers but don't build newlib first (e.g. gcc).
Is this needed when you do one-tree build?

Yes, but I think you also can keep them split and tell gcc where the headers are (IIRC using the --with-headers option).

I'm wondering about the necessity because this file gets included
while running newlib testsuite when I really want a testcase to
include the installed version of newlib.h (with lots of #defines in
it).

That is a bug that will require looking into.

Thanks,

Kazu Hirata

Regards,

-- Jeff J.

References:
- A question about newlib/libc/include/newlib.h.
  - From: Kazu Hirata

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]