FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 02-18-2012, 11:18 PM
Mark Knecht
 
Default python 2.x vs 3.x

In a current thread started by Meino where he is having trouble
emerging hydrogen he reported the following quoted data to Neil. I
don't believe Neil has responded yet but Meino's data brought me back
to a question I've meant to ask for a while so I'll take this
opportunity.

From Meino:

<QUOTE>
With

eselect python list

I get

Available Python interpreters:
[1] python2.6
[2] python2.7
[3] python3.1
[4] python3.2 *
</QUOTE>

which shows python3.2 as the system wide default.

It's been my understanding ever since we first emerged any
python-3.x version that we were not supposed to set any version of
python3 as the system wide default. On all of my systems I have
something like this:

c2stable ~ # eselect python list
Available Python interpreters:
[1] python2.7 *
[2] python3.2
c2stable ~ # eselect python list --python2
Available Python 2 interpreters:
[1] python2.7 *
c2stable ~ # eselect python list --python3
Available Python 3 interpreters:
[1] python3.2 *
c2stable ~ #

Now, like Paul Hartman I didn't have any trouble building and
running Hydrogen as a Jack client. It works just fine for me. However
no one else seemed to have picked up on Meino's configuration which
makes me wonder if I missed the memo to make the 3.x version of the
system wide default.

What is the current best practice in this area?

Cheers,
Mark
 
Old 02-19-2012, 12:37 AM
Paul Hartman
 
Default python 2.x vs 3.x

On Sat, Feb 18, 2012 at 6:18 PM, Mark Knecht <markknecht@gmail.com> wrote:
> In a current thread started by Meino where he is having trouble
> emerging hydrogen he reported the following quoted data to Neil. I
> don't believe Neil has responded yet but Meino's data brought me back
> to a question I've meant to ask for a while so I'll take this
> opportunity.
>
> From Meino:
>
> <QUOTE>
> With
>
> * eselect python list
>
> I get
>
> Available Python interpreters:
> *[1] * python2.6
> *[2] * python2.7
> *[3] * python3.1
> *[4] * python3.2 *
> </QUOTE>
>
> which shows python3.2 as the system wide default.
>
> * It's been my understanding ever since we first emerged any
> python-3.x version that we were not supposed to set any version of
> python3 as the system wide default. On all of my systems I have
> something like this:
>
> c2stable ~ # eselect python list
> Available Python interpreters:
> *[1] * python2.7 *
> *[2] * python3.2
> c2stable ~ # eselect python list --python2
> Available Python 2 interpreters:
> *[1] * python2.7 *
> c2stable ~ # eselect python list --python3
> Available Python 3 interpreters:
> *[1] * python3.2 *
> c2stable ~ #
>
> * Now, like Paul Hartman I didn't have any trouble building and
> running Hydrogen as a Jack client. It works just fine for me. However
> no one else seemed to have picked up on Meino's configuration which
> makes me wonder if I missed the memo to make the 3.x version of the
> system wide default.
>
> * What is the current best practice in this area?
>
> Cheers,
> Mark
>

I still have 2.7 set as default, but even after changing it to 3.2
that package still builds for me (and still shows linux2 not linux3
when it is emerging). The only overlays I use are nx and vmware.
 
Old 02-19-2012, 06:24 AM
 
Default python 2.x vs 3.x

Mark Knecht <markknecht@gmail.com> [12-02-19 03:13]:
> In a current thread started by Meino where he is having trouble
> emerging hydrogen he reported the following quoted data to Neil. I
> don't believe Neil has responded yet but Meino's data brought me back
> to a question I've meant to ask for a while so I'll take this
> opportunity.
>
> From Meino:
>
> <QUOTE>
> With
>
> eselect python list
>
> I get
>
> Available Python interpreters:
> [1] python2.6
> [2] python2.7
> [3] python3.1
> [4] python3.2 *
> </QUOTE>
>
> which shows python3.2 as the system wide default.
>
> It's been my understanding ever since we first emerged any
> python-3.x version that we were not supposed to set any version of
> python3 as the system wide default. On all of my systems I have
> something like this:
>
> c2stable ~ # eselect python list
> Available Python interpreters:
> [1] python2.7 *
> [2] python3.2
> c2stable ~ # eselect python list --python2
> Available Python 2 interpreters:
> [1] python2.7 *
> c2stable ~ # eselect python list --python3
> Available Python 3 interpreters:
> [1] python3.2 *
> c2stable ~ #
>
> Now, like Paul Hartman I didn't have any trouble building and
> running Hydrogen as a Jack client. It works just fine for me. However
> no one else seemed to have picked up on Meino's configuration which
> makes me wonder if I missed the memo to make the 3.x version of the
> system wide default.
>
> What is the current best practice in this area?
>
> Cheers,
> Mark
>

Hi Mark,

after a lot of revdep-rebuilds and unresolved (or over-resolved)
references hydrogen builds fine. TADA!
That is very nice ! )

Thank you very much for all your help.

Unfortunately the svn-build of blender builds, but
the executable only prints:

Fatal Python error: Py_Initialize: Unable to get the locale encoding
LookupError: no codec search functions registered: can't find encoding
[1] 20570 abort blender -noaudio

Does anyone has built a daily snapshot of the svn blender successfully
against the systemwide python 3.2. ?

How can I get blender to work?

Cheers
mcc
 
Old 02-19-2012, 02:48 PM
Mark Knecht
 
Default python 2.x vs 3.x

