compiling povray on slackware 6 current
by jr_bob_dobbs from LinuxQuestions.org on (#4WV3F)
EDIT: Title is in error: "6" should "64". Looks like title editing is not a thing so it will have to stay.
Installed Slackware 64 current from the November 14th current.
I've been using an older version of povray, 3.6, for ages, recompiling it again for each install of an operating system. This time, it failed to compile and i was unable to fix it. As an immediate solution, I reused the binary package I'd made from the May or April -current.
Today I decided to see about getting it to properly compile. Since the 3.6 version won't compile, I decided to give in and try the 3.7 version.
Attempt 1: compile it myself, making the slackbuild as I go. Nope. Oh well, I kind of expected that. Seems povray has a problem with boost and my attempts to pass "--without-boost" were failures.
Attempt 2: Slackbuilds.org. They have one but, it fails. Also not unexpected.
Attempt 3: ponce...
There was a link for povray. That went to a page. On that page there was actually a link "download". OK.
That downloaded a large tarball. Large. Seems to be the povray source. Oh. Why is the source tarball not named with the version? The ponce page identifies it as "version 3.7.0.8" yet the tarball is named "slackbuilds-povray.tar.gz."
I grepped the output of "tar -tf" of that tar for "Slackbuild" to see if there was a slackbuild file in it. There was more than one .Slackbuild, including "zuluCrypt.SlackBuild". What is Zulu crypt? This is a tar that claims to be povray. Why is there a slackbuild for an encryption product within? At this point I said, "this is screwy, I'm stopping"
Has anyone actually compiled povray (3.6 or 3.7, at this point I don't care which) in a reasonably recent slackware? If so, how did you manage it?
Thank you.
Installed Slackware 64 current from the November 14th current.
I've been using an older version of povray, 3.6, for ages, recompiling it again for each install of an operating system. This time, it failed to compile and i was unable to fix it. As an immediate solution, I reused the binary package I'd made from the May or April -current.
Today I decided to see about getting it to properly compile. Since the 3.6 version won't compile, I decided to give in and try the 3.7 version.
Attempt 1: compile it myself, making the slackbuild as I go. Nope. Oh well, I kind of expected that. Seems povray has a problem with boost and my attempts to pass "--without-boost" were failures.
Attempt 2: Slackbuilds.org. They have one but, it fails. Also not unexpected.
Attempt 3: ponce...
There was a link for povray. That went to a page. On that page there was actually a link "download". OK.
That downloaded a large tarball. Large. Seems to be the povray source. Oh. Why is the source tarball not named with the version? The ponce page identifies it as "version 3.7.0.8" yet the tarball is named "slackbuilds-povray.tar.gz."
I grepped the output of "tar -tf" of that tar for "Slackbuild" to see if there was a slackbuild file in it. There was more than one .Slackbuild, including "zuluCrypt.SlackBuild". What is Zulu crypt? This is a tar that claims to be povray. Why is there a slackbuild for an encryption product within? At this point I said, "this is screwy, I'm stopping"
Has anyone actually compiled povray (3.6 or 3.7, at this point I don't care which) in a reasonably recent slackware? If so, how did you manage it?
Thank you.