From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com
Subject: Re: building snapshot on hp-ux with hp tools
Date: Tue, 13 Jan 2004 15:43:00 -0000 [thread overview]
Message-ID: <40041214.6010803@gnu.org> (raw)
In-Reply-To: <20040113104006.5A84A4ACDA@berman.michael-chastain.com>
> I'm building gdb+dejagnu-20040113.tar.bz2 on hpux 11.11 using
> the hp-ux tools, and I'm running into two problems.
>
> (1) expect doesn't build with hp-ux make.
> When I use gnu make, it builds fine.
Does a more up-to-date expect build?
Per
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=1349
> Will need to merge in changes that get expect/ to link against
> ../tcl/unix/libtcl*.a instead of the installed tcl.
I've found nothing else (but those configury changes looked nasty :-().
> (2) dejagnu doesn't build because it doesn't find a C++ compiler
It doesn't actually need the C++ compiler - its an unnecessary test in
one of the subdirectories (examples?). A quick hack may pasify it :-)
> I can think of several ways around this:
>
> (A) Make snapshots with no expect+dejagnu, such as gdb-20040113.tar.bz2.
> Since our releases are like that, I think it's okay for our
> snapshots to be like that.
Historically expect and dejagnu have been bundled in with GDB to ensure
that all parties are using a consistent test framework. It might be
time to cut our losses?
> (B) Tell people who use snapshots to remove the expect and dejagnu
> subdirectories before building from source.
It's a workaround.
> (C) Upgrade dejagnu in sourceware (and upstream if necessary) to make
> the C++ compiler optional.
Yes, someone was looking at that? (BTW, upstream where?).
Andrew
next prev parent reply other threads:[~2004-01-13 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 10:39 Michael Elizabeth Chastain
2004-01-13 15:43 ` Andrew Cagney [this message]
2004-01-13 21:24 ` Daniel Jacobowitz
2004-01-13 22:59 Michael Elizabeth Chastain
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=40041214.6010803@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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