From: "H. J. Lu" <hjl@lucon.org>
To: GDB <gdb-patches@sources.redhat.com>
Subject: Re: PATCH: Make sure gdb-cfg.texi is created
Date: Fri, 09 May 2003 20:35:00 -0000 [thread overview]
Message-ID: <20030509133511.A6844@lucon.org> (raw)
In-Reply-To: <20030509201835.GA27906@nevyn.them.org>; from drow@mvista.com on Fri, May 09, 2003 at 04:18:35PM -0400
[-- Attachment #1: Type: text/plain, Size: 398 bytes --]
On Fri, May 09, 2003 at 04:18:35PM -0400, Daniel Jacobowitz wrote:
> Maybe I'm missing something obvious. The link will be created to point
> at /export/gnu/src/gdb/gdb/gdb/doc/all-cfg.texi. Whether
> ../../../../../import/gdb/src/gdb/doc/all-cfg.texi exists from that
> directory does not matter. It will be resolved from the directory
> containing the second symlink.
>
It is a typo.
H.J.
[-- Attachment #2: gdb-link.patch --]
[-- Type: text/plain, Size: 637 bytes --]
2003-05-09 H.J. Lu <hongjiu.lu@intel.com>
* Makefile.in (gdb-cfg.texi): Fix a typo.
--- gdb/doc/Makefile.in.link 2003-04-02 16:40:17.000000000 -0800
+++ gdb/doc/Makefile.in 2003-05-09 13:33:23.000000000 -0700
@@ -245,7 +245,7 @@ GDBvn.texi : ${gdbdir}/version.in
# not one for their binary config---which may not be specifically
# defined anyways).
gdb-cfg.texi: ${srcdir}/${DOC_CONFIG}-cfg.texi
- (test "$$LN_S" = "ln -s" && \
+ (test "$(LN_S)" = "ln -s" && \
ln -s ${srcdir}/${DOC_CONFIG}-cfg.texi gdb-cfg.texi) || \
ln ${srcdir}/${DOC_CONFIG}-cfg.texi gdb-cfg.texi || \
cp ${srcdir}/${DOC_CONFIG}-cfg.texi gdb-cfg.texi
next prev parent reply other threads:[~2003-05-09 20:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 19:24 H. J. Lu
2003-05-09 19:34 ` Daniel Jacobowitz
2003-05-09 19:59 ` H. J. Lu
2003-05-09 20:06 ` Daniel Jacobowitz
2003-05-09 20:10 ` H. J. Lu
2003-05-09 20:18 ` Daniel Jacobowitz
2003-05-09 20:35 ` H. J. Lu [this message]
2003-05-09 20:42 ` Daniel Jacobowitz
2003-05-10 9:49 ` Eli Zaretskii
2003-05-10 15:39 ` Andreas Schwab
2003-05-10 17:57 ` Eli Zaretskii
2003-05-10 19:00 ` Andreas Schwab
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=20030509133511.A6844@lucon.org \
--to=hjl@lucon.org \
--cc=gdb-patches@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