From: Kai Ruottu <kai.ruottu@wippies.com>
To: gowrisankar loganathan <lgowris@hotmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Help needed to buid GCC for NEC V850
Date: Tue, 17 Mar 2009 14:38:00 -0000 [thread overview]
Message-ID: <49BFB6BC.5020106@wippies.com> (raw)
In-Reply-To: <SNT102-W743D79D911CCC9E179CAB9B4980@phx.gbl>
gowrisankar loganathan wrote:
> I have Mingw in the same PC which compiles all programes corrrectly.
What on earth this note has to do with this build problem?
You configured the GCC for Cygwin $host, not for MinGW $host
('i686-mingw32'). So you MUST have the Cygwin GCC as the 'gcc'
which compiles the GCC sources !
>> The 'gcc' in your log is the Cygwin GCC ! So it uses its own "Cygwin
>> target headers" when compiling something for Cygwin :
>>
>>>>> gcc -c -DHAVE_CONFIG_H -g -O2 -I.
>>>>> -I../../Gcc_Source/gcc-4.3.3/libiberty/../include
>> But other headers could be required additionally...
>>
>> So the 'fcntl.h' should be in your Cygwin target headers in
>> '/usr/include' or something !
Very simply: If you want the 'v850-elf' target GCC for the
Cygwin $host, then use the Cygwin target GCC with its headers
and libraries! If you want the 'v850-elf' target GCC for the
MinGW $host, then please use the MinGW target GCC with its
headers and libraries! And in this MinGW case also use the
'--host=i686-mingw32' when configuring the GCC...
next prev parent reply other threads:[~2009-03-17 14:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 12:20 gowrisankar loganathan
2009-03-16 14:25 ` Kai Ruottu
2009-03-16 14:59 ` gowrisankar loganathan
2009-03-16 15:18 ` Kai Ruottu
2009-03-17 9:26 ` gowrisankar loganathan
2009-03-17 14:38 ` Kai Ruottu [this message]
2009-03-19 15:50 ` Gcc for V850 gowrisankar loganathan
2009-03-19 22:08 ` Jeff Law
2009-03-19 23:23 ` Ian Lance Taylor
2009-03-20 9:06 ` gowrisankar loganathan
2009-03-20 10:23 ` Kai Ruottu
2009-03-20 14:09 ` Ian Lance Taylor
2009-03-20 10:45 ` gowrisankar loganathan
2009-03-20 14:38 ` Ian Lance Taylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49BFB6BC.5020106@wippies.com \
--to=kai.ruottu@wippies.com \
--cc=gcc-help@gcc.gnu.org \
--cc=lgowris@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).