From: Ojasi <ojasi_kul@yahoo.com>
To: gcc-help@gcc.gnu.org
Subject: parse error before "size_t"
Date: Thu, 18 Sep 2003 13:16:00 -0000 [thread overview]
Message-ID: <20030918131619.67403.qmail@web8007.mail.in.yahoo.com> (raw)
Hello,
After compiling my small test program ie.
gcc -I/home/dummy/linux/include test1.c -o test1
I am getting following errors.
In file included from /usr/include/_G_config.h:44,
from /usr/include/libio.h:32,
from /usr/include/stdio.h:72,
from test1.c:2:
/usr/include/gconv.h:72: parse error before "size_t"
/usr/include/gconv.h:88: parse error before "size_t"
/usr/include/gconv.h:97: parse error before "size_t"
/usr/include/gconv.h:174: parse error before "size_t"
/usr/include/gconv.h:177: parse error before '}' token
In file included from /usr/include/libio.h:32,
from /usr/include/stdio.h:72,
from test1.c:2:
/usr/include/_G_config.h:47: field `__cd' has
incomplete type
/usr/include/_G_config.h:50: field `__cd' has
incomplete type
In file included from /usr/include/stdio.h:72,
from test1.c:2:
/usr/include/libio.h:350: parse error before "size_t"
/usr/include/libio.h:359: parse error before "size_t"
/usr/include/libio.h:467: parse error before
"_IO_sgetn"
/usr/include/libio.h:467: parse error before "size_t"
(I have to add include path -I/home... because on my
machine I have two linux kernels, one patched 2.4.18
in my dummy directory and 2.4.20 the origianl one. I
want to use patched 2.4.18)
How should I compile my program to avoid these errors.
Thanks,
Ojasi
________________________________________________________________________
Yahoo! India Matrimony: Find your partner online.
Go to http://yahoo.shaadi.com
next reply other threads:[~2003-09-18 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 13:16 Ojasi [this message]
2003-09-18 17:17 lrtaylor
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=20030918131619.67403.qmail@web8007.mail.in.yahoo.com \
--to=ojasi_kul@yahoo.com \
--cc=gcc-help@gcc.gnu.org \
/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).