public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug build/9111] "Cannot use procfs in large file compilation environment"
       [not found] <20050906184801.9111.joel.wagler@utstar.com>
@ 2008-12-30 15:51 ` pedro at codesourcery dot com
  0 siblings, 0 replies; only message in thread
From: pedro at codesourcery dot com @ 2008-12-30 15:51 UTC (permalink / raw)
  To: gdb-prs


------- Additional Comments From pedro at codesourcery dot com  2008-12-30 15:51 -------
Yes, that's right.  A recent bfd change had forced large file support on 32-bit
solaris systems, and we had to explicitly disable it to keep GDB working.  See
PR9641.

It *may* be possible to support large file support by hacking around that 
sys/procfs.h check, and being careful to not rely on its affected structures:
that is, e.g., redefining the procfs structures in gdb/bfd always with
32-bit/kernel layout; or hardcoding the needed offsets in bfd, and perhaps
disabling largefile support when building procfs.c + explicitly using
transitional large file compilation environment there ...

See:
 http://opensolaris.org/jive/thread.jspa?threadID=76693
 http://lists.kde.org/?l=kde-solaris&m=110574609925934&w=2

I can't claim that it would be pretty, though...


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=9111

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2008-12-30 15:51 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20050906184801.9111.joel.wagler@utstar.com>
2008-12-30 15:51 ` [Bug build/9111] "Cannot use procfs in large file compilation environment" pedro at codesourcery dot com

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).