POV-Ray : Newsgroups : povray.unix : Error building POV-Ray 3.7 on Linux (Debian Testing) Server Time: 18 Jun 2019 06:37:19 GMT
  Error building POV-Ray 3.7 on Linux (Debian Testing) (Message 1 to 10 of 15)  
Goto Latest 10 Messages Next 5 Messages >>>
From: Joel Yliluoma
Subject: Error building POV-Ray 3.7 on Linux (Debian Testing)
Date: 21 Nov 2013 12:15:00
Message: <slrnl8rua3.ipl.bisqwit@bisqwit.iki.fi>
I am having trouble building POV-Ray 3.7.

I downloaded povray-3.7-stable.zip from the github page at
  https://github.com/POV-Ray/povray/tree/3.7-stable
and unzipped it.

I also installed the debian package "libboost-all-dev", which
installs every Boost library. The current version is 1.54.0.

I applied a preliminary fix. (Explained below.)*

In the unix/ directory, I ran prebuild.sh.

It lists the following errors and warnings:

+ aclocal -I .

  configure.ac:302: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
  ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
  ../../lib/autoconf/general.m4:2590: _AC_COMPILE_IFELSE is expanded from...
  ../../lib/autoconf/general.m4:2606: AC_COMPILE_IFELSE is expanded from...
  ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from...
  ../../lib/autoconf/general.m4:2031: AC_CACHE_VAL is expanded from...
  ../../lib/autoconf/general.m4:2052: AC_CACHE_CHECK is expanded from...
  unix/config/ax_boost_thread.m4:32: AX_BOOST_THREAD is expanded from...
  configure.ac:302: the top level

+ autoheader --warnings=all

  (repeats the same warnings as above)

+ automake --warnings=all

  configure.ac:302: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
  ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
  ../../lib/autoconf/general.m4:2590: _AC_COMPILE_IFELSE is expanded from...
  ../../lib/autoconf/general.m4:2606: AC_COMPILE_IFELSE is expanded from...
  ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from...
  ../../lib/autoconf/general.m4:2031: AC_CACHE_VAL is expanded from...
  ../../lib/autoconf/general.m4:2052: AC_CACHE_CHECK is expanded from...
  unix/config/ax_boost_thread.m4:32: AX_BOOST_THREAD is expanded from...
  configure.ac:302: the top level
  configure.ac:185: error: required file 'unix/config/compile' not found
  configure.ac:185:   'automake --add-missing' can install 'compile'
  source/Makefile.am:35: warning: source file 'frontend/shelloutprocessing.cpp' is in
a subdirectory,
  source/Makefile.am:35: but option 'subdir-objects' is disabled
  automake: warning: possible forward-incompatibility.
  automake: At least a source file is in a subdirectory, but the 'subdir-objects'
  automake: automake option hasn't been enabled.  For now, the corresponding output
  automake: object file(s) will be placed in the top-level directory.  However,
  automake: this behaviour will change in future Automake versions: they will
  automake: unconditionally cause object files to be placed in the same subdirectory
  automake: of the corresponding sources.
  automake: You are advised to start using 'subdir-objects' option throughout your
  automake: project, to avoid future incompatibilities.
  source/Makefile.am:35: warning: source file 'frontend/rendermessagehandler.cpp' is
in a subdirectory,
  source/Makefile.am:35: but option 'subdir-objects' is disabled
  source/Makefile.am:35: warning: source file 'frontend/console.cpp' is in a
subdirectory,
  source/Makefile.am:35: but option 'subdir-objects' is disabled
  (and so on repeated for a few dozen cpp files)
  /usr/share/automake-1.14/am/library.am: warning: 'libpovray.a': linking libraries
using a non-POSIX
  /usr/share/automake-1.14/am/library.am: archiver requires 'AM_PROG_AR' in
'configure.ac'
  source/Makefile.am:32:   while processing library 'libpovray.a'
  vfe/Makefile.am:35: warning: source file 'unix/vfeplatform.cpp' is in a
subdirectory,
  vfe/Makefile.am:35: but option 'subdir-objects' is disabled
  vfe/Makefile.am:35: warning: source file 'unix/unixoptions.cpp' is in a
