From: Ian Lance Taylor <ian AT zembu (dot com)>
To: John.Barry AT eso (dot org)
Cc: binutils AT sourceware.cygnus (dot com)
Subject: Re: strange compile problem
Date: Mon, 13 Sep 1999 11:58:00 -0000 [thread overview]
Message-ID: <19990913185821.30628.qmail@daffy.airs.com> (raw)
In-Reply-To: <199909131849.UAA25046@osc1.hq.eso.org>
From: John Barry <jbarry@eso.org>
Date: Mon, 13 Sep 1999 20:49:34 +0200 (MET DST)
> ../../binutils-2.9.5.0.12/bfd/libbfd.c: In function `bfd_stat':
> ../../binutils-2.9.5.0.12/bfd/libbfd.c:638: argument `statbuf' doesn't match prototype
> ../../binutils-2.9.5.0.12/bfd/bfd.h:482: prototype declaration
>
> extern int bfd_stat PARAMS ((bfd *abfd, struct stat *));
>
> I don't see that with the current development sources. Do you see it
> with the snapshot from the Cygnus site, or just with 2.9.5.0.12 (which
> is a GNU/Linux specific release)?
I've been getting this with every version of binutils I've built up since I
started using -D_LARGEFILE64_SOURCE=1 -D_FILE_OFFSET_BITS=64, this includes
2.9.1 and every snapshop I've downloaded from cygnus. It's a Solaris only
issue, didn't happen when I built it on a hppa2.0 Visualise C 3000
You can probably fix it by adding
#include <sys/types.h>
#include <sys/stat.h>
near the top of bfd/bfd-in2.h.
I'm somewhat uncomfortable with requiring every program which includes
bfd.h to also include those files. Unfortunately, the only other
choice is probably to change the two uses of struct stat * to void *,
instead, and thus lose type checking.
Ian
next prev parent reply other threads:[~1999-09-13 11:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-13 11:50 John Barry
1999-09-13 11:58 ` Ian Lance Taylor [this message]
1999-09-13 12:39 ` Roland McGrath
1999-09-13 12:53 ` Roland McGrath
1999-09-13 13:13 ` John Barry
-- strict thread matches above, loose matches on Subject: below --
1999-09-13 10:14 John Barry
1999-09-13 11:23 ` Ian Lance Taylor
1999-09-13 6:54 John Barry
1999-09-13 9:12 ` 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=19990913185821.30628.qmail@daffy.airs.com \
--to=binutils@sourceware.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).