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

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

Re: python 6 compilation failure on RHEL

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: python 6 compilation failure on RHEL Cameron Simpson <cs@zip.com.au> - 2012-08-21 08:25 +1000
    Re: python 6 compilation failure on RHEL Anssi Saari <as@sci.fi> - 2012-08-23 14:34 +0300

#27535 — Re: python 6 compilation failure on RHEL

On 20Aug2012 12:19, Emile van Sebille <emile@fenx.com> wrote:
| On 8/20/2012 11:37 AM Walter Hurry said...
| > On Mon, 20 Aug 2012 11:02:25 -0700, Emile van Sebille wrote:
| >> On 8/20/2012 10:20 AM Walter Hurry said...
| >>> I concur, but FYI the version of Python with RHEL5 is 2.4. Still, OP
| >>> should stick with that unless there is a pressing reason.
| >>
| >> Hence, the 2.6 install.
| >
| > First, sorry for my omission to trim.
| >
| > Second, the reason for recommending that OP stick to the Red Hat provided
| > version (unless there is a pressing reason) is the question of the
| > already-paid-for Red Hat support.
| 
| Generally, when you compile from source the binaries will install to 
| /usr/local/bin and not be in conflict with RH's install version.

I was going to chime in with this anyway had the thread said nothing; I
strongly prefer to specify --prefix explicitly with configure.

My personal habit to to build with (adjust to match):

  --prefix=/usr/local/python-2.6.4

and put some symlinks in /usr/local/bin afterwards (python2.6, etc).

That way one doesn't tread on the system Python (after all the OS vendor
distro is also a collection of packages with coordinated versions)
and one can easily put in another python beside it.

| > And for that matter, if OP is forced to a later Python 2 version than
| > 2.4, why not 2.7.3?
| 
| Package dependencies.  If the OP intends to install a package that 
| doesn't support other than 2.6, you install 2.6.

Indeed. And this is a strong reason to keep out of the vendor's /usr
filesystem space, also.

Cheers,
-- 
Cameron Simpson <cs@zip.com.au>

[toc] | [next] | [standalone]

#27861

Cameron Simpson <cs@zip.com.au> writes:

> My personal habit to to build with (adjust to match):
>
>   --prefix=/usr/local/python-2.6.4
>
> and put some symlinks in /usr/local/bin afterwards (python2.6, etc).

There's actually a program for that, it's called stow.

[toc] | [prev] | [standalone]

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

csiph-web