Mark Knecht <markkne...@gmail.com> [12-02-19 19:56]:
> On Sun, Feb 19, 2012 at 8:37 AM, <meino.cra...@gmx.de> wrote:
> > Mark Knecht <markkne...@gmail.com> [12-02-19 16:52]:
> >> On Sat, Feb 18, 2012 at 11:24 PM, <meino.cra...@gmx.de> wrote:
> >> > Mark Knecht <markkne...@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