subdirectory,
  vfe/Makefile.am:35: but option 'subdir-objects' is disabled
  vfe/Makefile.am:35: warning: source file 'unix/unixconsole.cpp' is in a
subdirectory,
  vfe/Makefile.am:35: but option 'subdir-objects' is disabled
  vfe/Makefile.am:35: warning: source file 'unix/platformbase.cpp' is in a
subdirectory,
  vfe/Makefile.am:35: but option 'subdir-objects' is disabled
  /usr/share/automake-1.14/am/library.am: warning: 'libvfe.a': linking libraries using
a non-POSIX
  /usr/share/automake-1.14/am/library.am: archiver requires 'AM_PROG_AR' in
'configure.ac'
  vfe/Makefile.am:32:   while processing library 'libvfe.a'

+ autoconf --warnings=all

  configure.ac:295: warning: The macro `AC_LANG_SAVE' is obsolete.
  configure.ac:295: You should run autoupdate.
  ../../lib/autoconf/lang.m4:125: AC_LANG_SAVE is expanded from...
  unix/config/acx_pthread.m4:78: ACX_PTHREAD is expanded from...
  configure.ac:295: the top level
  configure.ac:295: warning: The macro `AC_LANG_C' is obsolete.
  configure.ac:295: You should run autoupdate.
  ../../lib/autoconf/c.m4:72: AC_LANG_C is expanded from...
  unix/config/acx_pthread.m4:78: ACX_PTHREAD is expanded from...
  configure.ac:295: the top level
  configure.ac:295: warning: The macro `AC_TRY_LINK' is obsolete.
  configure.ac:295: You should run autoupdate.
  ../../lib/autoconf/general.m4:2687: AC_TRY_LINK is expanded from...
  unix/config/acx_pthread.m4:78: ACX_PTHREAD is expanded from...
  configure.ac:295: the top level
  configure.ac:295: warning: The macro `AC_LANG_RESTORE' is obsolete.
  configure.ac:295: You should run autoupdate.
  ../../lib/autoconf/lang.m4:134: AC_LANG_RESTORE is expanded from...
  unix/config/acx_pthread.m4:78: ACX_PTHREAD is expanded from...
  configure.ac:295: the top level
  configure.ac:302: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
  ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
  ../../lib/autoconf/general.m4:2590: _AC_COMPILE_IFELSE is expanded from...
  ../../lib/autoconf/general.m4:2606: AC_COMPILE_IFELSE is expanded from...
  ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from...
  ../../lib/autoconf/general.m4:2031: AC_CACHE_VAL is expanded from...
  ../../lib/autoconf/general.m4:2052: AC_CACHE_CHECK is expanded from...
  unix/config/ax_boost_thread.m4:32: AX_BOOST_THREAD is expanded from...
  configure.ac:302: the top level
  + cat ./configure
  + sed -e 's,configure.gnu  --help=recursive,& --srcdir=$ac_srcdir,g' -e 's,\(cd
\)\($ac_\)\(pop\)*\(dir\),\1"\2\3\4",g' -e
's,$am_aux_dir/missing,\\"$am_aux_dir\\"/missing,g'
  + mv -f ./configure.tmp ./configure
  + chmod +x ./configure
  + rm -f -r ./autom4te.cache
  sed: can't read ./Makefile.in: No such file or directory

It generates a "configure" script in "unix/.." .

