When trying to compile the latest povray-master on the latest opensuse 
tumbleweed I get the following

Making install in source
make[1]: Entering directory '/home/ger/Downloads/povray-master/source'
depbase=`echo backend/bounding/boundingtask.o | sed 
's|[^/]*$|.deps/&|;s|\.o$||'`;\
g++ -DHAVE_CONFIG_H -I. -I..  -I../unix/povconfig -I.. 
-I../platform/unix -I../platform/x86 -I../unix -I../vfe -I../vfe/unix 
-I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -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 backend/bounding/boundingtask.o 
-MD -MP -MF $depbase.Tpo -c -o backend/bounding/boundingtask.o 
backend/bounding/boundingtask.cpp &&\
mv -f $depbase.Tpo $depbase.Po
In file included from ../unix/povconfig/syspovconfigbase.h:42:0,
                  from ./base/configbase.h:41,
                  from ./backend/frame.h:57,
                  from backend/bounding/boundingtask.cpp:42:
../unix/povconfig/syspovconfig.h:59:10: fatal error: 
boost/tr1/memory.hpp: No such file or directory
  #include <boost/tr1/memory.hpp>
           ^~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [Makefile:1178: backend/bounding/boundingtask.o] Error 1
make[1]: Leaving directory '/home/ger/Downloads/povray-master/source'
make: *** [Makefile:663: install-recursive] Error 1

Since the above text is either Chinese or Klingon to me I have no clue 
where to look for any resolving the error, so help would be appreciated.

-- 
Cheers

Post a reply to this message

Am 30.11.2017 um 21:15 schrieb Ger:
> When trying to compile the latest povray-master on the latest opensuse
> tumbleweed I get the following

As mentioned in the project's `README.md` file, we generally discourage
building from the master branch. Please build from any of the tagged
commits instead:

https://github.com/POV-Ray/povray/tags

The issue you've encountered should already be fixed in the latest and
greatest of those versions (currently v3.8.0-alpha.9387404).

Post a reply to this message

On 11/30/2017 03:21 PM, clipka wrote:
> Am 30.11.2017 um 21:15 schrieb Ger:
>> When trying to compile the latest povray-master on the latest opensuse
>> tumbleweed I get the following
> 
> As mentioned in the project's `README.md` file, we generally discourage
> building from the master branch. Please build from any of the tagged
> commits instead:
> 
> https://github.com/POV-Ray/povray/tags
> 
> The issue you've encountered should already be fixed in the latest and
> greatest of those versions (currently v3.8.0-alpha.9387404).
> 
I've used the povray-master file before and it always worked.
tried 3.7.0.3 and it failed with the same error
3.7.0.4 works

I prefer to stay clear of anything that has "alpha" in the version and 
if I read you correct the master is the very latest uploaded and it's 
not guaranteed to work.
-- 
cheers
Ger

Post a reply to this message

Am 01.12.2017 um 00:00 schrieb Ger:
> On 11/30/2017 03:21 PM, clipka wrote:
>> Am 30.11.2017 um 21:15 schrieb Ger:
>>> When trying to compile the latest povray-master on the latest opensuse
>>> tumbleweed I get the following
>>
>> As mentioned in the project's `README.md` file, we generally discourage
>> building from the master branch. Please build from any of the tagged
>> commits instead:
>>
>> https://github.com/POV-Ray/povray/tags
>>
>> The issue you've encountered should already be fixed in the latest and
>> greatest of those versions (currently v3.8.0-alpha.9387404).
>>
> I've used the povray-master file before and it always worked.
> tried 3.7.0.3 and it failed with the same error
> 3.7.0.4 works
> 
> I prefer to stay clear of anything that has "alpha" in the version and
> if I read you correct the master is the very latest uploaded and it's
> not guaranteed to work.

All our code is automatically test-built on various platforms (four of
them, to be precise), and if any of the test builds fails, we make it a
habit of fixing the code in a timely fashion. Moreover, we will never
tag such a broken version.

The problem you're suffering from was caused by a breaking change in the
boost libraries, which is beyond our control. We cannot avoid such
breakage, we can only clean up the damage after the fact. That hasn't
happened yet in the master branch.

The current master branch happens to /not/ be the latest uploaded code.
That would happen to be the `hotfix/issue_339` branch (which is a
3.7.0.4 derivative). However, the "latest and greatest" code is
currently maintained in the `release/v3.8.0` branch, which happens to be
at alpha stage.

BTW, the current master branch also has "alpha" in its version. It's
actually even more "alpha" than any tagged version, in that it doesn't
even have a dedicated pre-release ID number after the "alpha".


`release/v3.8.0` is where we maintain the version that's ultimately
going to become v3.8.0.

`master` is where we maintain any changes that are to be released in a
later version.

Since we're currently focusing on v3.8.0, that's where most changes are
happening; from time to time they will be merged into the master branch,
but at times the master branch may lag behind.

The old v3.7.0 is maintained in an entirely separate branch, and only
gets occasional updates to keep it "alive" (read: compile with modern
compilers and 3rd party libraries such as boost).


I hope this clarifies things a bit.

Post a reply to this message

On 12/01/2017 02:52 AM, clipka wrote:
...
> 
> `release/v3.8.0` is where we maintain the version that's ultimately
> going to become v3.8.0.
> 
> `master` is where we maintain any changes that are to be released in a
> later version.
> 
...
This last statement is of course why those of us with patches/branches 
create and maintain them off the 'master' branch - whether or not our 
work is aimed at POV-Ray proper.

While I understand the resource constraints, the 'master' branch 
breaking over time due environmental changes - and not getting timely 
updates for such breakage - effectively stalls, or makes more 
complicated(1), ongoing fix/feature development.

In addition, the master branch falling considerably behind makes it more 
likely future re-bases of our branches to master will be messy.

Bill P.

(1) - I've started to use git's 'cherry-pick' feature to pull 
'release/v3.8.0' commits into my: 'master' + 'all_my_own_branches' + 
'some_3.8_stuff' version of POV-Ray. I've not yet needed the tr1 boost 
update(s), so I don't have that update handy for pushing onto github for 
a possible merge into master. Aside: The change log and other 
documentation files are problematic when using the cherry-pick feature 
as are multiple-commit-single-fix/features and many-features/fixes 
commits...

Post a reply to this message

FYI, `master` branch is now back up to date.

Post a reply to this message

On 12/02/2017 06:45 PM, clipka wrote:
> FYI, `master` branch is now back up to date.
> 
Thank you!

Post a reply to this message