From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1088 invoked by alias); 5 Aug 2008 02:42:42 -0000 Received: (qmail 1066 invoked by uid 48); 5 Aug 2008 02:42:42 -0000 Date: Tue, 05 Aug 2008 02:42:00 -0000 Message-ID: <20080805024242.1065.qmail@sourceware.org> X-Bugzilla-Reason: CC References: 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 In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: java-prs@gcc.gnu.org From: "rob1weld at aol dot com" Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org X-SW-Source: 2008-q3/txt/msg00025.txt.bz2 ------- Comment #5 from rob1weld at aol dot com 2008-08-05 02:42 ------- Andrew Pinski 2008-08-04 18:53 wrote: > Not if they want to call their OS a POSIX or UNIX OS really. POSIX actually > makes a standard about programs too. If you want Posix conformant commands (not necessarily GNU programs) then the Docs are here: C(5) http://docs.sun.com/app/docs/doc/819-2252/6n4i8rtov?l=en&a=view It might be easier (for gcc) if we used GNU programs but if you would prefer Posix and other Standards (certified by various groups) then here are a few quotes from that Doc. Solaris 10 supports IEEE Std 1003.1 and IEEE Std 1003.2, commonly known as POSIX.1 and POSIX.2, respectively. POSIX Standard Description Release POSIX.1–2001 POSIX.1-1990, POSIX.1b-1993, POSIX.1c-1996, POSIX.2-1992, and POSIX.2a-1992 updates Solaris 10 Solaris 10 also supports the X/Open Common Applications Environment (CAE) Portability Guide Issue 3 (XPG3) and Issue 4 (XPG4); Single UNIX Specification (SUS, also known as XPG4v2); Single UNIX Specification, Version 2 (SUSv2); and Single UNIX Specification, Version 3 (SUSv3). Both XPG4 and SUS include Networking Services Issue 4 (XNS4). SUSv2 includes Networking Services Issue 5 (XNS5). Utilities If the behavior required by POSIX.2, POSIX.2a, XPG4, SUS, or SUSv2 conflicts with historical Solaris utility behavior, the original Solaris version of the utility is unchanged; a new version that is standard-conforming has been provided in /usr/xpg4/bin. If the behavior required by POSIX.1–2001 or SUSv3 conflicts with historical Solaris utility behavior, a new version that is standard-conforming has been provided in /usr/xpg4/bin or in /usr/xpg6/bin. If the behavior required by POSIX.1–2001 or SUSv3 conflicts with POSIX.2, POSIX.2a, SUS, or SUSv2, a new version that is SUSv3 standard-conforming has been provided in /usr/xpg6/bin. We will need to check the "/usr/xpg4/bin" and "/usr/xpg6/bin" directories also if you desire to use a program that meets a specific standard. Or ... We could just use GNU programs and require that the version number be greater than X and less than Y and that all scripts work within those versions. Newer series of gcc could permit newer version of the said utility program and old versions of gcc could have patch sets made to permit some flexibility on the range of versions permitted. This way we won't paint (program) ourselves into a corner. To me it seems easier to require GNU programs to compile GNU programs. This is why I like to see the old compilers (gcc-3.4.3) working so we can bootstrap up to the newer compilers (4.2.x series). But when I'm running Solaris (and not Linux) I can use the "/usr/xpg4/bin" and "/usr/xpg6/bin" programs (and the wonders of ZFS) too. -- rob1weld at aol dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |major http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37019