Hi,

I can't compile povray under Ubuntu 14.04. It fails in the configure stage:

./configure COMPILED_BY="your name <email@address>"

...
checking for boostlib >= 1.37... yes
checking whether the Boost::Thread library is available... yes
checking whether the boost thread library is usable... no
configure: error: in `/tmp/povray':
configure: error: cannot link with the boost thread library
See `config.log' for more details



config.log says

configure:7849: checking whether the boost thread library is usable
configure:7869: g++ -o conftest  -pthread  -pthread -I/usr/include
-L/usr/lib conftest.cpp   -pthread  >&5
/tmp/ccPemSjN.o: In function
`__static_initialization_and_destruction_0(int, int)':
conftest.cpp:(.text+0x4f): undefined reference to
`boost::system::generic_category()'
conftest.cpp:(.text+0x5b): undefined reference to
`boost::system::generic_category()'
conftest.cpp:(.text+0x67): undefined reference to
`boost::system::system_category()'
collect2: error: ld returned 1 exit status




The reason might be that under Ubuntu libboost is split into several
parts and the missing symbols are in libboost_system, which is not
linked against.

regards
Hadmut

Post a reply to this message

Le 22/03/2014 22:19, Hadmut Danisch nous fit lire :
> Hi,
> 
> I can't compile povray under Ubuntu 14.04. It fails in the configure stage:
> 
> ./configure COMPILED_BY="your name <email@address>"
> 

Same old story, same workaround when using gcc compiler:

./configure ... LIBS="-lboost_system -lboost_thread"

Post a reply to this message

Am 23.03.2014 07:35, schrieb Le_Forgeron:

> Same old story, same workaround when using gcc compiler:
>
> ./configure ... LIBS="-lboost_system -lboost_thread"


Still lots of problems even before configure (fresh git checkout):


Detected autoconf 2.69
Detected automake 1.14.1

...

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 'base/pov_err.cpp' is in a
subdirectory,
source/Makefile.am:35: but option 'subdir-objects' is disabled

...

source/Makefile.am:35: warning: source file 'base/animation/moov.cpp' is
in a subdirectory,
source/Makefile.am:35: but option 'subdir-objects' is disabled
source/Makefile.am:35: warning: source file
'base/animation/animation.cpp' is in a subdirectory,
source/Makefile.am:35: but option 'subdir-objects' is disabled

...



And configure fails even with the LIBS option:


Makefiles
---------
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: error: cannot find input file: `Makefile.in'


Seems as if there were several files missing oder in wrong position
(git branch 3.7-stable )


Hadmut

Post a reply to this message

On 03/25/2014 02:48 PM, Hadmut Danisch wrote:
> Am 23.03.2014 07:35, schrieb Le_Forgeron:
>
>> Same old story, same workaround when using gcc compiler:
>>
>> ./configure ... LIBS="-lboost_system -lboost_thread"
>
>
> Still lots of problems even before configure (fresh git checkout):
>
>
> Detected autoconf 2.69
> Detected automake 1.14.1
>
> ...
>
> 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 'base/pov_err.cpp' is in a
> subdirectory,
> source/Makefile.am:35: but option 'subdir-objects' is disabled
>
> ...
>
> source/Makefile.am:35: warning: source file 'base/animation/moov.cpp' is
> in a subdirectory,
> source/Makefile.am:35: but option 'subdir-objects' is disabled
> source/Makefile.am:35: warning: source file
> 'base/animation/animation.cpp' is in a subdirectory,
> source/Makefile.am:35: but option 'subdir-objects' is disabled
>
> ...
>
>
>
> And configure fails even with the LIBS option:
>
>
> Makefiles
> ---------
> checking that generated files are newer than configure... done
> configure: creating ./config.status
> config.status: error: cannot find input file: `Makefile.in'
>
>
> Seems as if there were several files missing oder in wrong position
> (git branch 3.7-stable )
>
>
> Hadmut
>
>

did you run ~unix/prebuild.sh script first? if not cd to that (unix) 
directory and run it ... then pop back up one directory and try the 
configure phase again

Post a reply to this message

