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: Mon, 16 Mar 2009 14:25:00 -0000 [thread overview]
Message-ID: <49BE6207.9090401@wippies.com> (raw)
In-Reply-To: <SNT102-W785CBEFA2FEF340580C357B49B0@phx.gbl>
gowrisankar loganathan wrote:
> $ make
>
> now I got the error as
>
> gcc -c -DHAVE_CONFIG_H -g -O2 -I. -I../../Gcc_Source/gcc-4.3.3/libiberty/../incl
> ude -W -Wall -Wwrite-strings -Wstrict-prototypes -pedantic ../../Gcc_Source/gc
> c-4.3.3/libiberty/pex-unix.c -o pex-unix.o
<snip>
> ./../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c: In function `pex_unix_fdopenw':
> ./../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: warning: implicit declarati
> on of function `fcntl'
> ./../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: error: `F_SETFD' undeclared
> (first use in this function)
> ./../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: error: (Each undeclared ide
> ntifier is reported only once
> ./../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: error: for each function it
> appears in.)
> ./../Gcc_Source/gcc-4.3.3/libiberty/pex-unix.c:518: error: `FD_CLOEXEC' undecla
> red (first use in this function)
>
> Can any one help me to fix the issue.
Just look in which standard C headers for Cygwin these are now
declared, if in any... Then why this headers wasn't seen in the
libiberty/configure. The '$build/libiberty/config.log' should
give some hint...
My old Cygwin toolchain had these in 'sys/fcntl.h'...
next prev parent reply other threads:[~2009-03-16 14:25 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 [this message]
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
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=49BE6207.9090401@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).