public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "rwild at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/37019] [4.2 Regression] Inconsistent gcc-4.2.3/libjava/configure uses "grep" and "egrep" and "grep -E" and "$EGGREP" but not ggrep -- sed also is trouble Date: Mon, 04 Aug 2008 08:57:00 -0000 [thread overview] Message-ID: <20080804085749.30345.qmail@sourceware.org> (raw) In-Reply-To: <bug-37019-13830@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from rwild at gcc dot gnu dot org 2008-08-04 08:57 ------- I see the egrep issue. Can you please specify for which grep and sed commands you see errors? The assumption is that all systems do have sed and grep available, but that the vendor versions of these tools have some quirks that make it unsuitable for some (but not all) uses. Wrt. egrep and fgrep, there are systems for which 'grep -E' and 'grep -F' have to be used. If any of these assumptions are not valid, then I would like to know details, so that the Autoconf manual can be updated to reflect this. -- rwild at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rwild at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37019
next prev parent reply other threads:[~2008-08-04 8:57 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-08-04 5:26 [Bug libgcj/37019] New: " rob1weld at aol dot com 2008-08-04 8:57 ` rwild at gcc dot gnu dot org [this message] 2008-08-04 17:18 ` [Bug libgcj/37019] " rob1weld at aol dot com 2008-08-04 17:21 ` rob1weld at aol dot com 2008-08-04 18:53 ` pinskia at gcc dot gnu dot org 2008-08-04 18:54 ` pinskia at gcc dot gnu dot org 2008-08-05 2:42 ` rob1weld at aol dot com 2008-08-05 5:07 ` rob1weld at aol dot com 2008-08-05 6:50 ` rwild at gcc dot gnu dot org 2008-08-05 16:59 ` rob1weld at aol dot com 2008-08-10 20:06 ` [Bug libgcj/37019] libjava/configure " pinskia at gcc dot gnu dot 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=20080804085749.30345.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@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).