Le 25/03/2014 20:48, James Holsenback nous fit lire :
> On 03/25/2014 02:48 PM, Hadmut Danisch wrote:
>> Am 23.03.2014 07:35, schrieb Le_Forgeron:
>>
>>> Same old story, same workaround when using gcc compiler:
>>>
>>> ./configure ... LIBS="-lboost_system -lboost_thread"
>>
>>
>> Still lots of problems even before configure (fresh git checkout):
>>
>>
>> Detected autoconf 2.69
>> Detected automake 1.14.1
>>

> 
> did you run ~unix/prebuild.sh script first? if not cd to that (unix)
> directory and run it ... then pop back up one directory and try the
> configure phase again

It seems he did. But there might be an issue with automake (my version
here is 1.13.3 and all is fine, but I'm on 13.10 not 14.04 yet): see the
thread "Error building POV-Ray 3.7 on Linux (Debian Testing)", the error
was already there too.

Reported solution: running "automake --add-missing" on top directory
after prebuild.sh was ran, and running prebuild.sh again.

date of solution post: 22/11/2013, by Joel Yliluoma, :

> 
> The problem was eventually resolved by running "automake --add-missing"
> in the top directory _after_ prebuild.sh was run once, and then running
> prebuild.sh again...
> 
> This appeared to generate a symlink, compile->/usr/share/automake-1.14/compile
> in unix/config/ . Then it configured and compiled properly.
> 
> Why does this not happen otherwise?
> I have no idea.

Post a reply to this message

On 03/25/2014 03:56 PM, Le_Forgeron wrote:
> It seems he did. But there might be an issue with automake (my version
> here is 1.13.3 and all is fine, but I'm on 13.10 not 14.04 yet): see the
> thread "Error building POV-Ray 3.7 on Linux (Debian Testing)", the error
> was already there too.
>
> Reported solution: running "automake --add-missing" on top directory
> after prebuild.sh was ran, and running prebuild.sh again.

I hadn't remembered having to do that on buildbot server (until you 
mentioned it) as well!

Post a reply to this message

Am 25.03.2014 20:56, schrieb Le_Forgeron:
> Reported solution: running "automake --add-missing" on top directory
> after prebuild.sh was ran, and running prebuild.sh again.


Yup, that works.

Thanks :-)

Post a reply to this message

Le_Forgeron <jgr### [at] freefr> wrote:
> Le 22/03/2014 22:19, Hadmut Danisch nous fit lire :
> > Hi,
> >
> > I can't compile povray under Ubuntu 14.04. It fails in the configure stage:
> >
> > ./configure COMPILED_BY="your name <email@address>"
> >
>
> Same old story, same workaround when using gcc compiler:
>
> ./configure ... LIBS="-lboost_system -lboost_thread"

---------------------------------------------------------------------------------
  As of 31-10-2014, Povray 3.7 Stable, for Unix, will not compile.
 First problem is the need to enter the Unix directory and run prebuild.sh, as
it is nowhere mentioned in the documentation.
   First error is the BOOST error, thread lib not working. This is fixed with -
