From: Alan Modra <amodra@bigpond.net.au>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: binutils@sources.redhat.com
Subject: libiberty.h
Date: Tue, 12 Apr 2005 01:21:00 -0000 [thread overview]
Message-ID: <20050412012121.GA3321@bubble.modra.org> (raw)
This change
2005-04-11 Kaveh R. Ghazi <ghazi@caip.rutgers.edu>
* libiberty.h (fopen_unlocked, fdopen_unlocked, freopen_unlocked):
Provide prototypes for new functions.
causes
gcc -DHAVE_CONFIG_H -I. -I/src/binutils-current/opcodes -I. -D_GNU_SOURCE -I. -I/src/binutils-current/opcodes -I../bfd -I/src/binutils-current/opcodes/../include -I/src/binutils-current/opcodes/../bfd -I/src/binutils-current/opcodes/../intl -I../intl -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O -c /src/binutils-current/opcodes/m88k-dis.c -o m88k-dis.o
In file included from /src/binutils-current/opcodes/m88k-dis.c:27:
/src/binutils-current/opcodes/../include/libiberty.h:55: error: parse error before numeric constant
/src/binutils-current/opcodes/../include/libiberty.h:55: warning: function declaration isn't a prototype
/src/binutils-current/opcodes/../include/libiberty.h:56: error: parse error before numeric constant
/src/binutils-current/opcodes/../include/libiberty.h:56: warning: function declaration isn't a prototype
/src/binutils-current/opcodes/../include/libiberty.h:57: error: parse error before numeric constant
/src/binutils-current/opcodes/../include/libiberty.h:57: warning: function declaration isn't a prototype
Preprocessing shows
extern FILE *fopen_unlocked (const char *path, const char *31);
extern FILE *fdopen_unlocked (int fildes, const char *31);
extern FILE *freopen_unlocked (const char *path, const char *31, FILE *stream);
Please remove the needless parameter names.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next reply other threads:[~2005-04-12 1:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 1:21 Alan Modra [this message]
2005-04-13 23:57 ` Remove parameter names from libiberty.h Kaveh R. Ghazi
2005-04-14 1:13 ` Ian Lance Taylor
2005-04-14 7:42 ` Thorsten Glaser
2005-04-14 12:41 ` DJ Delorie
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=20050412012121.GA3321@bubble.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=ghazi@caip.rutgers.edu \
/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).