From: Andrew Cagney <ac131313@cygnus.com>
To: James Ingham <jingham@cygnus.com>
Cc: "Insight (GDB GUI)" <insight@sourceware.cygnus.com>,
GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: Re: RFC: More fixes to insights ln -s
Date: Sun, 26 Mar 2000 22:34:00 -0000 [thread overview]
Message-ID: <38DF009B.4AC2E2ED@cygnus.com> (raw)
In-Reply-To: <14543.54628.527337.770021@leda.cygnus.com>
James Ingham wrote:
>
> Andrew,
>
> I haven't really been paying that much attention to this configure
> stuff of late, sorry... But now that I think of it, I am pretty sure
> all these link machinations are wholly unnecessary. I munged the gdb
> startup code around so that gdb will find its library files from the
> build directory without using the link at all. Moreover, when you
> fail at making the link gdb will still work in GUI mode. So maybe we
> can just bag all this?
>
> However, it would be good to make sure that this is not some wierdness
> in my environment that makes it work. What about others? If you
> delete the gdbtcl link in your build directory, can you still run gdb
> in gui mode from the gdb build directory? If this is true for others
> as well, then we should just drop the extra complexity.
FYI,
I applied the attatched. I don't have the time to look at your
environment :-(
Andrew
Mon Mar 27 16:26:11 2000 Andrew Cagney <cagney@b1.cygnus.com>
* Makefile.in (all-gdbtk): Check for an existing link/directory.
Re-format warning message. Document that post 5.0 this can be
deleted.
Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/Makefile.in,v
retrieving revision 1.14
diff -p -r1.14 Makefile.in
*** Makefile.in 2000/03/20 20:38:22 1.14
--- Makefile.in 2000/03/27 06:29:37
*************** findvar.o: findvar.c $(defs_h) $(gdbcore
*** 1260,1274 ****
fork-child.o: fork-child.c gdb_wait.h $(defs_h) $(gdbcore_h) \
$(inferior_h) target.h terminal.h gdbthread.h gdb_string.h
all-gdbtk:
! if test "$(LN_S)" = "ln -s" -a ! -d gdbtcl/images ; then \
! echo linking ${srcdir}/gdbtk/library to gdbtcl ; \
! $(LN_S) ${srcdir}/gdbtk/library gdbtcl ; \
! else \
! echo Warning: Unable to link ${srcdir}/gdbtk/library to gdbtcl. ; \
! echo " " You will need to do a ; \
! echo " " make install before you are able to run the GUI. ; \
! fi
clean-gdbtk:
rm -f gdbtcl
--- 1260,1282 ----
fork-child.o: fork-child.c gdb_wait.h $(defs_h) $(gdbcore_h) \
$(inferior_h) target.h terminal.h gdbthread.h gdb_string.h
+ # FIXME: cagney/2000-03-27: Post 5.0 this link code can be removed.
+ # It should now be possible to run GDBtk from the build directory
+ # without the link in place.
all-gdbtk:
! @if test ! -d gdbtcl/images ; then \
! if test "$(LN_S)" = "ln -s" ; then \
! echo linking ${srcdir}/gdbtk/library to gdbtcl ; \
! rm -f gdbtcl ; \
! test ! -r gdbtcl || exit 1 ; \
! $(LN_S) ${srcdir}/gdbtk/library gdbtcl ; \
! else \
! echo "Warning:" ; \
! echo "Unable to link ${srcdir}/gdbtk/library to gdbtcl." ; \
! echo "You will need to do a \`make install' before you are" ; \
! echo "able to run the GUI." ; \
! fi ; \
! else true ; fi
clean-gdbtk:
rm -f gdbtcl
prev parent reply other threads:[~2000-03-26 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-14 23:13 Andrew Cagney
2000-03-15 10:21 ` James Ingham
2000-03-26 22:34 ` Andrew Cagney [this message]
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=38DF009B.4AC2E2ED@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=jingham@cygnus.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).