Then I do:  cd ..; ./configure COMPILED_BY="Bisqwit <bis### [at] ikifi>".
configuring stops at the following error:
  ---------
  checking that generated files are newer than configure... done
  configure: creating ./config.status
  config.status: error: cannot find input file: `Makefile.in'


Bash's autocomplete gives me the following list of versions of autotools:

  unix$ automake
  automake       automake-1.14  automake-1.4   automake-1.8   automake-1.9   
  unix$ autoconf
  autoconf      autoconf2.13  autoconf2.50  autoconf2.59  autoconf2.64  
  unix$ autohead
  autoheader      autoheader2.13  autoheader2.50  autoheader2.59  autoheader2.64  
  unix$ acloc
  aclocal       aclocal-1.14  aclocal-1.4   aclocal-1.8   aclocal-1.9   

  autoconf version is 2.69. automake version is 1.14.
  autoheader version is 2.69. aclocal version is 1.14.


What should I do?



*) Preliminary fix:
In unix/config/ax_boost_thread.m4, I added -lboost_system
right next to -l$ax_lib, because otherwise configure would
complain that it cannot link with boost_thread and config.log
would indicate this linker error message:
undefined reference to symbol '_ZN5boost6system15system_categoryEv'

-- 
Joel Yliluoma
http://iki.fi/bisqwit/


Post a reply to this message

From: clipka
Subject: Re: Error building POV-Ray 3.7 on Linux (Debian Testing)
Date: 21 Nov 2013 12:39:37
Message: <528dff09$1@news.povray.org>
Am 21.11.2013 13:15, schrieb Joel Yliluoma:
> I am having trouble building POV-Ray 3.7.

Am I correctly infering from the subject line that you are running a 
non-stable version of Linux?

It seems to me that the autoconf tool suite has some backward 
compatibility issues. Which, if I may say so, is /not/ the best thing 
that can happen with a tool that was designed to /solve/ compatibility 
issues...


Folks, did anybody already try compiling POV-Ray 3.7 on the latest 
stable Debian?


Post a reply to this message

From: James Holsenback
Subject: Re: Error building POV-Ray 3.7 on Linux (Debian Testing)
Date: 21 Nov 2013 12:46:15
Message: <528e0097$1@news.povray.org>
On 11/21/2013 07:39 AM, clipka wrote:
> Am 21.11.2013 13:15, schrieb Joel Yliluoma:
>> I am having trouble building POV-Ray 3.7.
>
> Am I correctly infering from the subject line that you are running a
> non-stable version of Linux?
>
> It seems to me that the autoconf tool suite has some backward
> compatibility issues. Which, if I may say so, is /not/ the best thing
> that can happen with a tool that was designed to /solve/ compatibility
> issues...

indeed those warnings are part of the landscape but shouldn't stop 
things (as the user indicated) ... look further down in the original 
post and see the missing Makefile.in problem that I was having .... I 
think user should pull again using git (unless your updates flowed into 
the zip download)


Post a reply to this message

From: James Holsenback
Subject: Re: Error building POV-Ray 3.7 on Linux (Debian Testing)
Date: 21 Nov 2013 12:56:03
Message: <528e02e3$1@news.povray.org>
On 11/21/2013 07:46 AM, James Holsenback wrote:
> On 11/21/2013 07:39 AM, clipka wrote:
>> Am 21.11.2013 13:15, schrieb Joel Yliluoma:
>>> I am having trouble building POV-Ray 3.7.
>>
>> Am I correctly infering from the subject line that you are running a
>> non-stable version of Linux?
>>
>> It seems to me that the autoconf tool suite has some backward
>> compatibility issues. Which, if I may say so, is /not/ the best thing
>> that can happen with a tool that was designed to /solve/ compatibility
>> issues...
>
> indeed those warnings are part of the landscape but shouldn't stop
> things (as the user indicated) ... look further down in the original
> post and see the missing Makefile.in problem that I was having .... I
> think user should pull again using git (unless your updates flowed into
> the zip download)
>

LOL ... knew it was going to happen eventually. I think the colour.ccp 
issue needs to flow to the /povray/ github as well


Post a reply to this message

From: clipka
Subject: Re: Error building POV-Ray 3.7 on Linux (Debian Testing)
Date: 21 Nov 2013 13:42:59
Message: <528e0de3$1@news.povray.org>
Am 21.11.2013 13:56, schrieb James Holsenback:
> On 11/21/2013 07:46 AM, James Holsenback wrote:
>> On 11/21/2013 07:39 AM, clipka wrote:
>>> Am 21.11.2013 13:15, schrieb Joel Yliluoma:
>>>> I am having trouble building POV-Ray 3.7.
>>>
>>> Am I correctly infering from the subject line that you are running a
>>> non-stable version of Linux?
>>>
>>> It seems to me that the autoconf tool suite has some backward
>>> compatibility issues. Which, if I may say so, is /not/ the best thing
>>> that can happen with a tool that was designed to /solve/ compatibility
>>> issues...
>>
>> indeed those warnings are part of the landscape but shouldn't stop
>> things (as the user indicated) ... look further down in the original
>> post and see the missing Makefile.in problem that I was having .... I
>> think user should pull again using git (unless your updates flowed into
>> the zip download)
>>
>
> LOL ... knew it was going to happen eventually. I think the colour.ccp
> issue needs to flow to the /povray/ github as well

Nope - the missing Makefile.in is just an indication that /something/ 
tore up the generation of said file. The duplicate file thing generates 
a particular message much earlier, which isn't there in this case, so 
something else must be going wrong.

Besides, the povray github doesn't even have the duplicate files yet.


Post a reply to this message

From: James Holsenback
Subject: Re: Error building POV-Ray 3.7 on Linux (Debian Testing)
Date: 21 Nov 2013 15:08:01
Message: <528e21d1$1@news.povray.org>
On 11/21/2013 07:15 AM, Joel Yliluoma wrote:

In the +automake section this is where things start to differ from what 
I'm getting:
<snipped a bunch>
>    configure.ac:185: error: required file 'unix/config/compile' not found
>    configure.ac:185:   'automake --add-missing' can install 'compile'

then I think this is what's causing the rest of the problems:

>    source/Makefile.am:35: warning: source file 'frontend/shelloutprocessing.cpp' is
in a subdirectory,
>    source/Makefile.am:35: but option 'subdir-objects' is disabled
>    automake: warning: possible forward-incompatibility.
>    automake: At least a source file is in a subdirectory, but the 'subdir-objects'
>    automake: automake option hasn't been enabled.  For now, the corresponding output
>    automake: object file(s) will be placed in the top-level directory.  However,
>    automake: this behaviour will change in future Automake versions: they will
>    automake: unconditionally cause object files to be placed in the same
subdirectory
>    automake: of the corresponding sources.
>    automake: You are advised to start using 'subdir-objects' option throughout your
>    automake: project, to avoid future incompatibilities.
>    source/Makefile.am:35: warning: source file 'frontend/rendermessagehandler.cpp'
is in a subdirectory,
>    source/Makefile.am:35: but option 'subdir-objects' is disabled
>    source/Makefile.am:35: warning: source file 'frontend/console.cpp' is in a
subdirectory,
>    source/Makefile.am:35: but option 'subdir-objects' is disabled
>    (and so on repeated for a few dozen cpp files)
>    /usr/share/automake-1.14/am/library.am: warning: 'libpovray.a': linking libraries
using a non-POSIX
>    /usr/share/automake-1.14/am/library.am: archiver requires 'AM_PROG_AR' in
'configure.ac'
>    source/Makefile.am:32:   while processing library 'libpovray.a'
>    vfe/Makefile.am:35: warning: source file 'unix/vfeplatform.cpp' is in a
subdirectory,
>    vfe/Makefile.am:35: but option 'subdir-objects' is disabled
>    vfe/Makefile.am:35: warning: source file 'unix/unixoptions.cpp' is in a
subdirectory,
>    vfe/Makefile.am:35: but option 'subdir-objects' is disabled
>    vfe/Makefile.am:35: warning: source file 'unix/unixconsole.cpp' is in a
subdirectory,
>    vfe/Makefile.am:35: but option 'subdir-objects' is disabled
>    vfe/Makefile.am:35: warning: source file 'unix/platformbase.cpp' is in a
subdirectory,
>    vfe/Makefile.am:35: but option 'subdir-objects' is disabled
>    /usr/share/automake-1.14/am/library.am: warning: 'libvfe.a': linking libraries
using a non-POSIX
>    /usr/share/automake-1.14/am/library.am: archiver requires 'AM_PROG_AR' in
'configure.ac'
>    vfe/Makefile.am:32:   while processing library 'libvfe.a'
>
> + autoconf --warnings=all
<snipped some more>

>    sed: can't read ./Makefile.in: No such file or directory

because of the above fail ... I'm thinking there needs to be some kind 
of error detection here that makes an aborted sequence apparent

> It generates a "configure" script in "unix/.." .
>
> Then I do:  cd ..; ./configure COMPILED_BY="Bisqwit <bis### [at] ikifi>".
> configuring stops at the following error:
>    ---------
>    checking that generated files are newer than configure... done
>    configure: creating ./config.status
>    config.status: error: cannot find input file: `Makefile.in'
>
>
> Bash's autocomplete gives me the following list of versions of autotools:
>
>    unix$ automake
>    automake       automake-1.14  automake-1.4   automake-1.8   automake-1.9
>    unix$ autoconf
>    autoconf      autoconf2.13  autoconf2.50  autoconf2.59  autoconf2.64
>    unix$ autohead
>    autoheader      autoheader2.13  autoheader2.50  autoheader2.59  autoheader2.64
>    unix$ acloc
>    aclocal       aclocal-1.14  aclocal-1.4   aclocal-1.8   aclocal-1.9
>
>    autoconf version is 2.69. automake version is 1.14.
>    autoheader version is 2.69. aclocal version is 1.14.

