From: Andreas Schwab <schwab@suse.de>
To: libc-hacker@sources.redhat.com
Subject: glob.h syntax errors
Date: Thu, 16 Sep 2004 23:30:00 -0000 [thread overview]
Message-ID: <je8yb994hi.fsf@sykes.suse.de> (raw)
When <glob.h> is included as the first header it produces lots of syntax
errors:
$ echo '#include <glob.h>' | gcc -c -xc - -o /dev/null
In file included from <stdin>:1:
/usr/include/glob.h:177: error: parse error before "__THROW"
/usr/include/glob.h:180: error: parse error before "__THROW"
$ echo '#include <glob.h>' | gcc -c -xc - -o /dev/null -D_LARGEFILE64_SOURCE
In file included from <stdin>:1:
/usr/include/glob.h:177: error: parse error before "__THROW"
/usr/include/glob.h:180: error: parse error before "__THROW"
/usr/include/glob.h:193: error: parse error before "__THROW"
/usr/include/glob.h:195: error: parse error before "__THROW"
$ echo '#include <glob.h>' | gcc -c -xc - -o /dev/null -D_FILE_OFFSET_BITS=64
In file included from <stdin>:1:
/usr/include/glob.h:182: error: parse error before '(' token
/usr/include/glob.h:184: error: `__REDIRECT_NTH' declared as function returning a function
/usr/include/glob.h:185: error: `glob_t' redeclared as different kind of symbol
/usr/include/glob.h:129: error: previous declaration of `glob_t'
/usr/include/glob.h:185: error: parse error before '*' token
/usr/include/glob.h:187: error: parse error before '(' token
/usr/include/glob.h:187: error: conflicting types for `__REDIRECT_NTH'
/usr/include/glob.h:184: error: previous declaration of `__REDIRECT_NTH'
/usr/include/glob.h:187: error: parse error before ')' token
Shouldn't it include <sys/cdefs.h>?
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next reply other threads:[~2004-09-16 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 23:30 Andreas Schwab [this message]
2004-09-16 23:43 ` Roland McGrath
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=je8yb994hi.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=libc-hacker@sources.redhat.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).