From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: dave@hiauly1.hia.nrc.ca (John David Anglin)
Cc: drow@false.org, gdb@sourceware.org, dave.anglin@nrc-cnrc.gc.ca,
brobecker@adacore.com, kettenis@gnu.org
Subject: Re: Likely obsolete pieces of GDB
Date: Mon, 18 Dec 2006 03:03:00 -0000 [thread overview]
Message-ID: <200612180241.kBI2fehd007870@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <200612170123.kBH1NfVF025104@hiauly1.hia.nrc.ca> from "John David Anglin" at Dec 16, 2006 08:23:40 pm
> I have built 6.5 on HP-UX 10.20. I will report back on the current
> status of the cvs source.
The current cvs still builds on HP-UX 10.20. I used GCC 4.1.1. The
system has a complete HP patch set. I had the cma hack applied to
configure to disable thread support. The only minor problem was I
had to define CPPFLAGS as follows prior to running configure:
export CPPFLAGS="-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE"
If I don't do this, there's a declaration conflict for fseeko and
fseeko64. Without these defines, configure doesn't find the routines
in <stdio.h>. However, the defines are used during the build and this
a conflict occurs with gdb's internal declaration of these two routines.
The define for _LARGEFILE_SOURCE may be implicit. _LARGEFILE64_SOURCE
is definitely by gdb.
I think the same issue is present under HP-UX 11.
The testsuite is running...
I'll check building without the cma hack.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
next prev parent reply other threads:[~2006-12-18 3:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 20:59 Daniel Jacobowitz
2006-12-16 21:23 ` Christopher Faylor
2007-02-10 21:42 ` Pedro Alves
2007-02-10 23:50 ` Daniel Jacobowitz
2007-02-19 1:25 ` Pedro Alves
2006-12-17 1:24 ` John David Anglin
2006-12-17 11:46 ` Mark Kettenis
2007-01-01 16:34 ` Daniel Jacobowitz
2006-12-18 3:03 ` John David Anglin [this message]
2006-12-18 3:43 ` John David Anglin
2006-12-20 16:07 ` John David Anglin
2006-12-20 17:41 ` John David Anglin
2007-01-01 16:33 ` Daniel Jacobowitz
2007-01-01 16:47 ` John David Anglin
2007-01-01 17:10 ` Mark Kettenis
2007-01-01 17:20 ` John David Anglin
2006-12-17 1:36 ` Russell Shaw
2006-12-17 12:20 ` Mark Kettenis
2006-12-17 14:26 ` Stephen & Linda Smith
2006-12-17 15:37 ` Daniel Jacobowitz
2006-12-20 6:01 ` Joel Brobecker
2006-12-17 13:40 ` Joel Brobecker
2007-01-01 16:46 ` Daniel Jacobowitz
2007-01-01 16:58 ` Mark Kettenis
2007-01-03 23:55 ` Jim Blandy
2007-02-10 20:50 ` Daniel Jacobowitz
2007-02-12 17:35 ` Joel Brobecker
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=200612180241.kBI2fehd007870@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=brobecker@adacore.com \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=kettenis@gnu.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