Mail Archives: cygwin/2001/02/19/12:42:06
1st question: if you are trying to build from the standard source, rather
than the one from the cygwin mirror directories, why?
2nd question: are you sure that the target selected automatically was not
i686-pc-cygwin32? It may be better to specify the target so that it is
identical to the host. If your --host and --target do not match exactly,
you are doing a cross build, which requires a copy of the include files to
be present in the appropriate target build directory.
3rd question: (depending on your answer to #2) did you remember to copy
/usr/include to /usr/local/i686-gcc/i686-pc-cygwin32/include (if that
corresponds to the selected target) before running configure? That should
postpone problems finding <windows.h> until the libf2c build, where you
really should be using the cygwin copy of the sources, even if you choose
the standard gcc-2.95.2 or 2.95.3 . The keepers of gcc-2.95.3 have declined
the suggestion that libf2c should correspond with any version of cygwin
other than -b20.
----- Original Message -----
From: "Blythe.Stephen" <Stephen DOT Blythe AT IGT DOT com>
To: "'Cygwin Mailing List'" <cygwin AT cygwin DOT com>
Sent: Monday, February 19, 2001 8:50 AM
Subject: Problems building gcc-2.95.2
>
> Hi,
>
> I have been trying to compile gcc-2.95.2 to act as a native compiler on a
> cygwin system. (My eventual aim is to compile it to act as a
> cygwin->m68k-coff cross compiler, but I decided to try to compile it as a
> native first, thinking it might be easier.)
>
> This is my config script, which I am running in a separate folder from the
> sources:
> #!/bin/bash
>
../gcc-2.95.2/configure --prefix=/usr/local/i686-gcc --enable-languages=c++
>
> It (correctly, I think) recognises the host (and target) as i686-pc-cygwin
> and all seems to configure OK, but when I "make bootstrap" it, it fails,
> because it can't find "windows.h".
> It compile a lot of other files OK, so I guess it finds all the rest of
the
> header files OK, it just doesn't like this one.
> The file is present in /usr/include/w32api, but the compiler doesn't seem
to
> be looking in here for it.
> Can anyone help? I'm guessing someone has successfully done this.
>
> I hope this is sufficiently on-topic (i.e. cygwin specific) not to annoy
> everyone on here, and I have tried searching the archives (and various GCC
> and cross-GCC FAQs) already, but with no luck.
>
> Stephen Blythe
>
>
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
>
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
- Raw text -