public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jitendra Pawar <jitendra@linsyssoft.com>
To: binutils@sources.redhat.com
Cc: ramana.radhakrishnan@codito.com, nickc@redhat.com
Subject: Re: Running Individual tests from gas suites.
Date: Wed, 09 Feb 2005 10:12:00 -0000	[thread overview]
Message-ID: <1107932114.3624.6.camel@ind.linsyssoft.com> (raw)
In-Reply-To: <Pine.BSF.4.58.0502081153110.26728@dair.pair.com>

[-- Attachment #1: Type: text/plain, Size: 566 bytes --]


> Please send patches, not the whole modified file.

Here I have attached patch file...!

:-)
Jitendra

On Tue, 2005-02-08 at 22:24, Hans-Peter Nilsson wrote:
> On Tue, 8 Feb 2005, Jitendra Pawar wrote:
> > To remove this error there is modification need in gas/lib/gas-defs.exp
> > file. here I have attached modified file. one can get changes by grep on
> > 'gas_spawned'.
> >
> > can you please add this change in nest release?
> 
> Please send patches, not the whole modified file.
> (No, don't send it to me, send it to the list.)
> Thanks.
> 
> brgds, H-P
> 

[-- Attachment #2: gas-defs.exp.patch --]
[-- Type: text/plain, Size: 952 bytes --]

--- gas-defs.exp.org	2005-02-09 12:13:09.000000000 +0530
+++ gas-defs.exp	2005-02-09 12:21:01.000000000 +0530
@@ -59,6 +59,7 @@
     global srcdir
     global subdir
     global spawn_id
+    global gas_spawned
 
     verbose -log "Starting $AS $ASFLAGS $as_opts $prog" 2
     catch {
@@ -66,14 +67,20 @@
     } foo
     if ![regexp {^[0-9]+} $foo] then {
 	perror "Can't run $subdir/$prog: $foo"
+    } else {
+        set gas_spawned 1
     }
 }
 
 proc gas_finish { } {
     global spawn_id
+    global gas_spawned
 
-    catch "close"
-    catch "wait"
+    if $gas_spawned then {
+	    catch "close"
+	    catch "wait"
+    }
+    set gas_spawned 0
 }
 
 proc want_no_output { testname } {
@@ -165,7 +172,9 @@
     global target_vendor
     global target_os
     global stdoptlist
+    global gas_spawned
 
+    set gas_spawned 0
     case "$target_cpu" in {
 	"m68???"		{ set target_cpu_family m68k }
 	"i[3-7]86"		{ set target_cpu_family i386 }

  reply	other threads:[~2005-02-09  7:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-01  7:12 Running gas and ld test suites remotely Jitendra Pawar
2005-02-01  7:21 ` Jitendra Pawar
2005-02-01 10:44 ` Nick Clifton
2005-02-02 13:21   ` Jitendra Pawar
2005-02-02 15:40     ` Ramana Radhakrishnan
2005-02-08 15:51       ` Jitendra Pawar
2005-02-08 16:01         ` Nick Clifton
2005-02-08 17:31           ` Running Individual tests from gas suites Jitendra Pawar
2005-02-08 20:19             ` Hans-Peter Nilsson
2005-02-09 10:12               ` Jitendra Pawar [this message]
2005-02-09 16:58             ` Nick Clifton
2005-02-10 13:13               ` Jitendra Pawar

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=1107932114.3624.6.camel@ind.linsyssoft.com \
    --to=jitendra@linsyssoft.com \
    --cc=binutils@sources.redhat.com \
    --cc=nickc@redhat.com \
    --cc=ramana.radhakrishnan@codito.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).