public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/37019]  New: [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 05:26:00 -0000	[thread overview]
Message-ID: <bug-37019-13830@http.gcc.gnu.org/bugzilla/> (raw)

The gcc-4.2.3/libjava/configure uses "grep" and "egrep" and "grep -E" and
"$EGGREP" (but not "ggrep") in a non-portable and inconsistent manner.

Examples:

1. Lines 5224, 5254, 5295, 5298, etc...  use "egrep" but "EGREP" is not tested
for (to decide if we will use "grep -E" or "egrep") until line 7315 and not set
until line 7322.

Correct usage would be to check if we need to use "ggrep" since on Solaris
"grep" is NOT the GNU grep, instead "ggrep" is the GNU grep. A few simple
commands in Solaris's "grep" _are_ compatable with GNU's "grep" but most
commands are not.

Solaris also has "egrep" and "fgrep" but those are also both Non-GNU programs.

To use "egrep" or "fgrep" (in Solaris) you must use "ggrep -E" or "ggrep -F".

---

The other problem is that Solaris (I have the newest version) does not have a
GNU sed program. Worse news. It _does_ have a "sed" program, but there is no
command to obtain a version number. Looking at the "man sed" command says that
the man page is dated "23 Jul 1998". In a "normal" installation of Solaris
there is no "gsed" command.

The GNU "sed" command can be tested by running "sed --version" and it will
reply "GNU sed version x.y.z". The Solaris "sed" command has no means to check
it's version (that I am aware of -- you might ggrep the binary ;) ).


If someone wants a "gsed" command for Solaris they must either compile "sed"
themselves or type this (see this URL: http://www.blastwave.org/howto.html):

# pkgadd -d http://www.blastwave.org/pkg_get.pkg
# /opt/csw/bin/pkg-get -U 
# /opt/csw/bin/pkg-get -i wget
# /opt/csw/bin/pkg-get -i gsed

That provides a "GNU sed" as "/opt/csw/bin/gsed". It is version 4.1.4

Elsewhere in gcc I have noticed that other configure scripts do not have this
problem, they do check for the "g"-prefixed commands. The (correct) configury
uses tests to set environment variables that are used for the program's name
throughout the rest of the script.


-- 
           Summary: [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
           Product: gcc
           Version: 4.2.3
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: libgcj
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: rob1weld at aol dot com
 GCC build triplet: i386-pc-solaris2.11
  GCC host triplet: i386-pc-solaris2.11
GCC target triplet: i386-pc-solaris2.11


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37019


             reply	other threads:[~2008-08-04  5:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04  5:26 rob1weld at aol dot com [this message]
2008-08-04  8:57 ` [Bug libgcj/37019] " rwild at gcc dot gnu dot org
2008-08-04 17:18 ` 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=bug-37019-13830@http.gcc.gnu.org/bugzilla/ \
    --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: 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).