From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: Time for a HP/PA hackathon?
Date: Fri, 13 Feb 2004 22:39:00 -0000 [thread overview]
Message-ID: <20040213223905.DBA604B104@berman.michael-chastain.com> (raw)
The problem is somewhere between 2004-02-11 22:00:00 UTC and 2004-02-11
23:30:00 UTC. That puts it in the BFD real_ftell/real_fseek changes.
I suspect that it's something like "ftello64" getting picked up by
the autoconf test which is looking in the library, but no prototype
is actually in scope, so the return value defaults to "int" and
some bits are getting lost.
Aha, look at this!
gcc -DHAVE_CONFIG_H -I. -I/house/chastain/gdb/s1/bfd -I. -D_GNU_SOURCE -DHOST_HPPAHPUX -DHPUX_CORE -I. -I/house/chastain/gdb/s1/bfd -I/house/chastain/gdb/s1/bfd/../include -I/house/chastain/gdb/s1/bfd/../intl -I../intl -W -Wall -Wstrict-prototypes -Wmissing-prototypes -g -O2 -c /house/chastain/gdb/s1/bfd/bfdio.c -o bfdio.o
/house/chastain/gdb/s1/bfd/bfdio.c: In function `real_ftell':
/house/chastain/gdb/s1/bfd/bfdio.c:45: warning: implicit declaration of function `ftello64'
/house/chastain/gdb/s1/bfd/bfdio.c: In function `real_fseek':
/house/chastain/gdb/s1/bfd/bfdio.c:57: warning: implicit declaration of function `fseeko64'
Michael C
next reply other threads:[~2004-02-13 22:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 22:39 Michael Elizabeth Chastain [this message]
2004-02-14 2:01 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2004-02-14 20:00 Michael Elizabeth Chastain
2004-02-15 1:20 ` Daniel Jacobowitz
2004-02-14 3:14 Michael Elizabeth Chastain
2004-02-14 15:54 ` Andrew Cagney
2004-02-13 18:13 Michael Elizabeth Chastain
2004-02-13 18:32 ` Elena Zannoni
2004-02-13 18:48 ` Andrew Cagney
2004-02-13 16:29 Michael Elizabeth Chastain
2004-02-13 16:54 ` Andrew Cagney
2004-02-11 17:05 Andrew Cagney
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=20040213223905.DBA604B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@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