diff options
Diffstat (limited to '')
| -rw-r--r-- | src/sed/README | 13 | ||||
| -rw-r--r-- | src/sed/README-alpha | 8 | ||||
| -rw-r--r-- | src/sed/README.boot | 23 |
3 files changed, 44 insertions, 0 deletions
diff --git a/src/sed/README b/src/sed/README new file mode 100644 index 0000000..3da31c2 --- /dev/null +++ b/src/sed/README @@ -0,0 +1,13 @@ +This is the GNU implementation of sed, the Unix stream editor. + +See the NEWS file for a brief summary and the ChangeLog for +more detailed descriptions of changes. + +See the file INSTALL for generic compilation and installation +instructions. + +See the file BUGS for instructions about reporting bugs. + +The file README.boot gives instructions for making a "bootstrap" +version of sed on systems which lack any pre-existing and working +version of sed. diff --git a/src/sed/README-alpha b/src/sed/README-alpha new file mode 100644 index 0000000..9235efe --- /dev/null +++ b/src/sed/README-alpha @@ -0,0 +1,8 @@ +This is an alpha version of GNU sed. Please try it on a wide +range of scripts (especially configure scripts) and submit +bug reports to bonzini@gnu.org. + +Thanks, + +Paolo Bonzini +GNU sed maintainer diff --git a/src/sed/README.boot b/src/sed/README.boot new file mode 100644 index 0000000..fd2d1a0 --- /dev/null +++ b/src/sed/README.boot @@ -0,0 +1,23 @@ +Because a working sed is a prerequisite for running the ``configure'' +script, I have provided the script ``bootstrap.sh'' which will attempt +to build a version of sed adequate for running ``configure''. If it +fails, edit the ``config.h'' file that was created according to the +comments found therein, and then try running ``bootstrap.sh'' again. + +The bootstrap build is quite likely to babble on and on with +various compiler warnings. You may want to tell bootstrap.sh +how to invoke your compiler with warnings disabled. For example, +with a Bourne-like shell and gcc one could use: + $ CC='gcc -w' sh bootstrap.sh +or with a csh-like shell, one could try: + % env CC='gcc -w' sh bootstrap.sh + +Once you get a working version of sed, temporarily install sed/sed +somewhere in your $PATH, and then really re-build the normal way +(starting with ``sh configure''); the bootstrap version is almost +certainly more crippled than it needs to be on your machine. + +I don't much care to hear about any bugs in ``bootstrap'' versions +of sed beyond those which actually keep the ``bootstrap'' version from +building, or sed's configure script from running properly. I am +especially uninterested in compiler warnings from the bootstrap build. |