 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 11.01.2017 um 17:09 schrieb LanuHum:
> I have another computer. AMD (1 kernel,1 thread) Povray has not been set. It was
> the first compilation.
> ...../configure --prefix=/usr COMPILED_BY=Lanuhum no problem
> make no problem
> make install no problem
> run povray - problem
There is little we can do if all the feedback we get is "run povray -
problem".
/What/ problem?
Are you talking about the same symptoms as those mentioned in the other
post? If so, then see the response to that post for what additional
information might help us help you.
> Previously, I have a hundred times povray created from the source code.
> Sometimes it was a configuration error.
> This case (beta 2) is the first.
>
> Now I installed 3.7.0 of the repository - no problem.
It would be interesting to know whether the latest tagged alpha
(v3.7.1-alpha.8927145) works better than the beta. Since we've made only
very few changes to the source code since then, that would give us a
clear hint where to search for things that might be going wrong.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 11.01.2017 um 17:09 schrieb LanuHum:
> I have another computer. AMD (1 kernel,1 thread) Povray has not been set. It was
> the first compilation.
> ...../configure --prefix=/usr COMPILED_BY=Lanuhum no problem
> make no problem
> make install no problem
> run povray - problem
BTW, did you try "make check" before "make install"?
That should give an indication whether the problem is with the binary
itself, or with how it gets installed.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymous org> wrote:
> Am 11.01.2017 um 17:09 schrieb LanuHum:
>
> > I have another computer. AMD (1 kernel,1 thread) Povray has not been set. It was
> > the first compilation.
> > ...../configure --prefix=/usr COMPILED_BY=Lanuhum no problem
> > make no problem
> > make install no problem
> > run povray - problem
>
> There is little we can do if all the feedback we get is "run povray -
> problem".
>
> /What/ problem?
>
While only I see it:
Error in `/usr/bin/povray': free(): invalid next size (fast): 0x00007f2ff0017120
Creation of the source code takes a lot of time.
In my free time, I try more...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
El 11/01/17 a las 06:59, clipka escribió:
> POV-Ray 3.7.1 has now officially entered public beta testing phase.
> Source code and Windows binaries are available on GitHub:
>
> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>
> (beta.1 was an internal release only.)
>
> The beta version is designed to install in its own dedicated
> directory, and live happily alongside an existing 3.7 installation.
>
> Happy testing!
>
Compiled fine on Ubuntu 16.04, and seems to be working correctly with
a few existing scenes.
Thanks... this was maybe what I needed to get out of lethargy.
--
jaime
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 01/11/2017 07:02 PM, LanuHum wrote:
>>> I have another computer. AMD (1 kernel,1 thread) Povray has not been set. It was
>>> the first compilation.
>>> ...../configure --prefix=/usr COMPILED_BY=Lanuhum no problem
>>> make no problem
>>> make install no problem
>>> run povray - problem
>>
>> There is little we can do if all the feedback we get is "run povray -
>> problem".
>>
>> /What/ problem?
>>
>
> While only I see it:
> Error in `/usr/bin/povray': free(): invalid next size (fast): 0x00007f2ff0017120
$ man 3 mallopt
can give some help for trying to solve the problem...
> Creation of the source code takes a lot of time.
> In my free time, I try more...
>
>
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/01/2017 12:59 AM, clipka wrote:
> POV-Ray 3.7.1 has now officially entered public beta testing phase.
> Source code and Windows binaries are available on GitHub:
>
> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>
> (beta.1 was an internal release only.)
>
> The beta version is designed to install in its own dedicated directory,
> and live happily alongside an existing 3.7 installation.
>
> Happy testing!
>
Will we be supporting WinXP 32 anymore?
A quick test suggests the render works, may have problems with editor.
More testing on Sunday morning local time.
Stephen S
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/01/2017 12:59 AM, clipka wrote:
> POV-Ray 3.7.1 has now officially entered public beta testing phase.
> Source code and Windows binaries are available on GitHub:
>
> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>
> (beta.1 was an internal release only.)
>
> The beta version is designed to install in its own dedicated directory,
> and live happily alongside an existing 3.7 installation.
>
> Happy testing!
>
Will we be supporting WinXP 32 anymore?
A quick test suggests the render works, may have problems with editor.
More testing on Sunday morning local time.
Stephen S
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 13.01.2017 um 12:30 schrieb StephenS:
> On 11/01/2017 12:59 AM, clipka wrote:
>> POV-Ray 3.7.1 has now officially entered public beta testing phase.
>> Source code and Windows binaries are available on GitHub:
>>
>> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>>
>> (beta.1 was an internal release only.)
>>
>> The beta version is designed to install in its own dedicated directory,
>> and live happily alongside an existing 3.7 installation.
>>
>> Happy testing!
>>
> Will we be supporting WinXP 32 anymore?
To all my current knowledge, the beta versions should work fine with XP.
In contrast to the alpha development binary-only builds, which were a
byproduct of automated build testing using a 3rd party service running
Visual Studio 2015 (which we couldn't get to spit out fully XP-comatible
binaries), the beta release was lovingly hand-crafted with good old
Visual Studio 2010, and we intend to do the same for all further 3.7.1
releases (betas, RCs and final release).
As for 32 bit, the installer contains all three binaries (32 bit, 32 bit
SSE2, and 64 bit) and should pick the one most appropriate for your machine.
Thus, should you encounter any problems with the beta on a 32 bit
Windows XP, please do let us know, as that would be unintentional.
> A quick test suggests the render works, may have problems with editor.
> More testing on Sunday morning local time.
Hm... I'll have to check with Chris whether he also used Visual Studio
2010 for the beta editor DLLs. (The beta does need its own version of
the DLLs to not interfere with an existing installation of 3.7.0 proper.
Other than that they should be interchangeable, though the beta DLLs
also contain some bugfixes.)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 13.01.2017 um 13:30 schrieb clipka:
>> Will we be supporting WinXP 32 anymore?
...
>> A quick test suggests the render works, may have problems with editor.
>> More testing on Sunday morning local time.
>
> Hm... I'll have to check with Chris whether he also used Visual Studio
> 2010 for the beta editor DLLs. (The beta does need its own version of
> the DLLs to not interfere with an existing installation of 3.7.0 proper.
> Other than that they should be interchangeable, though the beta DLLs
> also contain some bugfixes.)
Chris just informed me that the editor DLLs have been built with Visual
Studio 2015, so they may or may not work on XP. Please do let us know
how you're faring.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1/11/2017 12:59 AM, clipka wrote:
> POV-Ray 3.7.1 has now officially entered public beta testing phase.
> Source code and Windows binaries are available on GitHub:
>
> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>
> (beta.1 was an internal release only.)
>
> The beta version is designed to install in its own dedicated directory,
> and live happily alongside an existing 3.7 installation.
>
> Happy testing!
>
well since i'm not a doze user perhaps it's just me but ... this release
seems to be having trouble honoring the Display = On option in the
master povray.ini file as well as having it in a povray.ini file in the
directory that the povray sdl file resides. In order to get a render
display i have to add +d in toolbar command line. btw: it (beta) is
reading all the other options (library path) options that i have in the
master povray.ini file
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