On Sat, Feb 18, 2012 at 11:24 PM, <meino.cramer@gmx.de> wrote:
> Mark Knecht <markknecht@gmail.com> [12-02-19 03:13]:
>> In a current thread started by Meino where he is having trouble
>> emerging hydrogen he reported the following quoted data to Neil. I
>> don't believe Neil has responded yet but Meino's data brought me back
>> to a question I've meant to ask for a while so I'll take this
>> opportunity.
>>
>> From Meino:
>>
>> <QUOTE>
>> With
>>
>> * *eselect python list
>>
>> I get
>>
>> Available Python interpreters:
>> *[1] * python2.6
>> *[2] * python2.7
>> *[3] * python3.1
>> *[4] * python3.2 *
>> </QUOTE>
>>
>> which shows python3.2 as the system wide default.
>>
>> * *It's been my understanding ever since we first emerged any
>> python-3.x version that we were not supposed to set any version of
>> python3 as the system wide default. On all of my systems I have
>> something like this:
>>
>> c2stable ~ # eselect python list
>> Available Python interpreters:
>> * [1] * python2.7 *
>> * [2] * python3.2
>> c2stable ~ # eselect python list --python2
>> Available Python 2 interpreters:
>> * [1] * python2.7 *
>> c2stable ~ # eselect python list --python3
>> Available Python 3 interpreters:
>> * [1] * python3.2 *
>> c2stable ~ #
>>
>> * *Now, like Paul Hartman I didn't have any trouble building and
>> running Hydrogen as a Jack client. It works just fine for me. However
>> no one else seemed to have picked up on Meino's configuration which
>> makes me wonder if I missed the memo to make the 3.x version of the
>> system wide default.
>>
>> * *What is the current best practice in this area?
>>
>> Cheers,
>> Mark
>>
>
> Hi Mark,
>
> after a lot of revdep-rebuilds and unresolved (or over-resolved)
> references hydrogen builds fine. TADA!
> That is very nice ! )
>
> Thank you very much for all your help.
>
> Unfortunately the svn-build of blender builds, but
> the executable only prints:
>
> * *Fatal Python error: Py_Initialize: Unable to get the locale encoding
> * *LookupError: no codec search functions registered: can't find encoding
> * *[1] * *20570 abort * * *blender -noaudio
>
> Does anyone has built a daily snapshot of the svn blender successfully
> against the systemwide python 3.2. ?
>
> How can I get blender to work?
>
> Cheers
> mcc

Meino,
First, congrats on getting Hydrogen going. May your life be full of
head banging drum riff all day & night long.

Now, can you verify that the system wide python setting was in fact
what made it build on your system? I know you were doing lots and lots
of things. Was switching this back to 2.7 the thing that allowed
Hydrogen to build for you?

As for Blender I really don't know what to do as I've never run it.
Are you building Blender from an overlay or standard portage? If it's
standard portage, and if the ebuild maintainer hasn't specifically
said that you have to use 3.x then should a bug report be filed?

That may make no sense on other information you posted. I really
haven't paid any attention to that part. Sorry.

Glad Hydrogen is working for you.

Cheers,
Mark
 
Old 02-19-2012, 03:37 PM
 
Default python 2.x vs 3.x

Mark Knecht <markknecht@gmail.com> [12-02-19 16:52]:
> On Sat, Feb 18, 2012 at 11:24 PM, <meino.cramer@gmx.de> wrote:
> > Mark Knecht <markknecht@gmail.com> [12-02-19 03:13]:
> >> In a current thread started by Meino where he is having trouble
> >> emerging hydrogen he reported the following quoted data to Neil. I
> >> don't believe Neil has responded yet but Meino's data brought me back
> >> to a question I've meant to ask for a while so I'll take this
> >> opportunity.
> >>
> >> From Meino:
> >>
> >> <QUOTE>
> >> With
> >>
> >> * *eselect python list
> >>
> >> I get
> >>
> >> Available Python interpreters:
> >> *[1] * python2.6
> >> *[2] * python2.7
> >> *[3] * python3.1
> >> *[4] * python3.2 *
> >> </QUOTE>
> >>
> >> which shows python3.2 as the system wide default.
> >>
> >> * *It's been my understanding ever since we first emerged any
> >> python-3.x version that we were not supposed to set any version of
> >> python3 as the system wide default. On all of my systems I have
> >> something like this:
> >>
> >> c2stable ~ # eselect python list
> >> Available Python interpreters:
> >> * [1] * python2.7 *
> >> * [2] * python3.2
> >> c2stable ~ # eselect python list --python2
> >> Available Python 2 interpreters:
> >> * [1] * python2.7 *
> >> c2stable ~ # eselect python list --python3
> >> Available Python 3 interpreters:
> >> * [1] * python3.2 *
> >> c2stable ~ #
> >>
> >> * *Now, like Paul Hartman I didn't have any trouble building and
> >> running Hydrogen as a Jack client. It works just fine for me. However
> >> no one else seemed to have picked up on Meino's configuration which
> >> makes me wonder if I missed the memo to make the 3.x version of the
> >> system wide default.
> >>
> >> * *What is the current best practice in this area?
> >>
> >> Cheers,
> >> Mark
> >>
> >
> > Hi Mark,
> >
> > after a lot of revdep-rebuilds and unresolved (or over-resolved)
> > references hydrogen builds fine. TADA!
> > That is very nice ! )
> >
> > Thank you very much for all your help.
> >
> > Unfortunately the svn-build of blender builds, but
> > the executable only prints:
> >
> > * *Fatal Python error: Py_Initialize: Unable to get the locale encoding
> > * *LookupError: no codec search functions registered: can't find encoding
> > * *[1] * *20570 abort * * *blender -noaudio
> >
> > Does anyone has built a daily snapshot of the svn blender successfully
> > against the systemwide python 3.2. ?
> >
> > How can I get blender to work?
> >
> > Cheers
> > mcc
>
> Meino,
> First, congrats on getting Hydrogen going. May your life be full of
> head banging drum riff all day & night long.
>
> Now, can you verify that the system wide python setting was in fact
> what made it build on your system? I know you were doing lots and lots
> of things. Was switching this back to 2.7 the thing that allowed
> Hydrogen to build for you?
>
> As for Blender I really don't know what to do as I've never run it.
> Are you building Blender from an overlay or standard portage? If it's
> standard portage, and if the ebuild maintainer hasn't specifically
> said that you have to use 3.x then should a bug report be filed?
>
> That may make no sense on other information you posted. I really
> haven't paid any attention to that part. Sorry.
>
> Glad Hydrogen is working for you.
>
> Cheers,
> Mark
>

