Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #70726 > unrolled thread

Re: how to build and install multiple micro-level major.minor versions of Python

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.

Contents

  Re: how to build and install multiple micro-level major.minor versions of Python "Brent S. Elmer Ph.D." <webe3vt@aim.com> - 2014-04-29 14:53 -0400
    Re: how to build and install multiple micro-level major.minor versions of Python Mark H Harris <harrismh777@gmail.com> - 2014-04-29 14:53 -0500
    Re: how to build and install multiple micro-level major.minor versions of Python Mark H Harris <harrismh777@gmail.com> - 2014-04-29 14:57 -0500

#70726 — Re: how to build and install multiple micro-level major.minor versions of Python

On Tue, 2014-04-29 at 11:35 -0700, Ned Deily wrote:
> 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
> 

Yes, I already use --prefix to build to a different path.  I guess that
is what I need to do but I would rather have a way to have the build and
install process install to the micro level.

Brent

[toc] | [next] | [standalone]

#70727

On 4/29/14 1:53 PM, Brent S. Elmer Ph.D. wrote:
> Yes, I already use --prefix to build to a different path.  I guess that
> is what I need to do but I would rather have a way to have the build and
> install process install to the micro level.
>

example only,
Use --prefix /usr/local/2.7.6/

Use --prefix /usr/local/2.7.2/

&c.,

Both of the 2.7 installs will be 2.7, but it doesn't matter because they 
will (each one) be installed under a different micro level.

... works great.

marcus

[toc] | [prev] | [next] | [standalone]

#70728

On 4/29/14 1:53 PM, Brent S. Elmer Ph.D. wrote:
> I would rather have a way to have the build and
> install process install to the micro level.
>

I agree.

On the other hand, is there really a special need to thoroughly test 
against a micro level.

I have the latest 2.6, 2.7, 3.2, 3.3, 3.4 ... there might a critical 
reason for splitting hairs, but honestly, probably not.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web