From: Daniel Jacobowitz <drow@mvista.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: gdb.asm/asm-source.exp creation of arch.inc doesn't work for relative ${srcdir}
Date: Fri, 19 Apr 2002 09:18:00 -0000 [thread overview]
Message-ID: <20020419121828.A24685@nevyn.them.org> (raw)
In-Reply-To: <15552.16512.955981.455419@localhost.redhat.com>
On Fri, Apr 19, 2002 at 12:06:24PM -0400, Elena Zannoni wrote:
> Daniel Jacobowitz writes:
> > On Tue, Apr 16, 2002 at 10:31:32AM -0400, Elena Zannoni wrote:
>
> > >
> > > -set insn_file ${srcdir}/${subdir}/${asm-arch}.inc
> > > -remote_exec build "rm -f ${objdir}/${subdir}/arch.inc"
> >
> > Please don't delete this line. If you remote_download onto a dangling
> > symlink, you get an error. I don't know what happens if you remote
> > download onto a normal symlink, but it runs a risk of clobbering
> > something in ${srcdir}.
> >
>
> Actually there would be no symlink at all after this patch.
> But I'll leave the line in anyway, just in case.
Thanks. There will be no symlink unless you're using an object
directory that predates the patch, which I was when I tried it.
> This is what I checked in:
>
> 2002-04-19 Elena Zannoni <ezannoni@redhat.com>
>
> * gdb.asm/asm-source.exp: Don't use a symlink, just copy the
> instruction file directly into the build tree. Clean up at end of
> test.
Thanks!
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-04-19 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-15 22:11 Daniel Jacobowitz
2002-04-16 7:31 ` Elena Zannoni
2002-04-16 9:56 ` Daniel Jacobowitz
2002-04-18 18:16 ` Michael Snyder
2002-04-19 9:06 ` Elena Zannoni
2002-04-19 9:18 ` Daniel Jacobowitz [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=20020419121828.A24685@nevyn.them.org \
--to=drow@mvista.com \
--cc=ezannoni@redhat.com \
--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