Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gcc@gcc.gnu.org, gdb@sources.redhat.com
Subject: HPUX `make'
Date: Sat, 02 Nov 2002 11:20:00 -0000	[thread overview]
Message-ID: <20021102192116.GA2044@nevyn.them.org> (raw)

Joel, you said you'd built GDB 5.3 on HP/UX recently, right?  Were you using
GNU tools?


I just tried to build GDB on an HP/UX (11i I think) system for the first
time.  It appears that /usr/bin/make can't handle at least two things in the
makefiles: $(VAR): targets, and "-include".  I ended up having to build GNU make.

I didn't get terribly far after that, either.  I'm using the installed
compiler, which I believe is the ANSI rather than bundled one; at least the
documentation says so and -Aa / -Ae work.  With cc:
cc: "../../gdb/intl/gettextP.h", line 49: error 1000: Unexpected symbol: "nls_uint32".
cc: "../../gdb/intl/gettextP.h", line 50: error 1584: Inconsistent type declaration: "SWAP".

Some limitation in the accepted syntax for "inline", I think.

I reconfigured forcing -Aa, and it did a little better, but bombed out in
libiberty not knowing how big a 'struct stat' was; some definition not
getting picked up...

I restarted using "cc -Aa -D_HPUX_SOURCE", based on a vague memory from this
list, and got much further; it went until <sys/core.h> is included in BFD. 
That file apparently requires -Ae.  Similar problems in GDB, which uses long
long.  So I ran "make CC='cc -Ae -D_HPUX_SOURCE', after configuring with
-Aa, and then I got out a working GDB binary.

So: how should one configure on this system to use the native tools, and can
we document it?  Any idea why configuring with -Ae didn't work?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


             reply	other threads:[~2002-11-02 19:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-02 11:20 Daniel Jacobowitz [this message]
2002-11-02 11:44 ` Andrew Cagney
2002-11-02 16:29 ` Joel Brobecker
2002-11-02 14:11 John David Anglin

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=20021102192116.GA2044@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@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