From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH, doc] PR30739: awk is a build prerequisite
Date: Sat, 14 Jun 2008 09:05:00 -0000 [thread overview]
Message-ID: <20080614084045.GF14042@ins.uni-bonn.de> (raw)
I suppose nobody in those PRs (30739, 29049) remembers which gawk
versions were broken, so let's just go for a general mention.
According to 'info gawk SVR4', GCC needs at least SVR4 awk because
multiple -f options, -v, and regex constants are used during the build.
I haven't seen any Posix requirement in the scripts, at a quick glance.
Tested 'make html info pdf'. OK for trunk?
Thanks,
Ralf
gcc/ChangeLog:
2008-06-14 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
PR documentation/30739
* doc/install.texi (Prerequisites): Document dependency on awk.
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 127f065..50b135d 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -273,6 +273,12 @@ environment to your ``good'' shell prior to running
@command{zsh} is not a fully compliant POSIX shell and will not
work when configuring GCC@.
+@item A ``working'' SVR4 or POSIX awk
+
+Necessary for creating some of the generated source files for GCC@.
+If in doubt, use a recent GNU awk version, as some of the older ones
+are broken.
+
@item GNU binutils
Necessary in some circumstances, optional in others. See the
next reply other threads:[~2008-06-14 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 9:05 Ralf Wildenhues [this message]
2008-06-15 22:21 ` Ian Lance Taylor
2008-06-15 22:23 ` NightStrike
2008-06-15 22:26 ` Ian Lance Taylor
2008-06-18 18:52 ` Ralf Wildenhues
2008-06-18 18:56 ` Andrew Pinski
2008-06-18 19:10 ` Ralf Wildenhues
2008-06-19 3:40 ` Gerald Pfeifer
2008-06-18 13:53 ` Gerald Pfeifer
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=20080614084045.GF14042@ins.uni-bonn.de \
--to=ralf.wildenhues@gmx.de \
--cc=gcc-patches@gcc.gnu.org \
/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).