| |
|---|
| | |
|---|
| | |
|---|
| | ## Building The Full Tools Set |
|---|
| | |
|---|
| | 1. Log into you build machine, VM, or`docker`image. *Make sure this |
|---|
| | 1. Log into your build machine, VM, or`docker`image. *Make sure this |
|---|
| | machine does *not* have native OS compilers and development tools |
|---|
| | installed and/or in `${PATH}`!* We want to use only the compiler and |
|---|
| | installed and/or in `${PATH}`*! We want to use only the compiler and |
|---|
| | tools created in the previous step. `Docker` containers are handy here: |
|---|
| | One for the bootstrap build, another for the self compiling |
|---|
| | full tools build. |
|---|
| | |
|---|
| | However, there are a few things that *are* required in the OS load, |
|---|
| | because of boneheaded assumptions made by some open source packages |
|---|
| | about where things live. So: |
|---|
| | |
|---|
| | `sudo yum -y install autoconf automake perl' # Or whatever package management system you use |
|---|
| | |
|---|
| | 2. Un-tar the bootstrap tarball created above into the proper location. |
|---|
| | Recall that this was saved with a date revision stamp. So, before |
|---|
| | proceeding, we have to: |
|---|
| |
|---|
| | 7. Cleanup: |
|---|
| | |
|---|
| | `make clean` |
|---|
| | |
|---|
| | |
|---|
| | ## Installing The Tools |
|---|
| | |
|---|
| | We've just created a tarball that has all the tools we want precompiled |
|---|
| | and ready for distribution. We just untar the full tools tarball onto |
|---|
| |
|---|
| | |
|---|
| | `/opt/mydir/tools` |
|---|
| | |
|---|
| | Every installation on other machines must also install them |
|---|
| | there (and be added to `$(PATH}` as described in `brewenv`. |
|---|
| | there (and be added to `$(PATH}` as described in `brewenv`). |
|---|
| | |
|---|
| | Recall that this procedure actually creates the tools directory |
|---|
| | as: |
|---|
| | |
|---|
| | `/opt/mydur/tools-YYYYMMDD`. |
|---|
| | `/opt/mydir/tools-YYYYMMDD`. |
|---|
| | |
|---|
| | In this example, you could either symlink `tools` to that |
|---|
| | directory or just rename the directory accordingly. |
|---|
| | |
|---|
| |
|---|
| | |
