POV-Ray : Newsgroups : povray.unofficial.patches : Hgpovray38, current state : Re: Hgpovray38, current state Server Time
18 Apr 2024 19:23:33 EDT (-0400)
  Re: Hgpovray38, current state  
From: clipka
Date: 13 Sep 2018 10:16:41
Message: <5b9a7149@news.povray.org>
Am 13.09.2018 um 11:29 schrieb jr:
> hi,
> 
> Le Forgeron <jgr### [at] freefr> wrote:
>> Le 12/09/2018 à 23:50, jr a écrit :
>>> downloaded the .tar.gz version and run into trouble -- make error when
>>> compilation gets to the maths/spline code.  log posted in p.binaries.misc.
>>
>> What age is your compiler ?
> 
> 4.8.2.  :-)

For the records, GCC 4.8.2 is feature-complete with respect to C++11.

> however, is that not a "red herring"?  I would expect './configure' to fail if
> the s/ware is .. not modern enough.

The question isn't that offbeat; as a matter of fact, the only reliable
way to test whether any given compiler will compile a given program is
to actually try compiling that program.

Case in point: gcc 4.8.2 (or, more precisely, the standard header files
that came with it), despite claiming full C++11 compliance, actually
isn't, due to a couple of bugs in the implementation of std::vector<T>.

And that seems to be exactly what you are seeing; I couldn't find a bug
report matching the /exact/ symptoms, but the error messages point to a
a non-standard-compliant interface of `std::vector<T>::insert`, and
there are bug reports of multiple other non-compliances of
`std::vector<T>`, such as this one:

    https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55817

Judging from when the other bugs were fixed, you'll probably need gcc
4.9 or later.


Post a reply to this message

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