| 1 | Because a working sed is a prerequisite for running the ``configure''
|
|---|
| 2 | script, I have provided the script ``bootstrap.sh'' which will attempt
|
|---|
| 3 | to build a version of sed adequate for running ``configure''. If it
|
|---|
| 4 | fails, edit the ``config.h'' file that was created according to the
|
|---|
| 5 | comments found therein, and then try running ``bootstrap.sh'' again.
|
|---|
| 6 |
|
|---|
| 7 | The bootstrap build is quite likely to babble on and on with
|
|---|
| 8 | various compiler warnings. You may want to tell bootstrap.sh
|
|---|
| 9 | how to invoke your compiler with warnings disabled. For example,
|
|---|
| 10 | with a Bourne-like shell and gcc one could use:
|
|---|
| 11 | $ CC='gcc -w' sh bootstrap.sh
|
|---|
| 12 | or with a csh-like shell, one could try:
|
|---|
| 13 | % env CC='gcc -w' sh bootstrap.sh
|
|---|
| 14 |
|
|---|
| 15 | Once you get a working version of sed, temporarily install sed/sed
|
|---|
| 16 | somewhere in your $PATH, and then really re-build the normal way
|
|---|
| 17 | (starting with ``sh configure''); the bootstrap version is almost
|
|---|
| 18 | certainly more crippled than it needs to be on your machine.
|
|---|
| 19 |
|
|---|
| 20 | I don't much care to hear about any bugs in ``bootstrap'' versions
|
|---|
| 21 | of sed beyond those which actually keep the ``bootstrap'' version from
|
|---|
| 22 | building, or sed's configure script from running properly. I am
|
|---|
| 23 | especially uninterested in compiler warnings from the bootstrap build.
|
|---|
