Post History
The usual way is to specify an installation location with ./configure --prefix="$HOME/python" ... and then make install after make. If you don't specify a --prefix argument to configure, it ty...
Answer
#2: Post edited
by
terdon
·
2023-06-21T21:06:35Z (over 1 year ago)
It isn't inconceivable that a user's $HOME can contain a space
- The usual way is to specify an installation location with
- ```
./configure --prefix=$HOME/python- ```
- ... and then `make install` after `make`.
- If you don't specify a `--prefix` argument to `configure`, it typically defaults to `/usr/local` (so `make install` will install `python` as `/usr/local/bin/python` which should already be on your `PATH`, and libraries somewhere like `/usr/local/lib/python/3.11`).
- The usual way is to specify an installation location with
- ```
- ./configure --prefix="$HOME/python"
- ```
- ... and then `make install` after `make`.
- If you don't specify a `--prefix` argument to `configure`, it typically defaults to `/usr/local` (so `make install` will install `python` as `/usr/local/bin/python` which should already be on your `PATH`, and libraries somewhere like `/usr/local/lib/python/3.11`).
#1: Initial revision
by
tripleee
·
2023-06-20T13:18:00Z (over 1 year ago)
The usual way is to specify an installation location with ``` ./configure --prefix=$HOME/python ``` ... and then `make install` after `make`. If you don't specify a `--prefix` argument to `configure`, it typically defaults to `/usr/local` (so `make install` will install `python` as `/usr/local/bin/python` which should already be on your `PATH`, and libraries somewhere like `/usr/local/lib/python/3.11`).