for what it's worth I'm using:

automake (GNU automake) 1.11.1
autoconf (GNU Autoconf) 2.68
autoheader (GNU Autoconf) 2.68
aclocal (GNU automake) 1.11.1


Post a reply to this message

From: James Holsenback
Subject: Re: Error building POV-Ray 3.7 on Linux (Debian Testing)
Date: 21 Nov 2013 16:51:44
Message: <528e3a20$1@news.povray.org>
On 11/21/2013 10:08 AM, James Holsenback wrote:
> for what it's worth I'm using:
>
> automake (GNU automake) 1.11.1
> autoconf (GNU Autoconf) 2.68
> autoheader (GNU Autoconf) 2.68
> aclocal (GNU automake) 1.11.1

one other thing that /might/ cause problems ... the version of make you 
are using. INSTALL file cites version 3.79 or above. on mine:

make --version

returns GNU Make 3.82


Post a reply to this message

From: xyproto
Subject: Re: Error building POV-Ray 3.7 on Linux (Debian Testing)
Date: 21 Nov 2013 20:00:01
Message: <web.528e6598ec21ff0aae7e3a340@news.povray.org>
Have you tried the solutions from the thread named "Packaging povray 3.7 stable
for Arch Linux"? The errors look somewhat similar to me.

Best regards,
Alexander Rødseth


