Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: RFC: Use program_transform_name correctly
Date: Tue, 07 Oct 2003 21:42:00 -0000	[thread overview]
Message-ID: <vt265j0hgj4.fsf@zenia.home> (raw)


It seems as if some Makefiles aren't properly using
program_transform_name.

The same kind of weirdness corrected(?) in the patch below appears in
gdb/Makefile.in, so I'm not at all sure I'm not misunderstanding
what's going on.  If folks agree that the change below would be
correct, then I'll put together a larger patch that fixes the ones I
can find elsewhere, too.

(Not sure why this hasn't come up before; Daniel J.'s recent posts on
the topic seem to be about setting program_transform_name, not on how
to use it.)

2003-10-07  Jim Blandy  <jimb@redhat.com>

	* Makefile.in (RUNTEST_FOR_TARGET): Pass the transformation to set
	properly.

Index: gdb/testsuite//Makefile.in
===================================================================
RCS file: /cvs/cvsfiles/devo/gdb/testsuite/Makefile.in,v
retrieving revision 1.66
diff -c -r1.66 Makefile.in
*** gdb/testsuite//Makefile.in	9 Sep 2003 21:03:53 -0000	1.66
--- gdb/testsuite//Makefile.in	7 Oct 2003 21:33:22 -0000
***************
*** 53,59 ****
      if [ "$(host_canonical)" = "$(target_canonical)" ]; then \
        echo runtest; \
      else \
!       t='$(program_transform_name)'; echo runtest | sed -e '' $$t; \
      fi; \
    fi`
  
--- 53,59 ----
      if [ "$(host_canonical)" = "$(target_canonical)" ]; then \
        echo runtest; \
      else \
!       t='$(program_transform_name)'; echo runtest | sed -e '$$t'; \
      fi; \
    fi`
  


             reply	other threads:[~2003-10-07 21:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 21:42 Jim Blandy [this message]
2003-10-07 21:50 ` Daniel Jacobowitz
2003-10-07 22:03   ` Theodore A. Roth
2003-10-07 22:53     ` Daniel Jacobowitz
2003-10-07 23:59       ` Felix Lee
2003-10-08  1:05         ` Daniel Jacobowitz
2003-10-08 19:15           ` Jim Blandy
2003-10-08 19:18           ` Jim Blandy
2003-10-08 19:31             ` Daniel Jacobowitz
2003-10-08 19:51               ` Andreas Schwab
2003-10-08 21:22             ` Felix Lee
2003-10-08 19:32           ` Jim Blandy
2003-10-08 19:52             ` Theodore A. Roth
2003-10-08 21:32               ` Felix Lee
2003-10-09  2:09             ` Daniel Jacobowitz
2003-10-08 19:14   ` Jim Blandy
2003-10-07 22:48 ` Felix Lee
2003-10-08 17:44   ` Jim Blandy
  -- strict thread matches above, loose matches on Subject: below --
2003-01-29 22:48 [RFC] Move ``length'' from struct main_type to struct type Kevin Buettner
2003-01-29 23:14 ` Daniel Jacobowitz
     [not found]   ` <drow@mvista.com>
2003-01-30  0:57     ` Kevin Buettner
2003-02-07 21:45 ` Kevin Buettner

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=vt265j0hgj4.fsf@zenia.home \
    --to=jimb@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