LIBS="-lboost_system -lboost_thread" --with-x --disable-io-restrictions. The x
and io stuff are to ease use.
  The second fault is -
 checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: error: cannot find input file: `Makefile.in'
  Makefile.in is indeed absent.
  The Makefile.in in unix is blank.
  This is total failure.
  I bought up the Git page, as instructed before, and by a dint of random
clicking managed to obtain Povray-Master. How I don't know.  Did the prebuild.sh
thing, cd .. to the Pov root, ./configure stuff -

apoof@Solaris:~/tmp/povray-3.7-stable$ ./configure COMPILED_BY="apoof
<Apo### [at] gmxcom>" LIBS="-lboost_system -lboost_thread" --with-x
--disable-io-restrictions

This worked.
Hope this helps some others.

Post a reply to this message

Le 31/10/2014 11:10, Adolph a écrit :
> Le_Forgeron <jgr### [at] freefr> wrote:
>> Le 22/03/2014 22:19, Hadmut Danisch nous fit lire :
>>> Hi,
>>>
>>> I can't compile povray under Ubuntu 14.04. It fails in the configure stage:
>>>
>>> ./configure COMPILED_BY="your name <email@address>"
>>>
>>
>> Same old story, same workaround when using gcc compiler:
>>
>> ./configure ... LIBS="-lboost_system -lboost_thread"
> 
> ---------------------------------------------------------------------------------
>   As of 31-10-2014, Povray 3.7 Stable, for Unix, will not compile.
>  First problem is the need to enter the Unix directory and run prebuild.sh, as
> it is nowhere mentioned in the documentation.
>    First error is the BOOST error, thread lib not working. This is fixed with -
> LIBS="-lboost_system -lboost_thread" --with-x --disable-io-restrictions. The x
> and io stuff are to ease use.
>   The second fault is -
>  checking that generated files are newer than configure... done
> configure: creating ./config.status
> config.status: error: cannot find input file: `Makefile.in'
>   Makefile.in is indeed absent.
>   The Makefile.in in unix is blank.
>   This is total failure.
>   I bought up the Git page, as instructed before, and by a dint of random
> clicking managed to obtain Povray-Master. How I don't know.  Did the prebuild.sh
> thing, cd .. to the Pov root, ./configure stuff -
> 
> apoof@Solaris:~/tmp/povray-3.7-stable$ ./configure COMPILED_BY="apoof
> <Apo### [at] gmxcom>" LIBS="-lboost_system -lboost_thread" --with-x
> --disable-io-restrictions
> 
> This worked.
> Hope this helps some others.
> 

So does it work, or not ?

it's not enough to run prebuild.sh, you should look at its output for
any error (such as missing Automake and others...)

Is stable broken and not master ?

I'm surprised by --with-x, as 3.7 use SDL instead of X11.
(and then SDL uses X11, but that's no more the interface that povray sees)



-- 
Just because nobody complains does not mean all parachutes are perfect.

Post a reply to this message

Le 31/10/2014 15:01, Le_Forgeron a écrit :
> Le 31/10/2014 11:10, Adolph a écrit :
>> Le_Forgeron <jgr### [at] freefr> wrote:
>>> Le 22/03/2014 22:19, Hadmut Danisch nous fit lire :
>>>> Hi,
>>>>
>>>> I can't compile povray under Ubuntu 14.04. It fails in the configure stage:
>>>>
>>>> ./configure COMPILED_BY="your name <email@address>"
>>>>
>>>
>>> Same old story, same workaround when using gcc compiler:
>>>
>>> ./configure ... LIBS="-lboost_system -lboost_thread"
>>
>> ---------------------------------------------------------------------------------
>>   As of 31-10-2014, Povray 3.7 Stable, for Unix, will not compile.
>>  First problem is the need to enter the Unix directory and run prebuild.sh, as
>> it is nowhere mentioned in the documentation.
>>    First error is the BOOST error, thread lib not working. This is fixed with -
>> LIBS="-lboost_system -lboost_thread" --with-x --disable-io-restrictions. The x
>> and io stuff are to ease use.
>>   The second fault is -
>>  checking that generated files are newer than configure... done
>> configure: creating ./config.status
>> config.status: error: cannot find input file: `Makefile.in'
>>   Makefile.in is indeed absent.
>>   The Makefile.in in unix is blank.
>>   This is total failure.
>>   I bought up the Git page, as instructed before, and by a dint of random
>> clicking managed to obtain Povray-Master. How I don't know.  Did the prebuild.sh
>> thing, cd .. to the Pov root, ./configure stuff -
>>
>> apoof@Solaris:~/tmp/povray-3.7-stable$ ./configure COMPILED_BY="apoof
>> <Apo### [at] gmxcom>" LIBS="-lboost_system -lboost_thread" --with-x
>> --disable-io-restrictions
>>
>> This worked.
>> Hope this helps some others.
>>
> 
> So does it work, or not ?

Looking at flyspray for povray, the issue with the stable branch is that
the automake need now some explicit "--add-missing" in prebuild.sh
(master has been patched for that).

underlying issue is that previously such flag was not required by
automake... and may be that flag is not even recognised by previous
version of automake (IMHO, automake's devs broke compatibility (on the
same way as libboost's devs did) and we have to remember how to adapt)






-- 
Just because nobody complains does not mean all parachutes are perfect.

Post a reply to this message