lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

lynx-dev dev.4 config.guess OS/390 turf war


From: pg
Subject: lynx-dev dev.4 config.guess OS/390 turf war
Date: Fri, 14 Jul 2000 15:56:01 -0600 (MDT)

Hello, Lyncei,

The following:

* updates for config.guess, config.sub from tin -TD

has introduced conflicting treatment of OS/390 in config.guess:

--- lynx2.8.4dev.3/lynx2-8-4/config.guess       Mon Feb 14 21:07:39 2000
+++ lynx2.8.4dev.4/lynx2-8-4/config.guess       Fri Jun 23 09:15:08 2000
@@ -133,6 +156,9 @@
     wgrisc:OpenBSD:*:*)
        echo mipsel-unknown-openbsd${UNAME_RELEASE}
        exit 0 ;;
+    *:OS/390:*:*)
+       echo i370-ibm-openedition
+       exit 0 ;;
     arm:RISC*:1.[012]*:*|arm:riscix:1.[012]*:*)
        echo arm-acorn-riscix${UNAME_RELEASE}
        exit 0;;
@@ -306,17 +362,17 @@
        exit 0 ;;
     ????????:AIX?:[12].1:2)   # AIX 2.2.1 or AIX 2.1.1 is RT/PC AIX.
        echo romp-ibm-aix      # uname -m gives an 8 hex-code CPU id
-       exit 0 ;;              # Note that: echo "'`uname -s`'" gives 'AIX '
+       exit 0 ;;              # Note that: echo "'`uname -s`'" gives 'AIX '
     i?86:AIX:*:*)
        echo i386-ibm-aix
        exit 0 ;;
-    *:MVS:*:* | *:OS390:*:*|*:OS/390:*:*)
+    *:MVS:*:* | *:OS390:*:* | *:OS/390:*:*)
                               # uname -m gives a processor model number  /* 
S/390 -- gil -- 1389 */
        echo s390-ibm-os390    # on R1 and R2, uname -s reports OS390
        exit 0 ;;              # on R3, uname -s reports OS/390
     *:AIX:2:3)
        if grep bos325 /usr/include/stdio.h >/dev/null 2>&1; then
-               sed 's/^                //' << EOF >dummy.c
+               sed 's/^                //' << EOF >$dummy.c
                #include <sys/systemcfg.h>
 
                main()

Alas, the earlier prevails where I much prefer the latter.
I'm surprised it worked at all.  I got the latter from Mortice Kern
Systems, http://www.mks.com/s390/gnu/register.htm, which has done
a thorough port of Autoconf.  Alas, reportedly RMS sneers at OS/390,
considering it too far out of mainstream to merit consideration,
so the MSK OS/390 adaptation has never been fed back to the main
Autoconf tree.

But which should prevail for Lynx's OS/390 port, Tin or MKS?

BTW, "370", "mvs" and "openedition" are all obsolete in IBM's
lexicon, having been replaced by "S/390", "OS/390", and
"Unix Services".  Of these, "S/390" and "OS/390" are marked
to be obsolete this year, to be replaced by something code
named "Freeway".

-- gil
-- 
StorageTek
INFORMATION made POWERFUL

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]