Running povray probs

[deniscallies]

Yesterday I installed PovRay... everything works right. now everytime i start PovRay there is following error- message: error while loading shared libraries: libstdc++-libc6.1-2.so.3: cannot open shared object.
Where can i find them?

Greets Denis

CACKO RULES!

[pmf]

You could try the POVRay-ipkg from my feed: http://www.pmf.neominds.net/feed/povray_3.50c_arm.ipk; it contains the library.

If you would rather use your povray (where did you get it?), you can just extract the library from my ipk-File:

Code: [Select]

tar xzf povray_3.50c_arm.ipk ./data.tar.gz -O | tar xzf - will create a subdir usr/lib in the current dir containing the library.

[deniscallies]

Thanks a lot
Tried the IPK from zaurus.spy but the new one does it.

Maybe I made a mistake?!?

[newkirk]

hah - this is too funny, POV-Ray on a \'PDA\'.

(I spent several years as the primary Amiga developer for POV-Ray - this just became a must-have install that I\'ll probably never use )

j

[diesel1]

Ok, we have povray, anyone got a modeler?

Could Giram be compiled for zaurus?

I might have to try bochs+POVLab!  

I have tried jPatch and ArtOfIllusion but they will not run (need java 1.4).

Simon.

[telemetric_au]

You could try the POVRay-ipkg from my feed: http://www.pmf.neominds.net/feed/povray_3.50c_arm.ipk; it contains the library.

If you would rather use your povray (where did you get it?), you can just extract the library from my ipk-File:

Code: [Select]

tar xzf povray_3.50c_arm.ipk ./data.tar.gz -O | tar xzf - will create a subdir usr/lib in the current dir containing the library.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

that link is down, try here:

[a href=\"http://www.pdaxrom.org/oldunstable/povray_3.50c_arm.ipk]http://www.pdaxrom.org/oldunstable/povray_3.50c_arm.ipk[/url]

and also here's some examples though ive never installed this software and have no idea what can be done with the z version...

http://hof.povray.org/index-lb.html

[0xDEADBEEF]

You guys are crazy. Z doesnt have floating point on a CPU. Povray is going to be as "fast" as on an Amiga

[telemetric_au]

hmmm... well i couldnt get it to run from the link i posted but that was with a 5500, good point though Beef

[miskinis]

Yeh, POV for the Zaurus is sort of funny, in that I never even thought of
the concept.  I will absolutley be trying it soon though!  I used to use POV
on a Pentium 100 daily, and it ran at "light speed" compared to using
it on older equipment.

On another funny note, circa 1987 or so, at DIGITAL, we had homebrew
ray tracer, that took 24 days of CPU to generate a very simplistic scene
of a room at a resolution of approx. 640x480...  

Many thanks for compiling/packaging this, I'll try it real soon on the SL-6000, I promise!

John

[miskinis]

FYI - povray segfaults at the end of displaying the help text, that is as far as I am now...

Sl-6000 on beta1, povray installed to SD

EDIT #1
   I can't seem to render even a very small scene.  It complains about the "camera location"
   and the "look at point" needing to be different, and they certainly are in the .pov file!
   I also saw parsing errors during include file processing, on some of the sample files.

   Is anyone able to render the "sample" files?  If so, what is the command line you use?

Thanks,  John

[miskinis]

Hi,

FYI - I removed povray, since I am pretty sure something major is wrong with the
package listed in the "link is down, but get it here" post above.

I installed a newer version ( povray_3.6.1_arm.ipk ) that is listed in the
Software forum, and although it installed OK, it requires the
libstdc++-libc6.1-2.so.3 library...

John

[miskinis]

Hi Folks,

Summary: POVRAY 3.6 is up and running OK on beta1!

Yesterday, with a renewed interest in POVRAY as well as pdaXrom on the SL-6000
I tried to get the 3.6 version running using the stdc++ library from the 3.5 version as
described in the the earlier posts.

Although I could get the parser to start, I kept running into problems with parsing
macros, with errors indicating that the version directive was missing, although it
was present, and I even tried specifying it on the command line.

Today, I took a new approach, and compiled the 3.6 linux source code, and ran into
absolutely no issues!  It seems to have consumed about 8MB on / , but I am very happy
to have it running.

I'm not sure how long it took to build, as I did not monitor it, but it was done when I
looked at the system after 2 hours.  Anyway, I figured I'd let folks know.   John

[stupkid]

Any chance on posting a tarball or package?

[miskinis]

Hi,

I just spent a little while trying to determine exactly what would have to be put
in a tarball to fully capture my POVRAY installation.  Before I post a tarball, I
would like a few folks to review and comment on my findings, so I can try to get
this right the first time.  Also, I have listed the dynamic link dependencies that
are shown on the povray binary I have produced.  I believe the stdc++ it is linked
to, is the one that I extracted from the 3.5 ipk that was listed in an earlier post.

draft tarball contents:

7.1M    /usr/local/share/doc/povray-3.6 (the docs)
3.9M    /usr/local/share/povray-3.6 (includes, scenes, ini files, scripts)
1.9M    /usr/local/bin/povray (the program)

dynamic link dependencies:

# ldd `which povray`        
        libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x4001f000)
        libpng12.so.0 => /usr/lib/libpng12.so.0 (0x40044000)
        libz.so.1 => /usr/lib/libz.so.1 (0x40081000)
        libXpm.so.4 => /usr/X11R6/lib/libXpm.so.4 (0x4009c000)
        libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x400b1000)
        libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x400c1000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x400de000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x401a4000)
        libm.so.6 => /lib/libm.so.6 (0x40283000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40332000)
        libc.so.6 => /lib/libc.so.6 (0x40343000)
        libdl.so.2 => /lib/libdl.so.2 (0x40463000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

[miskinis]

Hi,

On second thought, I am just going to post a tarball, as pdaXrom is in
fact a "fly by the seat of your pants for a while"- style dist, right?

I believe it will work, if you have the deps, if not, or if you observe other issues,
please post them.  I plan to be here for many hours tonight

DARN - Upload failed - I am not permitted to upload a file with that extension!