octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Compiling with Qhull


From: Ben Abbott
Subject: Re: Compiling with Qhull
Date: Tue, 17 Jan 2012 10:50:25 -0500

On Jan 17, 2012, at 10:42 AM, Jarno Rajahalme wrote:

> 
> On Jan 14, 2012, at 4:09 , ext Ben Abbott wrote:
> 
>> On Jan 13, 2012, at 2:17 PM, Muhali wrote:
>> 
>>>> I tried that version on MacOS 10.7.2 with gcc 4.5, but encountered an error
>>>> with the "voronoi" diagram ...
>>>> 
>>>>    ../../run-octave -f -q -H -p . --eval "geometryimages ('voronoi', 
>>>> 'eps');"
>>> 
>>> I have the same problem now when trying to compile the current stable tip
>>> (81ee6b12adbc). Here is what I get (running Ubuntu Natty):
>>> 
>>> make[3]: Entering directory `/usr/src/octave/doc/interpreter'
>>> ../../run-octave -f -q -H -p . --eval "geometryimages ('voronoi', 'eps');"
>>> panic: Segmentation fault -- stopping myself...
>>> attempting to save variables to `octave-core'...
>>> save to `octave-core' complete
>>> make[3]: *** [voronoi.eps] Segmentation fault
>>> 
>>> M.
>> 
>> What version of qhull do you have installed ?
>> 
>> If it is qhull-2011, you'll want to install the 2010 version, or apply the 
>> attached patch.
>> 
>> Ben
>> 
>> 
>> <qhull.diff>
> 
> I tried the patch, but still had one related failure on make check (using 
> qhull 2011):
> 
>>>>>> processing 
>>>>>> /Users/Shared/Development/octave-3.6.0/src/DLD-FUNCTIONS/convhulln.cc
>  ***** testif HAVE_QHULL
> cube = [0 0 0;1 0 0;1 1 0;0 1 0;0 0 1;1 0 1;1 1 1;0 1 1];
> [h, v] = convhulln (cube);
> assert (size (h), [6 4]); 
> h = sortrows (sort (h, 2), [1:4]);
> assert (h, [1 2 3 4; 1 2 5 6; 1 4 5 8; 2 3 6 7; 3 4 7 8; 5 6 7 8]);
> assert (v, 1, 10*eps);
> !!!!! test failed
> assert (size (h),[6, 4]) expected
>   6   4
> but got
>   12    3
> values do not match
> 
> This failure does not appear when using qhull 2010.
> 
> I'm using up-to-date macports to satisfy dependencies. 
> 
> Regards,
> 
>  Jarno

I'm seeing this same failure, but haven't had time to look into the problem.

Ben
 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]