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 19:59:00 -0000 [thread overview]
Message-ID: <20030509125943.A6257@lucon.org> (raw)
In-Reply-To: <20030509193206.GA1189@nevyn.them.org>; from drow@mvista.com on Fri, May 09, 2003 at 03:32:06PM -0400
On Fri, May 09, 2003 at 03:32:06PM -0400, Daniel Jacobowitz wrote:
> On Fri, May 09, 2003 at 12:24:34PM -0700, H. J. Lu wrote:
> > My gdb source tree is created with relative symlinks. ln -s won't work
> > with them. Here is a patch to make sure gdb-cfg.texi is created.
>
> That patch doesn't make sense. You're saying that ln -s can succeed
> when test -e would fail?
>
I got
# bash
# ln -s "doesn't exist" foo || echo bad
# test -e foo || echo "doesn't exist"
doesn't exist
H.J.
next prev parent reply other threads:[~2003-05-09 19:59 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 [this message]
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
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=20030509125943.A6257@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