rtsi.com/2014.01.www.rtsi.com.tar/www.rtsi.com/OS9/OSK/APPS/bash.lzh/oskBashStory

Text File | 1993-09-13 | 2KB | 40 lines

================================================ Wed Sep  8 09:30:32 GMT 1993 =

This is the file "oskBashStory.txt". It describes how things came to the
port of GNU-bash to OSK. The information herein is not of much interest.
I think you should read this only if you absolutely have no idea how to
waste your time :-).

Actually I ported bash to OSK for my own (especially for the purpose of
running UN*X scripts like GNUs "configure" and others). My intention was
to establish an easy to use method for porting arbitrary GNU/UN*X software
to OSK. The method should need as few manual intervention as possible.
Ideally there would be a program "gnu2osk" which does all needed
modifications automagically. So one would only have to type:

        gnu2osk ; make all        (or something like that)

For that I first ported gcc to OSK (1.07, 1.36, 2.1, ...).

Second I re-coded the whole uware C-library "clib.l", added some
frequently used ANSI-C and UN*X features and wrote online doc for it.

After that I ported some other GNU software to OSK (m4, sed, awk,
bash, make, tar, compress, gzip, bison, flex, [ef]grep, ...).

While doing the things above I got sad of the OSK filesystem's
boring naming conventions. Three of two UN*X filenames are not valid
under OSK :-(. So the most important thing I got to do was to overload
OSK filesystem's naming conventions. I did it ... and it works fine!

Some time ago I started writing a simple bash-script for automatic
modifying GNUs configure scripts. But this is very far away from
being "ready to run". (Currently I do not have much time to deal with
OS-9 since there are other things to do ...).

===============================================================================

Norbert Berzen ([e-mail])

*** eof