Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@elta.co.il>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [cplus] Add an entry point for cp-names
Date: Tue, 10 Feb 2004 06:36:00 -0000	[thread overview]
Message-ID: <uk72vzbic.fsf@elta.co.il> (raw)
In-Reply-To: <20040209203434.GA12280@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 9 Feb 2004 15:34:34 -0500)

> Date: Mon, 9 Feb 2004 15:34:34 -0500
> From: Daniel Jacobowitz <drow@mvista.com>
> 
> > Actually, there's more to this: cp-names_tab.c and cp-names-main_tab.c
> > map to the same 8+3 DOS name, so they will break the script in
> > gdb/config/djgpp/djconfig.sh which accounts for renaming of *.tab.c
> > files (see config.sed for the gory details).  Thus, please consider
> > some other name for cp-names-main.tab.c, one that doesn't conflict
> > with cp-names.tab.c.
> 
> I don't think any of that code is live in this case.  It looks for
> [yp*].tab.c and cp-names.tab.c won't match that.

That just means that the problem is slightly more complicated than I
remembered.

> I really don't want to dig my hands into a 43-line sed script
> editing another sed expression when I can't test it, so I'm afraid I
> will have to leave this to someone with DJGPP installed.

Oh, come on!  Just changing [yp*] to [yps*] is all we need.  That, and
renaming one of the two object files produced from cp-names.tab.c, to
avoid file-name clashes.


  reply	other threads:[~2004-02-10  6:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-24 22:36 Daniel Jacobowitz
2004-01-04  6:16 ` Eli Zaretskii
2004-02-09 20:34   ` Daniel Jacobowitz
2004-02-10  6:36     ` Eli Zaretskii [this message]
2004-02-29 17:25       ` Daniel Jacobowitz
2004-02-29 18:05         ` Eli Zaretskii

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=uk72vzbic.fsf@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=drow@mvista.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