From: Ian Lance Taylor <ian@zembu.com>
To: John.Barry@eso.org
Cc: binutils@sourceware.cygnus.com
Subject: Re: strange compile problem
Date: Mon, 13 Sep 1999 11:23:00 -0000 [thread overview]
Message-ID: <19990913182314.30277.qmail@daffy.airs.com> (raw)
In-Reply-To: <199909131713.TAA13159@osc1.hq.eso.org>
From: John Barry <jbarry@eso.org>
Date: Mon, 13 Sep 1999 19:13:03 +0200 (MET DST)
I was trying to compile binutils-2.9.5.0.12, which I found on va-research's
ftp site, it gives me the same kind of problems with the latest snap from
cygnus too. Though while I'm on the subject I get a problem building
bfd/libbfd.c it always fails with this error:
../../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)?
Which I figure is because 2.9.1, et all aren't fully 64bit file system
compliant, (or Solaris 2.6 isn't :) I get around it by removing
-D_FILE_OFFSET_BITS=64 from the compile flags, and leaving -D_LARGEFILE64_SOURCE=1
in, seems to work, though a patch would be very welcome :)
I don't know what has to change in the binutils for them to become
64bit file compliant. I don't really know why anything has to
change.
> To check that, run the above command with the --save-temps option, and
> take a look at the resulting assembler file. Send it in here if you
> want to, or better yet just send the lines that the assembler is
> complaining about.
Here you go :)
-c --save-temps ../../binutils-2.9.5.0.12/gprof/hist.c
hist.s:1963: Error: Illegal operands [fbule,a,pn %fcc3, .LL310]
hist.s:1986: Error: Illegal operands [fbule,a,pn %fcc3, .LL256]
hist.s:2008: Error: Illegal operands [fbule,a,pn %fcc3, .LL311]
hist.s:2100: Error: Illegal operands [fbule,a,pn %fcc3, .LL316]
Thanks. The current development sources do assemble these
instructions correctly when using the -Av9 option.
Ian
next prev parent reply other threads:[~1999-09-13 11:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-13 10:14 John Barry
1999-09-13 11:23 ` Ian Lance Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-13 11:50 John Barry
1999-09-13 11:58 ` Ian Lance Taylor
1999-09-13 12:39 ` Roland McGrath
1999-09-13 12:53 ` Roland McGrath
1999-09-13 13:13 ` John Barry
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=19990913182314.30277.qmail@daffy.airs.com \
--to=ian@zembu.com \
--cc=John.Barry@eso.org \
--cc=binutils@sourceware.cygnus.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).