Hi(gh)!

I just downloaded the zip package from povray.org, unzipped it into my 
home directory... changed to the "unix" directory, read the instructions 
in install.txt - but even failed to perform only the first command, 

there is no configure program at all!

Where do I have to look?!?

See you in Khyberspace!

Yadgar

Post a reply to this message

Jörg 'Yadgar' Bleimann wrote:

> Hi(gh)!
> 
> I just downloaded the zip package from povray.org, unzipped it into my
> home directory... changed to the "unix" directory, read the instructions
> in install.txt - but even failed to perform only the first command,
> ./configure COMPILED_BY="Jörg 'Yadgar' Bleimann <yaz### [at] gmxde>", as
> there is no configure program at all!
> 
> Where do I have to look?!?
> 
In povray.unix
I dropped a script there to configure/compile/install povray on suse linux.
You should be able to convert it to what you want.
-- 

Ger

Post a reply to this message

> Hi(gh)!
>
> I just downloaded the zip package from povray.org, unzipped it into my
> home directory... changed to the "unix" directory, read the instructions
> in install.txt - but even failed to perform only the first command,

> there is no configure program at all!
>
> Where do I have to look?!?

Note that the zip package is /not/ a Unix source code package, but a 
generic platform-independent one; as such it does not conform to the 
typical unixoid conventions.

In order to turn the generic source code package into a Unix-specific 
one, you'll have to run "prebuild.sh" from the "./unix" directory.

Among other things, this will create the "./configure" script in the 
main directory, which then in turn generates the files needed by "make".

Post a reply to this message

Hi(gh)!

On 07.02.2014 05:48, clipka wrote:

> In order to turn the generic source code package into a Unix-specific
> one, you'll have to run "prebuild.sh" from the "./unix" directory.

...which lead to an error message:
error: requires autoconf 2.59 or above

When trying to install autoconf via apt-get, I discovered that the 
Debian repositories only keep the 2.13 version! And now?

See you in Khyberspace!

Yadgar

Now playing: Cover Me (Bruce Springsteen)

Post a reply to this message

> Hi(gh)!
>
> On 07.02.2014 05:48, clipka wrote:
>
>> In order to turn the generic source code package into a Unix-specific
>> one, you'll have to run "prebuild.sh" from the "./unix" directory.
>
> ...which lead to an error message:
> error: requires autoconf 2.59 or above
>
> When trying to install autoconf via apt-get, I discovered that the
> Debian repositories only keep the 2.13 version! And now?

http://www.gnu.org/software/autoconf/#downloading

Post a reply to this message

> Hi(gh)!
>
> On 07.02.2014 05:48, clipka wrote:
>
>> In order to turn the generic source code package into a Unix-specific
>> one, you'll have to run "prebuild.sh" from the "./unix" directory.
>
> ...which lead to an error message:
> error: requires autoconf 2.59 or above
>
> When trying to install autoconf via apt-get, I discovered that the
> Debian repositories only keep the 2.13 version! And now?

or try ...

apt-cache search autoconf

i see:
autoconf - automatic configure script builder
autoconf-doc - automatic configure script builder documentation
autoconf2.13 - automatic configure script builder (obsolete version)
autoconf2.64 - automatic configure script builder (obsolete version)
autotools-dev - Update infrastructure for config.{guess,sub} files
autoconf-archive - Autoconf Macro Archive
autoconf-gl-macros - autoconf macros to check for OpenGL/GLU/GLUT
autoconf2.59 - automatic configure script builder (obsolete version)

Post a reply to this message

Hi(gh)!

On 07.02.2014 05:48, clipka wrote:

> In order to turn the generic source code package into a Unix-specific
> one, you'll have to run "prebuild.sh" from the "./unix" directory.
>
> Among other things, this will create the "./configure" script in the
> main directory, which then in turn generates the files needed by "make".

O.k., now I managed to install an autoconf version higher than 2.59 (and 
also automake) just to be able to do prebuild.sh... then I started 
./configure - and now it complains about the missing boost libraries! 
Which packages exactly do I have to install now?

See you in Khyberspace!

Yadgar

Post a reply to this message

> Hi(gh)!
>
> On 07.02.2014 05:48, clipka wrote:
>
>> In order to turn the generic source code package into a Unix-specific
>> one, you'll have to run "prebuild.sh" from the "./unix" directory.
>>
>> Among other things, this will create the "./configure" script in the
>> main directory, which then in turn generates the files needed by "make".
>
> O.k., now I managed to install an autoconf version higher than 2.59 (and
> also automake) just to be able to do prebuild.sh... then I started
> ./configure - and now it complains about the missing boost libraries!
> Which packages exactly do I have to install now?

apt-get build-dep libboost-all-dev
apt-get install libboost-all-dev

Post a reply to this message

Hi(gh)!

On 08.02.2014 18:46, James Holsenback wrote:

> apt-get build-dep libboost-all-dev
> apt-get install libboost-all-dev

I did that - and got the error message as follows:

checking whether the Boost::Thread library is available... no
configure: error: cannot find a suitable boost thread library

Where do I get that "thread library"?

See you in Khyberspace!

Yadgar

Post a reply to this message

> Hi(gh)!
>
> On 08.02.2014 18:46, James Holsenback wrote:
>
>> apt-get build-dep libboost-all-dev
>> apt-get install libboost-all-dev
>
> I did that - and got the error message as follows:
>
> checking whether the Boost::Thread library is available... no
> configure: error: cannot find a suitable boost thread library
>
> Where do I get that "thread library"?

did you use sudo on apt-get commands?

what does you configure command looks like ... did you add appropriate 
options? http://wiki.povray.org/content/User:Le_Forgeron/vault/Compilation

Post a reply to this message