From: Andrew Cagney <ac131313@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: insight@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: [rfa/toplevel] Conditionalize GDB_TK
Date: Fri, 03 Jan 2003 19:23:00 -0000 [thread overview]
Message-ID: <3E15E32C.2050405@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 322 bytes --]
Hello,
The attatched only adds the tk directories to the gdb dependency list
when the corresponding tk files are present. That way `all-gdb' doesn't
build tk files (except when needed).
ok?
Andrew
PS: Disclaimer, I cut/paste the configure changes. Perhaphs someone
able to regenerate configure should commit this?
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 2369 bytes --]
2003-01-03 Andrew Cagney <ac131313@redhat.com>
* configure.in (GDB_TK): Add tcl directories conditional on
gdb/gdbtk directory being present.
* configure: Regenerate.
Index: configure
===================================================================
RCS file: /cvs/src/src/configure,v
retrieving revision 1.40
diff -u -r1.40 configure
--- configure 31 Dec 2002 18:00:11 -0000 1.40
+++ configure 3 Jan 2003 17:48:45 -0000
@@ -2334,11 +2334,23 @@
# so we should be able to put the 'maybe's in unconditionally and
# leave out the maybe dependencies when enable_gdbtk is false. I'm not
# 100% sure that that's safe though.
+
+gdb_tk="maybe-all-tcl maybe-all-tk maybe-all-itcl maybe-all-tix maybe-all-libgui"
case "$enable_gdbtk" in
no)
GDB_TK="" ;;
+ yes)
+ GDB_TK="${gdb_tk}" ;;
*)
- GDB_TK="maybe-all-tcl maybe-all-tk maybe-all-itcl maybe-all-tix maybe-all-libgui" ;;
+ # Only add the dependency on gdbtk when GDBtk is part of the gdb
+ # distro. Eventually someone will fix this and move Insight, nee
+ # gdbtk to a separate directory.
+ if test -d ${srcdir}/gdb/gdbtk ; then
+ GDB_TK="${gdb_tk}"
+ else
+ GDB_TK=""
+ fi
+ ;;
esac
# Create the 'maybe dependencies'. This uses a temporary file.
Index: configure.in
===================================================================
RCS file: /cvs/src/src/configure.in,v
retrieving revision 1.137
diff -u -r1.137 configure.in
--- configure.in 31 Dec 2002 18:00:11 -0000 1.137
+++ configure.in 3 Jan 2003 17:48:45 -0000
@@ -1677,11 +1677,23 @@
# so we should be able to put the 'maybe's in unconditionally and
# leave out the maybe dependencies when enable_gdbtk is false. I'm not
# 100% sure that that's safe though.
+
+gdb_tk="maybe-all-tcl maybe-all-tk maybe-all-itcl maybe-all-tix maybe-all-libgui"
case "$enable_gdbtk" in
no)
GDB_TK="" ;;
+ yes)
+ GDB_TK="${gdb_tk}" ;;
*)
- GDB_TK="maybe-all-tcl maybe-all-tk maybe-all-itcl maybe-all-tix maybe-all-libgui" ;;
+ # Only add the dependency on gdbtk when GDBtk is part of the gdb
+ # distro. Eventually someone will fix this and move Insight, nee
+ # gdbtk to a separate directory.
+ if test -d ${srcdir}/gdb/gdbtk ; then
+ GDB_TK="${gdb_tk}"
+ else
+ GDB_TK=""
+ fi
+ ;;
esac
# Create the 'maybe dependencies'. This uses a temporary file.
next reply other threads:[~2003-01-03 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 19:23 Andrew Cagney [this message]
2003-01-03 19:46 ` DJ Delorie
2003-01-06 18:38 ` Andrew Cagney
2003-01-04 0:45 ` Michael Snyder
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=3E15E32C.2050405@redhat.com \
--to=ac131313@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=insight@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).