Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: GDB <gdb-patches@sources.redhat.com>
Subject: Re: PATCH: Make sure gdb-cfg.texi is created
Date: Fri, 09 May 2003 20:18:00 -0000	[thread overview]
Message-ID: <20030509201835.GA27906@nevyn.them.org> (raw)
In-Reply-To: <20030509131049.A6435@lucon.org>

On Fri, May 09, 2003 at 01:10:49PM -0700, H. J. Lu wrote:
> On Fri, May 09, 2003 at 04:06:43PM -0400, Daniel Jacobowitz wrote:
> > On Fri, May 09, 2003 at 12:59:43PM -0700, H. J. Lu wrote:
> > > 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
> > 
> > Sure, but then why would "ln" or "cp" work from "doesn't exist"?
> 
> I have a tree with relative symlinks. all-cfg.texi in the source tree
> is
> 
> # ls -l /export/gnu/src/gdb/gdb/gdb/doc/all-cfg.texi
> lrwxrwxrwx    1 hjl      hjl            50 May  9 09:58 /export/gnu/src/gdb/gdb/gdb/doc/all-cfg.texi -> ../../../../../import/gdb/src/gdb/doc/all-cfg.texi
> 
> Since my build dir != source dir,
> 
> ../../../../../import/gdb/src/gdb/doc/all-cfg.texi
> 
> doesn't exist in my build dir.

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.

Otherwise relative symlinks would never be useful.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-05-09 20:18 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 [this message]
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=20030509201835.GA27906@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=hjl@lucon.org \
    /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