Hi Mark,



currently the rest of my gentoo system is banging my head... )))



I did it the hard way:
I threw away the installation of python-3.2 in /usr/local which I need
to compile blender. Effect: Blender does no longer build.

I removed all python installation from my system except of the one
emerge uses.

I did a revdep-rebuild -pv to see, what applications and libs depends
on what version of python.

I filtered out all package which looks like libs or things used by
other programs and tried to build them against python 3.2: Some failed

I reinstalled python all versions of python, which were needed from
the dependencies shown by revdep rebuild.

With eselect python I set it to python 2.7.

I rebuild hydrogen, which wasn't confused by linux3 setting from out
space (plan9, I think).

Blender now builds and runs. The trick was, that the system wide
python 3.2 (which blender needs) uses lib64 while the previously
under /usr/local installed one uses lib as the directory where its
own python code is store.

I build blender by myself. The pure vanilla code, freshly taken from
the developpers svn repository. No patch, no tweak. The real thing
))

Unfortunately blender spit out messages, that it is built against
libpng-1.2.27 ... and the whole systems only contains libpng-1.5*.

Currently I have no clue, what the reasons fro this is. Unfortunately
the CUDE renderer fails to do its job. I can start blender...but not
really much more.

This was a day in deep hack mode. Strace was my friend...as so often.

Will see how I can fix the rest of the problems.

The main problem of builing hydrogen was the python under /usr/local
I think...

Will see what hick up next ....

Cheers,
Meino
 
Old 02-19-2012, 05:53 PM
Mark Knecht
 
Default python 2.x vs 3.x

On Sun, Feb 19, 2012 at 8:37 AM, <meino.cramer@gmx.de> wrote:
> Mark Knecht <markknecht@gmail.com> [12-02-19 16:52]:
>> On Sat, Feb 18, 2012 at 11:24 PM, *<meino.cramer@gmx.de> wrote:
>> > Mark Knecht <markknecht@gmail.com> [12-02-19 03:13]:
>> >> In a current thread started by Meino where he is having trouble
>> >> emerging hydrogen he reported the following quoted data to Neil. I
>> >> don't believe Neil has responded yet but Meino's data brought me back
>> >> to a question I've meant to ask for a while so I'll take this
>> >> opportunity.
>> >>
>> >> From Meino:
>> >>
>> >> <QUOTE>
>> >> With
>> >>
>> >> * *eselect python list
>> >>
>> >> I get
>> >>
>> >> Available Python interpreters:
>> >> *[1] * python2.6
>> >> *[2] * python2.7
>> >> *[3] * python3.1
>> >> *[4] * python3.2 *
>> >> </QUOTE>
>> >>
>> >> which shows python3.2 as the system wide default.
>> >>
>> >> * *It's been my understanding ever since we first emerged any
>> >> python-3.x version that we were not supposed to set any version of
>> >> python3 as the system wide default. On all of my systems I have
>> >> something like this:
>> >>
>> >> c2stable ~ # eselect python list
>> >> Available Python interpreters:
>> >> * [1] * python2.7 *
>> >> * [2] * python3.2
>> >> c2stable ~ # eselect python list --python2
>> >> Available Python 2 interpreters:
>> >> * [1] * python2.7 *
>> >> c2stable ~ # eselect python list --python3
>> >> Available Python 3 interpreters:
>> >> * [1] * python3.2 *
>> >> c2stable ~ #
>> >>
>> >> * *Now, like Paul Hartman I didn't have any trouble building and
>> >> running Hydrogen as a Jack client. It works just fine for me. However
>> >> no one else seemed to have picked up on Meino's configuration which
>> >> makes me wonder if I missed the memo to make the 3.x version of the
>> >> system wide default.
>> >>
>> >> * *What is the current best practice in this area?
>> >>
>> >> Cheers,
>> >> Mark
>> >>
>> >
>> > Hi Mark,
>> >
>> > after a lot of revdep-rebuilds and unresolved (or over-resolved)
>> > references hydrogen builds fine. TADA!
>> > That is very nice ! )
>> >
>> > Thank you very much for all your help.
>> >
>> > Unfortunately the svn-build of blender builds, but
>> > the executable only prints:
>> >
>> > * *Fatal Python error: Py_Initialize: Unable to get the locale encoding
>> > * *LookupError: no codec search functions registered: can't find encoding
>> > * *[1] * *20570 abort * * *blender -noaudio
>> >
>> > Does anyone has built a daily snapshot of the svn blender successfully
>> > against the systemwide python 3.2. ?
>> >
>> > How can I get blender to work?
>> >
>> > Cheers
>> > mcc
>>
>> Meino,
>> * *First, congrats on getting Hydrogen going. May your life be full of
>> head banging drum riff all day & night long.
>>
>> * *Now, can you verify that the system wide python setting was in fact
>> what made it build on your system? I know you were doing lots and lots
>> of things. Was switching this back to 2.7 the thing that allowed
>> Hydrogen to build for you?
>>
>> * *As for Blender I really don't know what to do as I've never run it.
>> Are you building Blender from an overlay or standard portage? If it's
>> standard portage, and if the ebuild maintainer hasn't specifically
>> said that you have to use 3.x then should a bug report be filed?
>>
>> * *That may make no sense on other information you posted. I really
>> haven't paid any attention to that part. Sorry.
>>
>> * *Glad Hydrogen is working for you.
>>
>> Cheers,
>> Mark
>>
>
> Hi Mark,
>
>
>
> currently the rest of my gentoo system is banging my head... )))
>
>
>
> I did it the hard way:
> I threw away the installation of python-3.2 in /usr/local which I need
> to compile blender. Effect: Blender does no longer build.
>
> I removed all python installation from my system except of the one
> emerge uses.
>
> I did a revdep-rebuild -pv to see, what applications and libs depends
> on what version of python.
>
> I filtered out all package which looks like libs or things used by
> other programs and tried to build them against python 3.2: Some failed
>
> I reinstalled python all versions of python, which were needed from
> the dependencies shown by revdep rebuild.
>
> With eselect python I set it to python 2.7.
>
> I rebuild hydrogen, which wasn't confused by linux3 setting from out
> space (plan9, I think).
>
> Blender now builds and runs. The trick was, that the system wide
> python 3.2 (which blender needs) uses lib64 while the previously
> under /usr/local installed one uses lib as the directory where its
> own python code is store.
>
> I build blender by myself. The pure vanilla code, freshly taken from
> the developpers svn repository. No patch, no tweak. The real thing
> ))
>
> Unfortunately blender spit out messages, that it is built against
> libpng-1.2.27 ... and the whole systems only contains libpng-1.5*.
>
> Currently I have no clue, what the reasons fro this is. Unfortunately
> the CUDE renderer fails to do its job. I can start blender...but not
> really much more.
>
> This was a day in deep hack mode. Strace was my friend...as so often.
>
> Will see how I can fix the rest of the problems.
>
> The main problem of builing hydrogen was the python under /usr/local
> I think...
>
> Will see what hick up next ....
>
> Cheers,
> Meino

