1 |
Mark Knecht <markknecht@×××××.com> [12-02-19 19:56]: |
2 |
> On Sun, Feb 19, 2012 at 8:37 AM, <meino.cramer@×××.de> wrote: |
3 |
> > Mark Knecht <markknecht@×××××.com> [12-02-19 16:52]: |
4 |
> >> On Sat, Feb 18, 2012 at 11:24 PM, <meino.cramer@×××.de> wrote: |
5 |
> >> > Mark Knecht <markknecht@×××××.com> [12-02-19 03:13]: |
6 |
> >> >> In a current thread started by Meino where he is having trouble |
7 |
> >> >> emerging hydrogen he reported the following quoted data to Neil. I |
8 |
> >> >> don't believe Neil has responded yet but Meino's data brought me back |
9 |
> >> >> to a question I've meant to ask for a while so I'll take this |
10 |
> >> >> opportunity. |
11 |
> >> >> |
12 |
> >> >> From Meino: |
13 |
> >> >> |
14 |
> >> >> <QUOTE> |
15 |
> >> >> With |
16 |
> >> >> |
17 |
> >> >> eselect python list |
18 |
> >> >> |
19 |
> >> >> I get |
20 |
> >> >> |
21 |
> >> >> Available Python interpreters: |
22 |
> >> >> [1] python2.6 |
23 |
> >> >> [2] python2.7 |
24 |
> >> >> [3] python3.1 |
25 |
> >> >> [4] python3.2 * |
26 |
> >> >> </QUOTE> |
27 |
> >> >> |
28 |
> >> >> which shows python3.2 as the system wide default. |
29 |
> >> >> |
30 |
> >> >> It's been my understanding ever since we first emerged any |
31 |
> >> >> python-3.x version that we were not supposed to set any version of |
32 |
> >> >> python3 as the system wide default. On all of my systems I have |
33 |
> >> >> something like this: |
34 |
> >> >> |
35 |
> >> >> c2stable ~ # eselect python list |
36 |
> >> >> Available Python interpreters: |
37 |
> >> >> [1] python2.7 * |
38 |
> >> >> [2] python3.2 |
39 |
> >> >> c2stable ~ # eselect python list --python2 |
40 |
> >> >> Available Python 2 interpreters: |
41 |
> >> >> [1] python2.7 * |
42 |
> >> >> c2stable ~ # eselect python list --python3 |
43 |
> >> >> Available Python 3 interpreters: |
44 |
> >> >> [1] python3.2 * |
45 |
> >> >> c2stable ~ # |
46 |
> >> >> |
47 |
> >> >> Now, like Paul Hartman I didn't have any trouble building and |
48 |
> >> >> running Hydrogen as a Jack client. It works just fine for me. However |
49 |
> >> >> no one else seemed to have picked up on Meino's configuration which |
50 |
> >> >> makes me wonder if I missed the memo to make the 3.x version of the |
51 |
> >> >> system wide default. |
52 |
> >> >> |
53 |
> >> >> What is the current best practice in this area? |
54 |
> >> >> |
55 |
> >> >> Cheers, |
56 |
> >> >> Mark |
57 |
> >> >> |
58 |
> >> > |
59 |
> >> > Hi Mark, |
60 |
> >> > |
61 |
> >> > after a lot of revdep-rebuilds and unresolved (or over-resolved) |
62 |
> >> > references hydrogen builds fine. TADA! ;) |
63 |
> >> > That is very nice ! :)) |
64 |
> >> > |
65 |
> >> > Thank you very much for all your help. |
66 |
> >> > |
67 |
> >> > Unfortunately the svn-build of blender builds, but |
68 |
> >> > the executable only prints: |
69 |
> >> > |
70 |
> >> > Fatal Python error: Py_Initialize: Unable to get the locale encoding |
71 |
> >> > LookupError: no codec search functions registered: can't find encoding |
72 |
> >> > [1] 20570 abort blender -noaudio |
73 |
> >> > |
74 |
> >> > Does anyone has built a daily snapshot of the svn blender successfully |
75 |
> >> > against the systemwide python 3.2. ? |
76 |
> >> > |
77 |
> >> > How can I get blender to work? |
78 |
> >> > |
79 |
> >> > Cheers |
80 |
> >> > mcc |
81 |
> >> |
82 |
> >> Meino, |
83 |
> >> First, congrats on getting Hydrogen going. May your life be full of |
84 |
> >> head banging drum riff all day & night long. |
85 |
> >> |
86 |
> >> Now, can you verify that the system wide python setting was in fact |
87 |
> >> what made it build on your system? I know you were doing lots and lots |
88 |
> >> of things. Was switching this back to 2.7 the thing that allowed |
89 |
> >> Hydrogen to build for you? |
90 |
> >> |
91 |
> >> As for Blender I really don't know what to do as I've never run it. |
92 |
> >> Are you building Blender from an overlay or standard portage? If it's |
93 |
> >> standard portage, and if the ebuild maintainer hasn't specifically |
94 |
> >> said that you have to use 3.x then should a bug report be filed? |
95 |
> >> |
96 |
> >> That may make no sense on other information you posted. I really |
97 |
> >> haven't paid any attention to that part. Sorry. |
98 |
> >> |
99 |
> >> Glad Hydrogen is working for you. |
100 |
> >> |
101 |
> >> Cheers, |
102 |
> >> Mark |
103 |
> >> |
104 |
> > |
105 |
> > Hi Mark, |
106 |
> > |
107 |
> > :) |
108 |
> > |
109 |
> > currently the rest of my gentoo system is banging my head... ;)))) |
110 |
> > |
111 |
> > :) |
112 |
> > |
113 |
> > I did it the hard way: |
114 |
> > I threw away the installation of python-3.2 in /usr/local which I need |
115 |
> > to compile blender. Effect: Blender does no longer build. |
116 |
> > |
117 |
> > I removed all python installation from my system except of the one |
118 |
> > emerge uses. |
119 |
> > |
120 |
> > I did a revdep-rebuild -pv to see, what applications and libs depends |
121 |
> > on what version of python. |
122 |
> > |
123 |
> > I filtered out all package which looks like libs or things used by |
124 |
> > other programs and tried to build them against python 3.2: Some failed |
125 |
> > |
126 |
> > I reinstalled python all versions of python, which were needed from |
127 |
> > the dependencies shown by revdep rebuild. |
128 |
> > |
129 |
> > With eselect python I set it to python 2.7. |
130 |
> > |
131 |
> > I rebuild hydrogen, which wasn't confused by linux3 setting from out |
132 |
> > space (plan9, I think). |
133 |
> > |
134 |
> > Blender now builds and runs. The trick was, that the system wide |
135 |
> > python 3.2 (which blender needs) uses lib64 while the previously |
136 |
> > under /usr/local installed one uses lib as the directory where its |
137 |
> > own python code is store. |
138 |
> > |
139 |
> > I build blender by myself. The pure vanilla code, freshly taken from |
140 |
> > the developpers svn repository. No patch, no tweak. The real thing :) |
141 |
> > ;))) |
142 |
> > |
143 |
> > Unfortunately blender spit out messages, that it is built against |
144 |
> > libpng-1.2.27 ... and the whole systems only contains libpng-1.5*. |
145 |
> > |
146 |
> > Currently I have no clue, what the reasons fro this is. Unfortunately |
147 |
> > the CUDE renderer fails to do its job. I can start blender...but not |
148 |
> > really much more. |
149 |
> > |
150 |
> > This was a day in deep hack mode. Strace was my friend...as so often. |
151 |
> > |
152 |
> > Will see how I can fix the rest of the problems. |
153 |
> > |
154 |
> > The main problem of builing hydrogen was the python under /usr/local |
155 |
> > I think... |
156 |
> > |
157 |
> > Will see what hick up next .... |
158 |
> > |
159 |
> > Cheers, |
160 |
> > Meino |
161 |
> |
162 |
> Meino, |
163 |
> Based on this thread's setup of python I had no trouble building |
164 |
> the stable version of blender offered in portage. I don't know how to |
165 |
> use blender but I had no trouble starting the app and getting the GUI |
166 |
> up. |
167 |
> |
168 |
> If you are not able to duplicate this then I would like to know. |
169 |
> Are you using the stable version or something newer? If newer have you |
170 |
> tried the stable version? If you can build the stable version then you |
171 |
> have a basis to file bug reports on anything newer that doesn't work. |
172 |
> If you cannot build the stable version then we need to determine why |
173 |
> on my audio application laptop where I'm running Jack+ Rosegarden + |
174 |
> qjackctl + hydrogen + etc., and now blender, you would be having |
175 |
> trouble on a smilar machine. |
176 |
> |
177 |
> Cheers, |
178 |
> Mark |
179 |
> |
180 |
> slinky ~ # emerge -DuN blender |
181 |
> Calculating dependencies... done! |
182 |
> >>> Verifying ebuild manifests |
183 |
> >>> Starting parallel fetch |
184 |
> >>> Emerging (1 of 6) media-libs/ilmbase-1.0.2 |
185 |
> >>> Emerging (2 of 6) media-libs/lcms-2.3 |
186 |
> >>> Emerging (3 of 6) media-libs/ftgl-2.1.3_rc5 |
187 |
> >>> Installing (1 of 6) media-libs/ilmbase-1.0.2 |
188 |
> >>> Emerging (4 of 6) media-libs/openexr-1.7.0 |
189 |
> >>> Installing (2 of 6) media-libs/lcms-2.3 |
190 |
> >>> Installing (3 of 6) media-libs/ftgl-2.1.3_rc5 |
191 |
> >>> Emerging (5 of 6) media-libs/openjpeg-1.4-r1 |
192 |
> >>> Installing (5 of 6) media-libs/openjpeg-1.4-r1 |
193 |
> >>> Installing (4 of 6) media-libs/openexr-1.7.0 |
194 |
> >>> Emerging (6 of 6) media-gfx/blender-2.49b-r2 |
195 |
> >>> Installing (6 of 6) media-gfx/blender-2.49b-r2 |
196 |
> >>> Recording media-gfx/blender in "world" favorites file... |
197 |
> >>> Jobs: 6 of 6 complete Load avg: 8.96, 5.21, 2.35 |
198 |
> |
199 |
> * Messages for package media-gfx/blender-2.49b-r2: |
200 |
> |
201 |
> * blender uses python integration. As such, may have some |
202 |
> * inherit risks with running unknown python scripting. |
203 |
> * |
204 |
> * CVE-2008-1103-1.patch has been removed as it interferes |
205 |
> * with autosave undo features. Up stream blender coders |
206 |
> * have not addressed the CVE issue as the status is still |
207 |
> * a CANDIDATE and not CONFIRMED. |
208 |
> * |
209 |
> * It is recommended to change your blender temp directory |
210 |
> * from /tmp to ~tmp or another tmp file under your home |
211 |
> * directory. This can be done by starting blender, then |
212 |
> * dragging the main menu down do display all paths. |
213 |
> >>> Auto-cleaning packages... |
214 |
> |
215 |
> >>> No outdated packages were found on your system. |
216 |
> |
217 |
> * GNU info directory index is up-to-date. |
218 |
> slinky ~ # |
219 |
> |
220 |
|
221 |
|
222 |
Hi Mark, |
223 |
|
224 |
thank you very much for all your helping and installing |
225 |
applications!!! |
226 |
|
227 |
As I wrote: |
228 |
|
229 |
I build blender by myself. The pure vanilla code, freshly taken from |
230 |
the developpers svn repository. No patch, no tweak. The real thing :) |
231 |
|
232 |
I am using the developpers source code tree, which is 2.62. Blender |
233 |
2.49 is a very old version of blender... |
234 |
|
235 |
I can start blender (build successful), but currently it does not find |
236 |
the GPU of my graphic card on which blender should render. This seems |
237 |
to be a bug in the nvidia driver...I have posted an according message |
238 |
to the german blender mailinglist "blendpolis". |
239 |
|
240 |
Since blender 2.62 is very much different from blender 2.49 (2.49 |
241 |
cannot render on the GPU of a graphic card and has no physically |
242 |
correct render engine like blender 2.62) results from building/using |
243 |
blender 2.49 cannot be used to analyze bugs with blender 2.62. |
244 |
Furthermore they both use different versions of python. |
245 |
|
246 |
Will see what finally is the bug... |
247 |
|
248 |
Thank you for your help and testing, Mark! |
249 |
|
250 |
Cheers |
251 |
Meino |