Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@gnat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: build failure due to observer.sh
Date: Fri, 16 Apr 2004 21:04:00 -0000	[thread overview]
Message-ID: <20040416210414.GI22414@gnat.com> (raw)
In-Reply-To: <408032C5.9040104@gnu.org>

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

> I don't think so, just sounds like it isn't a common extension, do the 
> comments need to be in column one?

Moving the comments to column one seems to be fixing the problem.
I tested the attached patch on ppc-aix 5.1 (/usr/bin/sed),
alpha-tru64 5.1 (/usr/bin/sed), and solaris 2.5+2.8 (usr/xpg4/bin/sed).
It worked in all cases.

> Having this built on-demand is one of the departures from gdbarch.sh 
> (and why I committed this now, so early in a release cycle).  I'd like 
> to see how unfixable the problem is before abandoning the idea.

OK. I tend to prefer to have all files under revision control, generated
files included. That's because when somebody tells us about a problem,
we are certain about the sources he used. If some of the files are
generated on demand, then we have to consider the possibility of him
having experienced a problem during the generation.

Hardly an important issue, though.

2004-04-16  Joel Brobecker  <brobecker@gnat.com>

        * observer.sh: Move comments in sed command to first column.

Ok to apply?

Thanks,
-- 
Joel

[-- Attachment #2: observer.sh.diff --]
[-- Type: text/plain, Size: 1331 bytes --]

Index: observer.sh
===================================================================
RCS file: /cvs/src/src/gdb/observer.sh,v
retrieving revision 1.1
diff -u -p -r1.1 observer.sh
--- observer.sh	15 Apr 2004 14:29:20 -0000	1.1
+++ observer.sh	16 Apr 2004 20:39:48 -0000
@@ -62,22 +62,22 @@ esac
 IFS=:
 sed -n '
 /@deftypefun void/{
-    # Save original line for later processing into the actual parameter
+# Save original line for later processing into the actual parameter
     h
-    # Convert from: @deftypefun void EVENT (TYPE @var{PARAM},...)
-    # to event and formals: EVENT:TYPE PARAM, ...:
+# Convert from: @deftypefun void EVENT (TYPE @var{PARAM},...)
+# to event and formals: EVENT:TYPE PARAM, ...:
     s/^.* void \([a-z_][a-z_]*\) (\(.*\))$/\1:\2/
     s/@var{//g
     s/}//g
-    # Switch to held
+# Switch to held
     x
-    # Convert from: @deftypefun void FUNC (TYPE @var{PARAM},...)
-    # to actuals: PARAM, ...
+# Convert from: @deftypefun void FUNC (TYPE @var{PARAM},...)
+# to actuals: PARAM, ...
     s/^[^{]*[{]*//
     s/[}]*[^}]*$//
     s/}[^{]*{/, /g
-    # Combine held (EVENT:TYPE PARAM, ...:) and pattern (PARAM, ...) into
-    # FUNC:TYPE PARAM, ...:PARAM, ...
+# Combine held (EVENT:TYPE PARAM, ...:) and pattern (PARAM, ...) into
+# FUNC:TYPE PARAM, ...:PARAM, ...
     H
     x
     s/\n/:/g

  reply	other threads:[~2004-04-16 21:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-16 16:39 Joel Brobecker
2004-04-16 19:24 ` Andrew Cagney
2004-04-16 21:04   ` Joel Brobecker [this message]
2004-04-17  0:43     ` Andrew Cagney
2004-04-17  4:46       ` Joel Brobecker
2004-04-20 16:26     ` Andrew Cagney
2004-04-20 18:06       ` Joel Brobecker
2004-04-16 21:55 ` Jim Blandy

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=20040416210414.GI22414@gnat.com \
    --to=brobecker@gnat.com \
    --cc=cagney@gnu.org \
    --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