Post a reply to this message

From: clipka
Subject: Re: Error building POV-Ray 3.7 on Linux (Debian Testing)
Date: 21 Nov 2013 20:23:49
Message: <528e6bd5$1@news.povray.org>
Am 21.11.2013 20:57, schrieb xyproto:
> Have you tried the solutions from the thread named "Packaging povray 3.7 stable
> for Arch Linux"? The errors look somewhat similar to me.
>
> Best regards,
> Alexander Rødseth

Indeed. Looks like we should consider those as permanent changes to the 
Unix build stuff; but we'll need to check when that option was first 
supported by automake.


Post a reply to this message

From: Joel Yliluoma
Subject: Re: Error building POV-Ray 3.7 on Linux (Debian Testing)
Date: 22 Nov 2013 19:03:20
Message: <slrnl8vajo.hjo.bisqwit@bisqwit.iki.fi>
On Thu, 21 Nov 2013 13:39:31 +0100, clipka wrote:
> Am 21.11.2013 13:15, schrieb Joel Yliluoma:
>> I am having trouble building POV-Ray 3.7.
>
> Am I correctly infering from the subject line that you are running a 
> non-stable version of Linux?

It's stable all right. What it isn't is stale.

-- 
Joel Yliluoma
http://iki.fi/bisqwit/


Post a reply to this message

Goto Latest 10 Messages Next 5 Messages >>>

Copyright 2003-2008 Persistence of Vision Raytracer Pty. Ltd.