From: Joel Brobecker <brobecker@gnat.com>
To: gdb-patches@sources.redhat.com
Subject: build failure due to observer.sh
Date: Fri, 16 Apr 2004 16:39:00 -0000 [thread overview]
Message-ID: <20040416163944.GS1131@gnat.com> (raw)
Hello,
The build failed on most of our machines, due to a problem happening
during the sed command in observer.sh. Here is the output we got:
Creating observer.h-tmp
sed: # Save original line for later processing into the actual parameter is not a recognized function.
As a consequence, all observers are missing, and we fail during the link.
I tried on AiX to remove the comments, to see if it works any better,
and managed to get past this error. Are comments a GNU sed extension?
In my opinion, I would handle observer.sh the same as gdbarch.sh:
The contributors run it manually when needed. And we keep and up-to-date
version of observer.[hc] checked in the repository. That way, we avoid
requiring a certain implementation of sed when just building GDB.
I can regenerate observer.[hc] and check them in, if you agree.
--
Joel
next reply other threads:[~2004-04-16 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 16:39 Joel Brobecker [this message]
2004-04-16 19:24 ` Andrew Cagney
2004-04-16 21:04 ` Joel Brobecker
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=20040416163944.GS1131@gnat.com \
--to=brobecker@gnat.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