Meino,
Based on this thread's setup of python I had no trouble building
the stable version of blender offered in portage. I don't know how to
use blender but I had no trouble starting the app and getting the GUI
up.

If you are not able to duplicate this then I would like to know.
Are you using the stable version or something newer? If newer have you
tried the stable version? If you can build the stable version then you
have a basis to file bug reports on anything newer that doesn't work.
If you cannot build the stable version then we need to determine why
on my audio application laptop where I'm running Jack+ Rosegarden +
qjackctl + hydrogen + etc., and now blender, you would be having
trouble on a smilar machine.

Cheers,
Mark

slinky ~ # emerge -DuN blender
Calculating dependencies... done!
>>> Verifying ebuild manifests
>>> Starting parallel fetch
>>> Emerging (1 of 6) media-libs/ilmbase-1.0.2
>>> Emerging (2 of 6) media-libs/lcms-2.3
>>> Emerging (3 of 6) media-libs/ftgl-2.1.3_rc5
>>> Installing (1 of 6) media-libs/ilmbase-1.0.2
>>> Emerging (4 of 6) media-libs/openexr-1.7.0
>>> Installing (2 of 6) media-libs/lcms-2.3
>>> Installing (3 of 6) media-libs/ftgl-2.1.3_rc5
>>> Emerging (5 of 6) media-libs/openjpeg-1.4-r1
>>> Installing (5 of 6) media-libs/openjpeg-1.4-r1
>>> Installing (4 of 6) media-libs/openexr-1.7.0
>>> Emerging (6 of 6) media-gfx/blender-2.49b-r2
>>> Installing (6 of 6) media-gfx/blender-2.49b-r2
>>> Recording media-gfx/blender in "world" favorites file...
>>> Jobs: 6 of 6 complete Load avg: 8.96, 5.21, 2.35

* Messages for package media-gfx/blender-2.49b-r2:

* blender uses python integration. As such, may have some
* inherit risks with running unknown python scripting.
*
* CVE-2008-1103-1.patch has been removed as it interferes
* with autosave undo features. Up stream blender coders
* have not addressed the CVE issue as the status is still
* a CANDIDATE and not CONFIRMED.
*
* It is recommended to change your blender temp directory
* from /tmp to ~tmp or another tmp file under your home
* directory. This can be done by starting blender, then
* dragging the main menu down do display all paths.
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.

* GNU info directory index is up-to-date.
slinky ~ #
 
Old 02-19-2012, 06:10 PM
 
Default python 2.x vs 3.x

