OS-SCO-OpenSource

From KRayWiki
Revision as of 19:52, 3 July 2018 by Krb (talk | contribs) (Describe user environment likely to affect free software build activityies.)
Jump to navigation Jump to search

Index to SCO OpenServer 5.0.7 topics related to the use of open source projects

See Also: 
OS-SCO-OpenSource-KnownIssues
OS-SCO


Introduction

Topic Goals

This page primarily indexes local wiki pages that aggregate information relating to attempts to build and deploy free software to the OpenServer 5.0.7 platform. While these pages will document successes, it is intended to also show issues, workarounds, and even failures to deploy projects to the platform.

FTP Site

  • ftp.bulgrien.net
    The server allows anonymous connections, but login details deviate from what is sometimes expected:
    User Name: anonymous@domain
    Password: any non-blank
    If a domain is not included, expect an error response like:
    421 Can't change directory to /var/ftp/ error message.

System Configuration

The following list helps define what vendor-specific packages are present on the systems used to build free software source packages. The list does not necessarily paint the complete picture, as a number of the software listed below is configured to take precedence over some of the vendor-supplied tools. This list taken from the Software tab of the "custom" utility.

Extended Shells (ver 1.4.1Ab) FSUpthreads - POSIX 1003.1c threads implementation (ver 3.14) GNU Development Tools (ver 5.0.7Kj) GNU Development Tools (ver 5.0.7g) Java 2 1.3.1_22 Plugin (ver 1.3.1Va) Java 2 1.3.1_22 Runtime Environment (ver 1.3.1Va) Java 2 1.3.1_22 Software Development Kit (ver 1.3.1Va) SCO OpenServer Development System (ver 5.2.0Aa) SCO OpenServer Enterprise System (ver 5.0.7Hw) patchck - package management tool (ver 18051503) OSS672A - OpenServer 5 Network Header File Update (ver 1.0.0) OSS673A - OSR 5.0.7 SCSI Floppy Driver supplement (ver 1.0.0) P535239A - pmd security fix (ver 1.0.0) SCO OpenServer Release 5.0.7 Maintenance Pack 5 (ver 1.0.0Mc)

User Account

A summary of possibly pertinent user environment follows:

  1. As a rule, development occurs from within a BASH shell.
    Logon, then $ bash --login.
    ~/.bashrc has no development-specific settings.
    ~/.bash_profile does have a few pertinent settings.
    ACCEPT_INFERIOR_RM_PROGRAM=yes
    export ACCEPT_INFERIOR_RM_PROGRAM
    CPATH=${HOME}/include
    export CPATH
    CFLAGS="-static"
    export CFLAGS
    PKG_CONFIG_PATH=${HOME}/lib/pkgconfig
    export PKG_CONFIG_PATH
  2. Search paths
    PATH
    ${HOME}/bin:/usr/local/bin:/usr/local/sbin:/usr/gnu/bin:/bin:/etc:/sbin:/usr/bin:/usr/sbin:/usr/java/bin:/usr/bin/X11
    MANPATH
    ${HOME}/share/man:${HOME}/man:/usr/local/share/man:/usr/man:/usr/gnu/man:/usr/X11R6/man
  3. Tool chain updates
    gcc
    In general, the vendor-supplied gcc 2.95 is used, but gcc-3.4.6 was built and is deployed to the user's directory along with autotool and other utility updates. gcc project files are named with a -3.4.6 suffix, so CC defaults to the older revision. 2.95 has worked fine so far, and use of 3.4.6 has not proven to be necessary as of yet.
    automake 1.9, 1.14, 1.15
    autoconf 2.69
    grep 2.25
    libtool 1.5.24
    make 3.82
  4. Various updated tools are used in lieu of older, vendor-supplied utilities:
    grep 2.25

NOTE: All newer tool and utility versions may not all prove essential. In the face of difficulty with replicating build results, it is hoped that these disclosures may facilitate understanding and resolution.

GNU

Miscellaneous