RE: any help? problems of making cross-complier for v850-nec-elf on cygwin

["akihiro terui" <terui at ns dot cdex dot co dot jp>]

Hi there, Thanks to all
I downloaded new one(gcc-3.1) and made sure that the same phenomenon
happened.
I've straggled these days.
After all, I deleted one line of header file(include_next<limits.h>
statement in ${my-build-dir}/gcc/include/limits.h)
somehow, it successfully made gcc up!
I'm going to make sure with compiling some of programs for v850.
I hope it will work well. (^_^);

Regards
akihiro

P.S.
I modified like this. Any suggestions?

#ifdef _GCC_NEXT_LIMITS_H
//#include_next <limits.h>              /* recurse down to the real one */
#endif


-----Original Message-----
From: Yves Rutschle [mailto:y.rutschle@indigovision.com]
Sent: Thursday, July 04, 2002 7:59 PM
To: Aaron J. Grier; akihiro terui; ML:Crossgcc
Subject: Re: any help? problems of making cross-complier for v850-nec-elf on
cygwin


On Wed, Jul 03, 2002 at 10:07:20AM -0700, Aaron J. Grier wrote:
> notice the system include paths, one of them is
> /home/terui/gcc-3.0.4/newlib/libc/include
>
> normally this path does not exist.  but if you put a symlink to newlib
> inside gcc-3.0.4 that will fix it.
>
> I do not know why configure does not generate proper include pathnames,
> but I have used the symlink trick as a workaround.

Because somebody might want to build gcc targeting another
library than newlib. Glibc comes to mind for example.

Therefore it would be questionnable to tie gcc to a
particular C library. It is part of the normal build process
to provide gcc with the target library and header files.

(argueably, gcc's configure could find out that you have
newlib in the source tree and automatically use it, but then
those using Glibc would be jealous :-) ).

/Y


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com