This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Building a cross-compiler for i586-pc-msdosdjgpp undergcc-2.95.1fails
- To: alex dot buell at tahallah dot demon dot co dot uk, egcs at egcs dot cygnus dot com
- Subject: Re: Building a cross-compiler for i586-pc-msdosdjgpp undergcc-2.95.1fails
- From: N8TM at aol dot com
- Date: Sun, 24 Oct 1999 10:33:45 EDT
In a message dated 10/24/99 6:02:35 AM Pacific Daylight Time,
alex.buell@tahallah.demon.co.uk writes:
> _muldi3
> ../../gcc-2.95.1/gcc/libgcc2.c:41: stdlib.h: No such file or directory
> ../../gcc-2.95.1/gcc/libgcc2.c:42: unistd.h: No such file or directory
I have this problem of not seeing the .h files when running under NT4 SP[35].
I don't have such a problem when running under W2K beta 3, provided that
--host and --target are configured correctly, with the include files present
in the expected locations. W95 has more severe problems with includes in the
libgcc2 build, where include files may be identified but not complete read.
Do I get the impression you are cross compiling from linux? I trust you have
checked Mumit Khan's site for any relevant advice. FWIW, when I see this
problem, I can patch over it by adding additional symlinks to make the .h
files show up either in /usr/include or in other directories on the search
path in effect at this point in the build. So it may well be an OS version
dependent problem.
Tim
tprince@computer.org