Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #70725 > unrolled thread
| Started by | Ned Deily <nad@acm.org> |
|---|---|
| First post | 2014-04-29 11:35 -0700 |
| Last post | 2014-04-29 11:35 -0700 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: how to build and install multiple micro-level major.minor versions of Python Ned Deily <nad@acm.org> - 2014-04-29 11:35 -0700
| From | Ned Deily <nad@acm.org> |
|---|---|
| Date | 2014-04-29 11:35 -0700 |
| Subject | Re: how to build and install multiple micro-level major.minor versions of Python |
| Message-ID | <mailman.9581.1398796532.18130.python-list@python.org> |
In article <1398785310.2673.16.camel@belmer>, "Brent S. Elmer Ph.D." <webe3vt@aim.com> wrote: > Is there a way to do what I want to do (i.e. install 2.7.6 beside 2.7)? The usual way to support multiple micro versions is to build and install to a different location on your system by using: ./configure --prefix=/new/path There is nothing magical about /usr/local or /usr other than that /usr/bin and /usr/local/bin are usually included in default $PATH. If you use a non-default prefix, it's also probably best to avoid using --enable-shared to minimize the chances of confusion with shared library loading. -- Ned Deily, nad@acm.org
Back to top | Article view | comp.lang.python
csiph-web