From: Wally Kramer <wally@steptech.com>
To: "'sourcenav@sources.redhat.com'" <sourcenav@sources.redhat.com>
Subject: building on HPUX
Date: Thu, 07 Mar 2002 14:55:00 -0000 [thread overview]
Message-ID: <26F9F6EAB586D411850700B0D049E6E410BDD5@shasta.pdx.steptech.com> (raw)
I'm having trouble building source navigator 5.0.0 on HP-UX11.11
9000/782/C240+ (PA-risc).
Someone apparently succeeded, because I downloaded and ran the executable
from
ftp://sourceware.cygnus.com/pub/sourcenav/releases/
I'm using gcc 3.0.4, gmake 3.79.1, etc.
Most modules compile (but with many warnings). Many components link okay:
fgrep grep dbcp dbimp dbdump
snavigator/parsers/assembly/ppc601-eabi/abrowser etc.
Problems:
tcl8.1: all files compile, but the link gives unresolved symbols for
TclpLoadFile and TclpUnloadFile. tclLoadNone.c is linked in, but this
module doesn't define these symbols. It *does* define a stub for
TclLoadFile (without the "p"). Is this correct?
tk8.1: error compiling source/tk8.1/unix/tkAppInit.c because it can't
include <X11/X.h> at tk8.1/generic/tk.h line 77. The comments indicate a
Mac hack.
Can anyone enlighten me? Do I need to tweak "configure"? Am I missing the
magic "set SNAV_HPUX_HACK = 1"?
reply other threads:[~2002-03-07 19:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=26F9F6EAB586D411850700B0D049E6E410BDD5@shasta.pdx.steptech.com \
--to=wally@steptech.com \
--cc=sourcenav@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).