------- Additional Comments From joel at oarcorp dot com 2005-02-08 19:16
-------
Subject: Re: gnat tools not buildable cross
neroden at gcc dot gnu dot org wrote:
> ------- Additional Comments From neroden at gcc dot gnu dot org 2005-02-08
> 18:30 -------
>
>>Is a fix likely to get into 4.0?
>
> Yes, the hackish fix is in. I hope to get the cleaner fix in, but who knows.
>
>
>>FYI Once I am able to build, the next issue is that the Ada libraries
>>do not look into newlib's headers and do not have a way to let a
>>target add specific include directories. See gcc/config/t-rtems for
>>the OS specific newlib include directory we need. With that resolved,
>>I think it could build in a single pass.
>
> I wouldn't want to touch this until substantially more of the branch went in,
> so that's probably a 4.1 issue.
I need to get to test this first but I think the mistake in the
gcc/ada/Makefile.in is actually quite simple. It has this:
GNATLIBCFLAGS_FOR_C = $(GNATLIBCFLAGS) $(TARGET_LIBGCC2_CFLAGS)
-fexceptions \
-DIN_RTS
$(TARGET_LIBGCC2_CFLAGS) is not sufficient to find all the newlib
headers. But the gcc/Makefile.in also uses $(LIBGCC2_INCLUDES) which is
target specific when compiling libgcc2. LIBGCC2_INCLUDES is primarily
set by RTEMS, VxWorks, and Cygwin.
What do you think?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19489
