public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "skunk at iskunk dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/53607] New: opt-functions.awk --> "awk: There is a regular expression error." Date: Fri, 08 Jun 2012 02:16:00 -0000 [thread overview] Message-ID: <bug-53607-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53607 Bug #: 53607 Summary: opt-functions.awk --> "awk: There is a regular expression error." Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap AssignedTo: unassigned@gcc.gnu.org ReportedBy: skunk@iskunk.org Host: hppa2.0w-hp-hpux11.00 Target: hppa2.0w-hp-hpux11.00 Build: hppa2.0w-hp-hpux11.00 Created attachment 27583 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27583 Proposed fix Bootstrapping 4.7.0 on an HP-UX 11.00 system fails with [...] echo timestamp > s-options awk -f /home/src/gcc-4.7.0/gcc/opt-functions.awk -f /tg/freepor t/src/gcc/gcc--4.7.0-tera/gcc/opt-read.awk \ -f /home/src/gcc-4.7.0/gcc/opth-gen.awk \ < optionlist > tmp-options.h awk: There is a regular expression error. ?, *, or + not preceded by valid regular expression The source line number is 90. The error context is if (flags ~ >>> "^{") <<< gmake[3]: *** [s-options-h] Error 2 gmake[3]: Leaving directory `/tmp/gcc-build/gcc' gmake[2]: *** [all-stage1-gcc] Error 2 gmake[2]: Leaving directory `/tmp/gcc-build' gmake[1]: *** [stage1-bubble] Error 2 gmake[1]: Leaving directory `/tmp/gcc-build' gmake: *** [bootstrap-lean] Error 2 The fix for this is fairly trivial; patch against SVN is attached.
next reply other threads:[~2012-06-08 2:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-08 2:16 skunk at iskunk dot org [this message] 2012-12-23 3:18 ` [Bug bootstrap/53607] " danglin at gcc dot gnu.org 2021-12-24 14:12 ` pinskia at gcc dot gnu.org
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=bug-53607-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).