Mark Knecht <markknecht@gmail.com> [12-02-19 19:56]:
> On Sun, Feb 19, 2012 at 8:37 AM, <meino.cramer@gmx.de> wrote:
> > Mark Knecht <markknecht@gmail.com> [12-02-19 16:52]:
> >> On Sat, Feb 18, 2012 at 11:24 PM, *<meino.cramer@gmx.de> wrote:
> >> > Mark Knecht <markknecht@gmail.com> [12-02-19 03:13]:
> >> >> In a current thread started by Meino where he is having trouble
> >> >> emerging hydrogen he reported the following quoted data to Neil. I
> >> >> don't believe Neil has responded yet but Meino's data brought me back
> >> >> to a question I've meant to ask for a while so I'll take this
> >> >> opportunity.
> >> >>
> >> >> From Meino:
> >> >>
> >> >> <QUOTE>
> >> >> With
> >> >>
> >> >> * *eselect python list
> >> >>
> >> >> I get
> >> >>
> >> >> Available Python interpreters:
> >> >> *[1] * python2.6
> >> >> *[2] * python2.7
> >> >> *[3] * python3.1
> >> >> *[4] * python3.2 *
> >> >> </QUOTE>
> >> >>
> >> >> which shows python3.2 as the system wide default.
> >> >>
> >> >> * *It's been my understanding ever since we first emerged any
> >> >> python-3.x version that we were not supposed to set any version of
> >> >> python3 as the system wide default. On all of my systems I have
> >> >> something like this:
> >> >>
> >> >> c2stable ~ # eselect python list
> >> >> Available Python interpreters:
> >> >> * [1] * python2.7 *
> >> >> * [2] * python3.2
> >> >> c2stable ~ # eselect python list --python2
> >> >> Available Python 2 interpreters:
> >> >> * [1] * python2.7 *
> >> >> c2stable ~ # eselect python list --python3
> >> >> Available Python 3 interpreters:
> >> >> * [1] * python3.2 *
> >> >> c2stable ~ #
> >> >>
> >> >> * *Now, like Paul Hartman I didn't have any trouble building and
> >> >> running Hydrogen as a Jack client. It works just fine for me. However
> >> >> no one else seemed to have picked up on Meino's configuration which
> >> >> makes me wonder if I missed the memo to make the 3.x version of the
> >> >> system wide default.
> >> >>
> >> >> * *What is the current best practice in this area?
> >> >>
> >> >> Cheers,
> >> >> Mark
> >> >>
> >> >
> >> > Hi Mark,
> >> >
> >> > after a lot of revdep-rebuilds and unresolved (or over-resolved)
> >> > references hydrogen builds fine. TADA!
> >> > That is very nice ! )
> >> >
> >> > Thank you very much for all your help.
> >> >
> >> > Unfortunately the svn-build of blender builds, but
> >> > the executable only prints:
> >> >
> >> > * *Fatal Python error: Py_Initialize: Unable to get the locale encoding
> >> > * *LookupError: no codec search functions registered: can't find encoding
> >> > * *[1] * *20570 abort * * *blender -noaudio
> >> >
> >> > Does anyone has built a daily snapshot of the svn blender successfully
> >> > against the systemwide python 3.2. ?
> >> >
> >> > How can I get blender to work?
> >> >
> >> > Cheers
> >> > mcc
> >>
> >> Meino,
> >> * *First, congrats on getting Hydrogen going. May your life be full of
> >> head banging drum riff all day & night long.
> >>
> >> * *Now, can you verify that the system wide python setting was in fact
> >> what made it build on your system? I know you were doing lots and lots
> >> of things. Was switching this back to 2.7 the thing that allowed
> >> Hydrogen to build for you?
> >>
> >> * *As for Blender I really don't know what to do as I've never run it.
> >> Are you building Blender from an overlay or standard portage? If it's
> >> standard portage, and if the ebuild maintainer hasn't specifically
> >> said that you have to use 3.x then should a bug report be filed?
> >>
> >> * *That may make no sense on other information you posted. I really
> >> haven't paid any attention to that part. Sorry.
> >>
> >> * *Glad Hydrogen is working for you.
> >>
> >> Cheers,
> >> Mark
> >>
> >
> > Hi Mark,
> >
> >
> >
> > currently the rest of my gentoo system is banging my head... )))
> >
> >
> >
> > I did it the hard way:
> > I threw away the installation of python-3.2 in /usr/local which I need
> > to compile blender. Effect: Blender does no longer build.
> >
> > I removed all python installation from my system except of the one
> > emerge uses.
> >
> > I did a revdep-rebuild -pv to see, what applications and libs depends
> > on what version of python.
> >
> > I filtered out all package which looks like libs or things used by
> > other programs and tried to build them against python 3.2: Some failed
> >
> > I reinstalled python all versions of python, which were needed from
> > the dependencies shown by revdep rebuild.
> >
> > With eselect python I set it to python 2.7.
> >
> > I rebuild hydrogen, which wasn't confused by linux3 setting from out
> > space (plan9, I think).
> >
> > Blender now builds and runs. The trick was, that the system wide
> > python 3.2 (which blender needs) uses lib64 while the previously
> > under /usr/local installed one uses lib as the directory where its
> > own python code is store.
> >
> > I build blender by myself. The pure vanilla code, freshly taken from
> > the developpers svn repository. No patch, no tweak. The real thing
> > ))
> >
> > Unfortunately blender spit out messages, that it is built against
> > libpng-1.2.27 ... and the whole systems only contains libpng-1.5*.
> >
> > Currently I have no clue, what the reasons fro this is. Unfortunately
> > the CUDE renderer fails to do its job. I can start blender...but not
> > really much more.
> >
> > This was a day in deep hack mode. Strace was my friend...as so often.
> >
> > Will see how I can fix the rest of the problems.
> >
> > The main problem of builing hydrogen was the python under /usr/local
> > I think...
> >
> > Will see what hick up next ....
> >
> > Cheers,
> > Meino
>
> Meino,
> Based on this thread's setup of python I had no trouble building
> the stable version of blender offered in portage. I don't know how to
> use blender but I had no trouble starting the app and getting the GUI
> up.
>
> If you are not able to duplicate this then I would like to know.
> Are you using the stable version or something newer? If newer have you
> tried the stable version? If you can build the stable version then you
> have a basis to file bug reports on anything newer that doesn't work.
> If you cannot build the stable version then we need to determine why
> on my audio application laptop where I'm running Jack+ Rosegarden +
> qjackctl + hydrogen + etc., and now blender, you would be having
> trouble on a smilar machine.
>
> Cheers,
> Mark
>
> slinky ~ # emerge -DuN blender
> Calculating dependencies... done!
> >>> Verifying ebuild manifests
> >>> Starting parallel fetch
> >>> Emerging (1 of 6) media-libs/ilmbase-1.0.2
> >>> Emerging (2 of 6) media-libs/lcms-2.3
> >>> Emerging (3 of 6) media-libs/ftgl-2.1.3_rc5
> >>> Installing (1 of 6) media-libs/ilmbase-1.0.2
> >>> Emerging (4 of 6) media-libs/openexr-1.7.0
> >>> Installing (2 of 6) media-libs/lcms-2.3
> >>> Installing (3 of 6) media-libs/ftgl-2.1.3_rc5
> >>> Emerging (5 of 6) media-libs/openjpeg-1.4-r1
> >>> Installing (5 of 6) media-libs/openjpeg-1.4-r1
> >>> Installing (4 of 6) media-libs/openexr-1.7.0
> >>> Emerging (6 of 6) media-gfx/blender-2.49b-r2
> >>> Installing (6 of 6) media-gfx/blender-2.49b-r2
> >>> Recording media-gfx/blender in "world" favorites file...
> >>> Jobs: 6 of 6 complete Load avg: 8.96, 5.21, 2.35
>
> * Messages for package media-gfx/blender-2.49b-r2:
>
> * blender uses python integration. As such, may have some
> * inherit risks with running unknown python scripting.
> *
> * CVE-2008-1103-1.patch has been removed as it interferes
> * with autosave undo features. Up stream blender coders
> * have not addressed the CVE issue as the status is still
> * a CANDIDATE and not CONFIRMED.
> *
> * It is recommended to change your blender temp directory
> * from /tmp to ~tmp or another tmp file under your home
> * directory. This can be done by starting blender, then
> * dragging the main menu down do display all paths.
> >>> Auto-cleaning packages...
>
> >>> No outdated packages were found on your system.
>
> * GNU info directory index is up-to-date.
> slinky ~ #
>


