 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I'm trying to install PovRay in Ubuntu 14.04. I've checked that all dependencies
are updated (libboost-dev, zlib1g-dev, libpng12-dev, libjpeg8-dev
libtiff5-dev,libopenexr-dev).
I've followed the instructions in:
https://github.com/POV-Ray/povray/blob/3.7-stable/unix/README.md
% cd unix/
% ./prebuild.sh
% cd ../
% ./configure COMPILED_BY="your name <email@address>"
% make
% make install
The prebuild is completed successfully, but when I ran make, I get the
following:
make all-recursive
make[1]: Entering directory `/home/mark/Desktop/povray/povray'
Making all in source
make[2]: Entering directory `/home/mark/Desktop/povray/povray/source'
depbase=`echo core/scene/object.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
g++ -DHAVE_CONFIG_H -I. -I.. -I../unix/povconfig -I.. -I../unix -I../vfe
-I../vfe/unix -pthread -I/usr/include/OpenEXR -pthread -I/usr/include
-I/usr/include -pipe -Wno-multichar -Wno-write-strings -fno-enforce-eh-specs
-Wno-non-template-friend -s -O3 -ffast-math -march=native -pthread -MT
core/scene/object.o -MD -MP -MF $depbase.Tpo -c -o core/scene/object.o
core/scene/object.cpp &&\
mv -f $depbase.Tpo $depbase.Po
In file included from ./core/configcore.h:41:0,
from core/scene/object.cpp:39:
#define POV_MATHUTIL_ASSERT(expr) NO_OP
^
POV_MATHUTIL_ASSERT((tempVal >= 0.0) && (tempVal < upperLimit));
^
make[2]: *** [core/scene/object.o] Error 1
make[2]: Leaving directory `/home/mark/Desktop/povray/povray/source'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/mark/Desktop/povray/povray'
make: *** [all] Error 2
Any ideas? Thanks in advance!
Mark
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/18/2015 11:44 AM, Mark B wrote:
> I'm trying to install PovRay in Ubuntu 14.04. I've checked that all dependencies
> are updated (libboost-dev, zlib1g-dev, libpng12-dev, libjpeg8-dev
> libtiff5-dev,libopenexr-dev).
>
> I've followed the instructions in:
> https://github.com/POV-Ray/povray/blob/3.7-stable/unix/README.md
>
> % cd unix/
> % ./prebuild.sh
> % cd ../
> % ./configure COMPILED_BY="your name <email@address>"
> % make
> % make install
>
> The prebuild is completed successfully, but when I ran make, I get the
> following:
>
> make all-recursive
> make[1]: Entering directory `/home/mark/Desktop/povray/povray'
> Making all in source
> make[2]: Entering directory `/home/mark/Desktop/povray/povray/source'
> depbase=`echo core/scene/object.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
> g++ -DHAVE_CONFIG_H -I. -I.. -I../unix/povconfig -I.. -I../unix -I../vfe
> -I../vfe/unix -pthread -I/usr/include/OpenEXR -pthread -I/usr/include
> -I/usr/include -pipe -Wno-multichar -Wno-write-strings -fno-enforce-eh-specs
> -Wno-non-template-friend -s -O3 -ffast-math -march=native -pthread -MT
> core/scene/object.o -MD -MP -MF $depbase.Tpo -c -o core/scene/object.o
> core/scene/object.cpp &&\
> mv -f $depbase.Tpo $depbase.Po
> In file included from ./core/configcore.h:41:0,
> from core/scene/object.cpp:39:
> #define POV_MATHUTIL_ASSERT(expr) NO_OP
> ^
> POV_MATHUTIL_ASSERT((tempVal >= 0.0) && (tempVal < upperLimit));
> ^
> make[2]: *** [core/scene/object.o] Error 1
> make[2]: Leaving directory `/home/mark/Desktop/povray/povray/source'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/mark/Desktop/povray/povray'
> make: *** [all] Error 2
>
>
> Any ideas? Thanks in advance!
>
> Mark
>
>
>
Mark,
How did you get your source code?
I only see the code an issue for you in the master branch and it
compiles OK for me just now with Ubuntu 14.04. In my git cloned code the
definition of NO_OP is located in source/base/types.h and it looks like:
/// A macro that does nothing.
///
/// This macro is intended to be used in the definition of other macros
that should behave
/// syntactically like a single statement, while evaluating to a
no-operation.
///
/// Example:
///
/// #declare MY_ASSERT(x) NO_OP
/// ...
/// if (some_cond)
/// MY_ASSERT(some_test);
/// else
/// ...
///
#define NO_OP SINGLE_STATEMENT(;)
Do you see this definition in in your copy of source/base/types.h ?
Another option is to try the 3.7-stable branch of the code which does
not have the code causing you compile trouble. You can get to this using
git in a source directory which does not already have a povray
subdirectory with:
git clone https://github.com/POV-Ray/povray.git
cd povray
git checkout origin/3.7-stable
Then do the prebuild & configure stuff again - you'll probably need to
add the LIBS="-lboost_system -lboost_thread" to your configure command
for the stable branch. Don't do the last git checkout command if you
want to try compiling the current master after cloning code via git.
Lastly, the following recent thread in this newsgroup might be of
general help with build dependencies in Ubuntu:
http://news.povray.org/povray.unix/thread/%3Cweb.5645c196e1bf2118ad6fa18f0%40news.povray.org%3E/
Bill P.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 19.11.2015 um 04:04 schrieb William F Pokorny:
> I only see the code an issue for you in the master branch and it
> compiles OK for me just now with Ubuntu 14.04.
That is not really a surprise, as I had already checked in a fix half an
hour after Mark's post ;)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Indeed - I confirm that the bug has been fixed just a few hours after I posted
this. It compiles OK now.
Thanks clipka!
clipka <ano### [at] anonymous org> wrote:
> Am 19.11.2015 um 04:04 schrieb William F Pokorny:
>
> > I only see the code an issue for you in the master branch and it
> > compiles OK for me just now with Ubuntu 14.04.
>
> That is not really a surprise, as I had already checked in a fix half an
> hour after Mark's post ;)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/19/2015 03:35 AM, clipka wrote:
> Am 19.11.2015 um 04:04 schrieb William F Pokorny:
>
>> I only see the code an issue for you in the master branch and it
>> compiles OK for me just now with Ubuntu 14.04.
>
> That is not really a surprise, as I had already checked in a fix half an
> hour after Mark's post ;)
>
:-) Cool.
Yep, I need to get in the habit of checking the commit history ("git
log"). I am still new to git/github code control and mostly I don't know
what I am doing.
Guess, the last bit there applies to my life in general and not just
git... ;-)
Bill P.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
