This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Fwd: Re: Time for a HP/PA hackathon?]


First fallout from 64-bit off_t, it appears that HP/UX 11.xx build needs --D_LARGEFILE64_SOURCE. Any suggestions on how to "correctly" do this?

Andrew

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


--- Begin Message ---
> What happens if -D_LARGEFILE64_SOURCE is added?  (Not sure of the 
> correct way to do that in BFD though).

"./gdb ./gdb" ; "break main" ; "run" works.

And it works with gdb built with gcc 3.3.2, ansi c B11.11,
and aC++ A.03.45.

I do think you're opening up a big can of worms shortly before
the 6.1 branch though.

Michael C


--- End Message ---

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]