 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Latest UberPOV version, with all the new official POV-Ray bells &
whistles merged in.
https://github.com/UberPOV/UberPOV/releases/tag/v1.37.1.0-beta.9
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymous org> wrote:
> Latest UberPOV version, with all the new official POV-Ray bells &
> whistles merged in.
>
> https://github.com/UberPOV/UberPOV/releases/tag/v1.37.1.0-beta.9
Cool that someone works on this :)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 01/31/2015 03:47 AM, clipka wrote:
> Latest UberPOV version, with all the new official POV-Ray bells &
> whistles merged in.
>
> https://github.com/UberPOV/UberPOV/releases/tag/v1.37.1.0-beta.9
I'm getting this error during the make portion of the build:
In file included from backend/frame.h:67:0,
from lightgrp.cpp:35:
./base/colour.h: In member function
‘pov_base::GenericTrans<COLOUR_T>::Channel
pov_base::GenericTrans<COLOUR_T>::LegacyOpacity(const Colour&) const’:
./base/colour.h:1132:28: error: ‘col’ was not declared in this scope
In file included from backend/frame.h:67:0,
from lightgrp.cpp:35:
./base/colour.h: In constructor
‘pov_base::GenericTransColour<CT>::GenericTransColour(const Colour&,
pov_base::GenericTransColour<CT>::Channel,
pov_base::GenericTransColour<CT>::Channel)’:
./base/colour.h:1933:13: error: class ‘pov_base::GenericTransColour<CT>’
does not have any field named ‘mFilter’
./base/colour.h:1934:13: error: class ‘pov_base::GenericTransColour<CT>’
does not have any field named ‘mTransm’
make[2]: *** [lightgrp.o] Error 1
make[2]: Leaving directory
`/home/ash/ScratchPad/uber/UberPOV-1.37.1.0-beta.9/source'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/home/ash/ScratchPad/uber/UberPOV-1.37.1.0-beta.9'
make: *** [all] Error 2
Same error that I'm getting with ANY source AFTER beta6 (which built
just fine)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 01/31/2015 08:26 PM, James Holsenback wrote:
> On 01/31/2015 03:47 AM, clipka wrote:
>> Latest UberPOV version, with all the new official POV-Ray bells &
>> whistles merged in.
>>
>> https://github.com/UberPOV/UberPOV/releases/tag/v1.37.1.0-beta.9
>
> I'm getting this error during the make portion of the build:
>
> In file included from backend/frame.h:67:0,
> from lightgrp.cpp:35:
> ./base/colour.h: In member function
> ‘pov_base::GenericTrans<COLOUR_T>::Channel
> pov_base::GenericTrans<COLOUR_T>::LegacyOpacity(const Colour&) const’:
> ./base/colour.h:1132:28: error: ‘col’ was not declared in this scope
> In file included from backend/frame.h:67:0,
> from lightgrp.cpp:35:
> ./base/colour.h: In constructor
> ‘pov_base::GenericTransColour<CT>::GenericTransColour(const Colour&,
> pov_base::GenericTransColour<CT>::Channel,
> pov_base::GenericTransColour<CT>::Channel)’:
> ./base/colour.h:1933:13: error: class ‘pov_base::GenericTransColour<CT>’
> does not have any field named ‘mFilter’
> ./base/colour.h:1934:13: error: class ‘pov_base::GenericTransColour<CT>’
> does not have any field named ‘mTransm’
> make[2]: *** [lightgrp.o] Error 1
> make[2]: Leaving directory
> `/home/ash/ScratchPad/uber/UberPOV-1.37.1.0-beta.9/source'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory
> `/home/ash/ScratchPad/uber/UberPOV-1.37.1.0-beta.9'
> make: *** [all] Error 2
>
> Same error that I'm getting with ANY source AFTER beta6 (which built
> just fine)
thinking it's the configure phase I redirected output to file to compare
results:
diff c-outb6 c-outb9
4c4
< Configure UberPOV version 1.37.0.0-beta.6
---
> Configure UberPOV version 1.37.1.0-beta.9
177a178
> checking whether g++ accepts -Wno-non-template-friend... yes
222c223
< UberPOV 1.37.0.0-beta.6 has been configured.
---
> UberPOV 1.37.1.0-beta.9 has been configured.
235c236
< Compiler flags: -pipe -Wno-multichar -Wno-write-strings
-fno-enforce-eh-specs -s -O3 -ffast-math -malign-double
-march=native -pthread
---
> Compiler flags: -pipe -Wno-multichar -Wno-write-strings
-fno-enforce-eh-specs -Wno-non-template-friend -s -O3 -
ffast-math -malign-double -march=native -pthread
and noticed the checking whether g++ accepts yada-yada shows up for the
beta9 configure ... is that a clue?
Post a reply to this message
|
|
| |
| |
|
|
From: James Holsenback
Subject: Re: UberPOV v1.37.1.0-beta.9 released
Date: 31 Jan 2015 20:49:01
Message: <54cd860d@news.povray.org>
|
|
|
| |
| |
|
|
On 01/31/2015 08:46 PM, James Holsenback wrote:
> On 01/31/2015 08:26 PM, James Holsenback wrote:
>> On 01/31/2015 03:47 AM, clipka wrote:
>>> Latest UberPOV version, with all the new official POV-Ray bells &
>>> whistles merged in.
>>>
>>> https://github.com/UberPOV/UberPOV/releases/tag/v1.37.1.0-beta.9
>>
>> I'm getting this error during the make portion of the build:
>>
>> In file included from backend/frame.h:67:0,
>> from lightgrp.cpp:35:
>> ./base/colour.h: In member function
>> ‘pov_base::GenericTrans<COLOUR_T>::Channel
>> pov_base::GenericTrans<COLOUR_T>::LegacyOpacity(const Colour&) const’:
>> ./base/colour.h:1132:28: error: ‘col’ was not declared in this scope
>> In file included from backend/frame.h:67:0,
>> from lightgrp.cpp:35:
>> ./base/colour.h: In constructor
>> ‘pov_base::GenericTransColour<CT>::GenericTransColour(const Colour&,
>> pov_base::GenericTransColour<CT>::Channel,
>> pov_base::GenericTransColour<CT>::Channel)’:
>> ./base/colour.h:1933:13: error: class ‘pov_base::GenericTransColour<CT>’
>> does not have any field named ‘mFilter’
>> ./base/colour.h:1934:13: error: class ‘pov_base::GenericTransColour<CT>’
>> does not have any field named ‘mTransm’
>> make[2]: *** [lightgrp.o] Error 1
>> make[2]: Leaving directory
>> `/home/ash/ScratchPad/uber/UberPOV-1.37.1.0-beta.9/source'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory
>> `/home/ash/ScratchPad/uber/UberPOV-1.37.1.0-beta.9'
>> make: *** [all] Error 2
>>
>> Same error that I'm getting with ANY source AFTER beta6 (which built
>> just fine)
>
> thinking it's the configure phase I redirected output to file to compare
> results:
>
> diff c-outb6 c-outb9
> 4c4
> < Configure UberPOV version 1.37.0.0-beta.6
> ---
> > Configure UberPOV version 1.37.1.0-beta.9
> 177a178
> > checking whether g++ accepts -Wno-non-template-friend... yes
> 222c223
> < UberPOV 1.37.0.0-beta.6 has been configured.
> ---
> > UberPOV 1.37.1.0-beta.9 has been configured.
> 235c236
> < Compiler flags: -pipe -Wno-multichar -Wno-write-strings
> -fno-enforce-eh-specs -s -O3 -ffast-math -malign-double
> -march=native -pthread
> ---
> > Compiler flags: -pipe -Wno-multichar -Wno-write-strings
> -fno-enforce-eh-specs -Wno-non-template-friend -s -O3 -
> ffast-math -malign-double -march=native -pthread
>
> and noticed the checking whether g++ accepts yada-yada shows up for the
> beta9 configure ... is that a clue?
Oh ... and the Compiler flags shows -Wno-non-template-friend for b9 as well
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 01/31/2015 08:49 PM, James Holsenback wrote:
> On 01/31/2015 08:46 PM, James Holsenback wrote:
>> On 01/31/2015 08:26 PM, James Holsenback wrote:
>>> On 01/31/2015 03:47 AM, clipka wrote:
>>>> Latest UberPOV version, with all the new official POV-Ray bells &
>>>> whistles merged in.
>>>>
>>>> https://github.com/UberPOV/UberPOV/releases/tag/v1.37.1.0-beta.9
>>>
>>> I'm getting this error during the make portion of the build:
>>>
>>> In file included from backend/frame.h:67:0,
>>> from lightgrp.cpp:35:
>>> ./base/colour.h: In member function
>>> ‘pov_base::GenericTrans<COLOUR_T>::Channel
>>> pov_base::GenericTrans<COLOUR_T>::LegacyOpacity(const Colour&) const’:
>>> ./base/colour.h:1132:28: error: ‘col’ was not declared in this scope
>>> In file included from backend/frame.h:67:0,
>>> from lightgrp.cpp:35:
>>> ./base/colour.h: In constructor
>>> ‘pov_base::GenericTransColour<CT>::GenericTransColour(const Colour&,
>>> pov_base::GenericTransColour<CT>::Channel,
>>> pov_base::GenericTransColour<CT>::Channel)’:
>>> ./base/colour.h:1933:13: error: class ‘pov_base::GenericTransColour<CT>’
>>> does not have any field named ‘mFilter’
>>> ./base/colour.h:1934:13: error: class ‘pov_base::GenericTransColour<CT>’
>>> does not have any field named ‘mTransm’
>>> make[2]: *** [lightgrp.o] Error 1
>>> make[2]: Leaving directory
>>> `/home/ash/ScratchPad/uber/UberPOV-1.37.1.0-beta.9/source'
>>> make[1]: *** [all-recursive] Error 1
>>> make[1]: Leaving directory
>>> `/home/ash/ScratchPad/uber/UberPOV-1.37.1.0-beta.9'
>>> make: *** [all] Error 2
>>>
>>> Same error that I'm getting with ANY source AFTER beta6 (which built
>>> just fine)
>>
>> thinking it's the configure phase I redirected output to file to compare
>> results:
>>
>> diff c-outb6 c-outb9
>> 4c4
>> < Configure UberPOV version 1.37.0.0-beta.6
>> ---
>> > Configure UberPOV version 1.37.1.0-beta.9
>> 177a178
>> > checking whether g++ accepts -Wno-non-template-friend... yes
>> 222c223
>> < UberPOV 1.37.0.0-beta.6 has been configured.
>> ---
>> > UberPOV 1.37.1.0-beta.9 has been configured.
>> 235c236
>> < Compiler flags: -pipe -Wno-multichar -Wno-write-strings
>> -fno-enforce-eh-specs -s -O3 -ffast-math -malign-double
>> -march=native -pthread
>> ---
>> > Compiler flags: -pipe -Wno-multichar -Wno-write-strings
>> -fno-enforce-eh-specs -Wno-non-template-friend -s -O3 -
>> ffast-math -malign-double -march=native -pthread
>>
>> and noticed the checking whether g++ accepts yada-yada shows up for the
>> beta9 configure ... is that a clue?
>
> Oh ... and the Compiler flags shows -Wno-non-template-friend for b9 as well
holy crap i'm rusty (bare with me) haven't even TOUCHED pov/uber for
almost 3 months now: I'm using gcc (SUSE Linux) 4.6.2
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 01.02.2015 um 02:49 schrieb James Holsenback:
>> and noticed the checking whether g++ accepts yada-yada shows up for the
>> beta9 configure ... is that a clue?
>
> Oh ... and the Compiler flags shows -Wno-non-template-friend for b9 as well
Nope (presuming with "yada-yada" you mean "-Wno-non-template-friend");
this is just the suppression of an unwarranted warning from g++.
Effectively, what this is all about is that there was a quirk in older
g++ versions violating the C++ specs, and now by default they issue a
warning just in case your code was relying on g++'s old behaviour.
I'll have a closer look at it. It's certainly not something affecting
the Windows build.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 01.02.2015 um 02:26 schrieb James Holsenback:
> Same error that I'm getting with ANY source AFTER beta6 (which built
> just fine)
Can you please do me a favor and check again with the following versions:
ce0aae6b54d434ceb3daf7410582f95ea742ac14 (2014-07-27)
e1028cd0dbb0918324cf9b898906b54222fc67da (2014-07-29)
I have strong reason to believe that the latter introduced the error.
Which also means that it's probably already present in the
feature/colour_model branch in the official POV-Ray repo.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 01/31/2015 10:37 PM, clipka wrote:
> Am 01.02.2015 um 02:26 schrieb James Holsenback:
>
>> Same error that I'm getting with ANY source AFTER beta6 (which built
>> just fine)
>
> Can you please do me a favor and check again with the following versions:
>
> ce0aae6b54d434ceb3daf7410582f95ea742ac14 (2014-07-27)
> e1028cd0dbb0918324cf9b898906b54222fc67da (2014-07-29)
>
> I have strong reason to believe that the latter introduced the error.
> Which also means that it's probably already present in the
> feature/colour_model branch in the official POV-Ray repo.
>
ce0aae6b54d434ceb3daf7410582f95ea742ac14 has the same error so I did NOT
pull e1028cd0dbb0918324cf9b898906b54222fc67da
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 01.02.2015 um 05:08 schrieb James Holsenback:
> On 01/31/2015 10:37 PM, clipka wrote:
>> Am 01.02.2015 um 02:26 schrieb James Holsenback:
>>
>>> Same error that I'm getting with ANY source AFTER beta6 (which built
>>> just fine)
>>
>> Can you please do me a favor and check again with the following versions:
>>
>> ce0aae6b54d434ceb3daf7410582f95ea742ac14 (2014-07-27)
>> e1028cd0dbb0918324cf9b898906b54222fc67da (2014-07-29)
>>
>> I have strong reason to believe that the latter introduced the error.
>> Which also means that it's probably already present in the
>> feature/colour_model branch in the official POV-Ray repo.
>>
>
> ce0aae6b54d434ceb3daf7410582f95ea742ac14 has the same error so I did NOT
> pull e1028cd0dbb0918324cf9b898906b54222fc67da
Strange - I suspect you must have done something wrong there. Never
mind, I've been able to reproduce the error and trace it back to the
"feature/colour_model" branch in the official repo (which is what
UberPOV is based on). I'm currently in the process of releasing a fix.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 31.01.2015 um 09:47 schrieb clipka:
> Latest UberPOV version, with all the new official POV-Ray bells &
> whistles merged in.
>
> https://github.com/UberPOV/UberPOV/releases/tag/v1.37.1.0-beta.9
As Jim has pointed out, beta.9 doesn't compile on Linux, so here's a
source code update:
https://github.com/UberPOV/UberPOV/releases/tag/v1.37.1.0-beta.9b
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 02/01/2015 12:56 AM, clipka wrote:
> Am 31.01.2015 um 09:47 schrieb clipka:
>> Latest UberPOV version, with all the new official POV-Ray bells &
>> whistles merged in.
>>
>> https://github.com/UberPOV/UberPOV/releases/tag/v1.37.1.0-beta.9
>
> As Jim has pointed out, beta.9 doesn't compile on Linux, so here's a
> source code update:
>
> https://github.com/UberPOV/UberPOV/releases/tag/v1.37.1.0-beta.9b
>
yer gettin' closer:
backend/povray.cpp: In function ‘void
{anonymous}::BuildInitInfo(POVMSObjectPtr)’:
backend/povray.cpp:301:115: error: expected ‘)’ before ‘SSE2_INCLUDED’
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 01.02.2015 um 07:23 schrieb James Holsenback:
> yer gettin' closer:
>
> backend/povray.cpp: In function ‘void
> {anonymous}::BuildInitInfo(POVMSObjectPtr)’:
> backend/povray.cpp:301:115: error: expected ‘)’ before ‘SSE2_INCLUDED’
Strangely enough, I didn't come across that one on my Linux machine.
Are you building on a 32 bit computer?
Until I figure this one out, I recommend you just remove the
"SSE2_INCLUDED" from that line (any anywhere else where it might cause
hiccups).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 02/01/2015 01:38 AM, clipka wrote:
> Am 01.02.2015 um 07:23 schrieb James Holsenback:
>
>> yer gettin' closer:
>>
>> backend/povray.cpp: In function ‘void
>> {anonymous}::BuildInitInfo(POVMSObjectPtr)’:
>> backend/povray.cpp:301:115: error: expected ‘)’ before ‘SSE2_INCLUDED’
>
> Strangely enough, I didn't come across that one on my Linux machine.
> Are you building on a 32 bit computer?
yes
>
> Until I figure this one out, I recommend you just remove the
> "SSE2_INCLUDED" from that line (any anywhere else where it might cause
> hiccups).
>
was already in the file trying to make repair when i saw your reply ...
line 301 was the only place
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 01/02/15 06:38, clipka wrote:
> Am 01.02.2015 um 07:23 schrieb James Holsenback:
>
>> yer gettin' closer:
>>
>> backend/povray.cpp: In function ‘void
>> {anonymous}::BuildInitInfo(POVMSObjectPtr)’:
>> backend/povray.cpp:301:115: error: expected ‘)’ before ‘SSE2_INCLUDED’
>
> Strangely enough, I didn't come across that one on my Linux machine.
> Are you building on a 32 bit computer?
>
> Until I figure this one out, I recommend you just remove the
> "SSE2_INCLUDED" from that line (any anywhere else where it might cause
> hiccups).
>
It appears that removing SSE_INCLUDED from line 301 in
backend/povray.cpp does the trick.
I got the same error as James but I was compiling on a 64 bit machine.
After removal of offending word, all is sweetness and light
John
--
Protect the Earth
It was not given to you by your parents
You hold it in trust for your children
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 01/02/15 14:15, Doctor John wrote:
>
> I got the same error as James but I was compiling on a 64 bit machine.
> After removal of offending word, all is sweetness and light
>
> John
>
Additional:
john@linux-bh1u:~> gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib64/gcc/x86_64-suse-linux/4.8/lto-wrapper
Target: x86_64-suse-linux
Configured with: ../configure --prefix=/usr --infodir=/usr/share/info
--mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64
--enable-languages=c,c++,objc,fortran,obj-c++,java,ada
--enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.8
--enable-ssp --disable-libssp --disable-plugin
--with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux'
--disable-libgcj --disable-libmudflap --with-slibdir=/lib64
--with-system-zlib --enable-__cxa_atexit
--enable-libstdcxx-allocator=new --disable-libstdcxx-pch
--enable-version-specific-runtime-libs --enable-linker-build-id
--enable-linux-futex --program-suffix=-4.8 --without-system-libunwind
--with-arch-32=i586 --with-tune=generic --build=x86_64-suse-linux
--host=x86_64-suse-linux
Thread model: posix
gcc version 4.8.3 20140627 [gcc-4_8-branch revision 212064] (SUSE Linux)
John
--
Protect the Earth
It was not given to you by your parents
You hold it in trust for your children
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