Hi Mark,

thank you very much for all your helping and installing
applications!!!

As I wrote:

I build blender by myself. The pure vanilla code, freshly taken from
the developpers svn repository. No patch, no tweak. The real thing

I am using the developpers source code tree, which is 2.62. Blender
2.49 is a very old version of blender...

I can start blender (build successful), but currently it does not find
the GPU of my graphic card on which blender should render. This seems
to be a bug in the nvidia driver...I have posted an according message
to the german blender mailinglist "blendpolis".

Since blender 2.62 is very much different from blender 2.49 (2.49
cannot render on the GPU of a graphic card and has no physically
correct render engine like blender 2.62) results from building/using
blender 2.49 cannot be used to analyze bugs with blender 2.62.
Furthermore they both use different versions of python.

Will see what finally is the bug...

Thank you for your help and testing, Mark!

Cheers
Meino
 
Old 02-19-2012, 06:47 PM
Mark Knecht
 
Default python 2.x vs 3.x

On Sun, Feb 19, 2012 at 11:10 AM, <meino.cramer@gmx.de> wrote:
> Mark Knecht <markknecht@gmail.com> [12-02-19 19:56]:
>> On Sun, Feb 19, 2012 at 8:37 AM, *<meino.cramer@gmx.de> wrote:
>> > Mark Knecht <markknecht@gmail.com> [12-02-19 16:52]:
>> >> On Sat, Feb 18, 2012 at 11:24 PM, *<meino.cramer@gmx.de> wrote:
>> >> > Mark Knecht <markknecht@gmail.com> [12-02-19 03:13]:
>> >> >> In a current thread started by Meino where he is having trouble
>> >> >> emerging hydrogen he reported the following quoted data to Neil. I
>> >> >> don't believe Neil has responded yet but Meino's data brought me back
>> >> >> to a question I've meant to ask for a while so I'll take this
>> >> >> opportunity.
>> >> >>
>> >> >> From Meino:
>> >> >>
>> >> >> <QUOTE>
>> >> >> With
>> >> >>
>> >> >> * *eselect python list
>> >> >>
>> >> >> I get
>> >> >>
>> >> >> Available Python interpreters:
>> >> >> *[1] * python2.6
>> >> >> *[2] * python2.7
>> >> >> *[3] * python3.1
>> >> >> *[4] * python3.2 *
>> >> >> </QUOTE>
>> >> >>
>> >> >> which shows python3.2 as the system wide default.
>> >> >>
>> >> >> * *It's been my understanding ever since we first emerged any
>> >> >> python-3.x version that we were not supposed to set any version of
>> >> >> python3 as the system wide default. On all of my systems I have
>> >> >> something like this:
>> >> >>
>> >> >> c2stable ~ # eselect python list
>> >> >> Available Python interpreters:
>> >> >> * [1] * python2.7 *
>> >> >> * [2] * python3.2
>> >> >> c2stable ~ # eselect python list --python2
>> >> >> Available Python 2 interpreters:
>> >> >> * [1] * python2.7 *
>> >> >> c2stable ~ # eselect python list --python3
>> >> >> Available Python 3 interpreters:
>> >> >> * [1] * python3.2 *
>> >> >> c2stable ~ #
>> >> >>
>> >> >> * *Now, like Paul Hartman I didn't have any trouble building and
>> >> >> running Hydrogen as a Jack client. It works just fine for me. However
>> >> >> no one else seemed to have picked up on Meino's configuration which
>> >> >> makes me wonder if I missed the memo to make the 3.x version of the
>> >> >> system wide default.
>> >> >>
>> >> >> * *What is the current best practice in this area?
>> >> >>
>> >> >> Cheers,
>> >> >> Mark
>> >> >>
>> >> >
>> >> > Hi Mark,
>> >> >
>> >> > after a lot of revdep-rebuilds and unresolved (or over-resolved)
>> >> > references hydrogen builds fine. TADA!
>> >> > That is very nice ! )
>> >> >
>> >> > Thank you very much for all your help.
>> >> >
>> >> > Unfortunately the svn-build of blender builds, but
>> >> > the executable only prints:
>> >> >
>> >> > * *Fatal Python error: Py_Initialize: Unable to get the locale encoding
>> >> > * *LookupError: no codec search functions registered: can't find encoding
>> >> > * *[1] * *20570 abort * * *blender -noaudio
>> >> >
>> >> > Does anyone has built a daily snapshot of the svn blender successfully
>> >> > against the systemwide python 3.2. ?
>> >> >
>> >> > How can I get blender to work?
>> >> >
>> >> > Cheers
>> >> > mcc
>> >>
>> >> Meino,
>> >> * *First, congrats on getting Hydrogen going. May your life be full of
>> >> head banging drum riff all day & night long.
>> >>
>> >> * *Now, can you verify that the system wide python setting was in fact
>> >> what made it build on your system? I know you were doing lots and lots
>> >> of things. Was switching this back to 2.7 the thing that allowed
>> >> Hydrogen to build for you?
>> >>
>> >> * *As for Blender I really don't know what to do as I've never run it.
>> >> Are you building Blender from an overlay or standard portage? If it's
>> >> standard portage, and if the ebuild maintainer hasn't specifically
>> >> said that you have to use 3.x then should a bug report be filed?
>> >>
>> >> * *That may make no sense on other information you posted. I really
>> >> haven't paid any attention to that part. Sorry.
>> >>
>> >> * *Glad Hydrogen is working for you.
>> >>
>> >> Cheers,
>> >> Mark
>> >>
>> >
>> > Hi Mark,
>> >
>> >
>> >
>> > currently the rest of my gentoo system is banging my head... )))
>> >
>> >
>> >
>> > I did it the hard way:
>> > I threw away the installation of python-3.2 in /usr/local which I need
>> > to compile blender. Effect: Blender does no longer build.
>> >
>> > I removed all python installation from my system except of the one
>> > emerge uses.
>> >
>> > I did a revdep-rebuild -pv to see, what applications and libs depends
>> > on what version of python.
>> >
>> > I filtered out all package which looks like libs or things used by
>> > other programs and tried to build them against python 3.2: Some failed
>> >
>> > I reinstalled python all versions of python, which were needed from
>> > the dependencies shown by revdep rebuild.
>> >
>> > With eselect python I set it to python 2.7.
>> >
>> > I rebuild hydrogen, which wasn't confused by linux3 setting from out
>> > space (plan9, I think).
>> >
>> > Blender now builds and runs. The trick was, that the system wide
>> > python 3.2 (which blender needs) uses lib64 while the previously
>> > under /usr/local installed one uses lib as the directory where its
>> > own python code is store.
>> >
>> > I build blender by myself. The pure vanilla code, freshly taken from
>> > the developpers svn repository. No patch, no tweak. The real thing
>> > ))
>> >
>> > Unfortunately blender spit out messages, that it is built against
>> > libpng-1.2.27 ... and the whole systems only contains libpng-1.5*.
>> >
>> > Currently I have no clue, what the reasons fro this is. Unfortunately
>> > the CUDE renderer fails to do its job. I can start blender...but not
>> > really much more.
>> >
>> > This was a day in deep hack mode. Strace was my friend...as so often.
>> >
>> > Will see how I can fix the rest of the problems.
>> >
>> > The main problem of builing hydrogen was the python under /usr/local
>> > I think...
>> >
>> > Will see what hick up next ....
>> >
>> > Cheers,
>> > Meino
>>
>> Meino,
>> * *Based on this thread's setup of python I had no trouble building
>> the stable version of blender offered in portage. I don't know how to
>> use blender but I had no trouble starting the app and getting the GUI
>> up.
>>
>> * *If you are not able to duplicate this then I would like to know.
>> Are you using the stable version or something newer? If newer have you
>> tried the stable version? If you can build the stable version then you
>> have a basis to file bug reports on anything newer that doesn't work.
>> If you cannot build the stable version then we need to determine why
>> on my audio application laptop where I'm running Jack+ Rosegarden +
>> qjackctl + hydrogen + etc., and now blender, you would be having
>> trouble on a smilar machine.
>>
>> Cheers,
>> Mark
>>
>> slinky ~ # emerge -DuN blender
>> Calculating dependencies... done!
>> >>> Verifying ebuild manifests
>> >>> Starting parallel fetch
>> >>> Emerging (1 of 6) media-libs/ilmbase-1.0.2
>> >>> Emerging (2 of 6) media-libs/lcms-2.3
>> >>> Emerging (3 of 6) media-libs/ftgl-2.1.3_rc5
>> >>> Installing (1 of 6) media-libs/ilmbase-1.0.2
>> >>> Emerging (4 of 6) media-libs/openexr-1.7.0
>> >>> Installing (2 of 6) media-libs/lcms-2.3
>> >>> Installing (3 of 6) media-libs/ftgl-2.1.3_rc5
>> >>> Emerging (5 of 6) media-libs/openjpeg-1.4-r1
>> >>> Installing (5 of 6) media-libs/openjpeg-1.4-r1
>> >>> Installing (4 of 6) media-libs/openexr-1.7.0
>> >>> Emerging (6 of 6) media-gfx/blender-2.49b-r2
>> >>> Installing (6 of 6) media-gfx/blender-2.49b-r2
>> >>> Recording media-gfx/blender in "world" favorites file...
>> >>> Jobs: 6 of 6 complete * * * * * * * * * * * * * Load avg: 8.96, 5.21, 2.35
>>
>> ** Messages for package media-gfx/blender-2.49b-r2:
>>
>> ** blender uses python integration. *As such, may have some
>> ** inherit risks with running unknown python scripting.
>> **
>> ** CVE-2008-1103-1.patch has been removed as it interferes
>> ** with autosave undo features. Up stream blender coders
>> ** have not addressed the CVE issue as the status is still
>> ** a CANDIDATE and not CONFIRMED.
>> **
>> ** It is recommended to change your blender temp directory
>> ** from /tmp to ~tmp or another tmp file under your home
>> ** directory. This can be done by starting blender, then
>> ** dragging the main menu down do display all paths.
>> >>> Auto-cleaning packages...
>>
>> >>> No outdated packages were found on your system.
>>
>> ** GNU info directory index is up-to-date.
>> slinky ~ #
>>
>
>
> Hi Mark,
>
> thank you very much for all your helping and installing
> applications!!!
>
> As I wrote:
>
> * *I build blender by myself. The pure vanilla code, freshly taken from
> * *the developpers svn repository. No patch, no tweak. The real thing
>
> I am using the developpers source code tree, which is 2.62. Blender
> 2.49 is a very old version of blender...
>
> I can start blender (build successful), but currently it does not find
> the GPU of my graphic card on which blender should render. This seems
> to be a bug in the nvidia driver...I have posted an according message
> to the german blender mailinglist "blendpolis".
>
> Since blender 2.62 is very much different from blender 2.49 (2.49
> cannot render on the GPU of a graphic card and has no physically
> correct render engine like blender 2.62) results from building/using
> blender 2.49 cannot be used to analyze bugs with blender 2.62.
> Furthermore they both use different versions of python.
>
> Will see what finally is the bug...
>
> Thank you for your help and testing, Mark!
>
> Cheers
> Meino

I understand new versions have new features. That's not really my
point. The real issue for this list (in my mind) is what can be done
on *Gentoo*, both with stable AND testing versions of software
supported by the Gentoo devs.

At this point, on my machine, I can build the stable version. Can you
build that version?

While writing this response I have now build the ~amd64 version of
blender which at this time is 2.60a. Again, I have no trouble starting
the GUI. I don't know whether the version works very well. (Or at
all!) I also don't know if this version has all the features you want
from 2.62, but I'm fairly sure 2.60a must be closer, correct?

My input to you, again, is please go about this the right way:

1) Build the stable version. Does it work.
2) Build the testing version. Does it work.
3) If both of those build but don't have the features you want or need
then file a new ebuild request to get it into standard portage and at
the same time look for an overlay that has one right now and try that.

At least, following some structured process like this, you have a
chance of knowing where he problems are and what _really_ needs to be
done in a minimal amount of time. I got this far in less than 60
minutes.

Good luck & cheers,
Mark


slinky ~ # emerge -DuN @world
Calculating dependencies... done!
>>> Verifying ebuild manifests
>>> Starting parallel fetch
>>> Emerging (1 of 3) media-libs/glew-1.6.0-r1
>>> Emerging (2 of 3) sci-physics/bullet-2.77
>>> Installing (1 of 3) media-libs/glew-1.6.0-r1
>>> Installing (2 of 3) sci-physics/bullet-2.77
>>> Emerging (3 of 3) media-gfx/blender-2.60a
>>> Installing (3 of 3) media-gfx/blender-2.60a
>>> Jobs: 3 of 3 complete Load avg: 8.68, 6.16, 2.74

* Messages for package media-gfx/blender-2.60a:

* Blender uses python integration. As such, may have some
* inherit risks with running unknown python scripting.
*
* It is recommended to change your blender temp directory
* from /tmp to /home/user/tmp or another tmp file under your
* home directory. This can be done by starting blender, then
* dragging the main menu down do display all paths.
*
* Blender has its own internal rendering engine but you
* can export to external renderers for image computation
* like: YafRay[1], sunflow[2], PovRay[3] and luxrender[4]
*
* If you need one of them just emerge it:
* [1] emerge -av media-gfx/yafray
* [2] emerge -av media-gfx/sunflow
* [3] emerge -av media-gfx/povray
* [4] emerge -av media-gfx/luxrender
*
* When setting the Blender paths with the User Preferences
* dialog box, remember to NOT declare your home's paths as:
* ~/.blender, but as: /home/user/.blender; in other words,
* DO NOT USE the tilde inside the paths, as Blender is not
* able to handle it, ignoring your customizations.
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.

* GNU info directory index is up-to-date.
* After world updates, it is important to remove obsolete packages with
* emerge --depclean. Refer to `man emerge` for more information.
slinky ~ #


Cheers,
Mark
 

Thread Tools




All times are GMT. The time now is 03:44 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org