On Fri, Mar 22, 2024 at 11:32:49AM -0700, Malte Dehling wrote:
> On Fri, Mar 22, 2024 at 08:50:41AM +0100, Thomas Klausner wrote:
> > I'll attach the whole build log, perhaps you can find out what's
> > different between our systems (a missing dependency perhaps?).
>
> I see the following lines in your log (and many similar ones):
>
> dot: graph is too large for cairo-renderer bitmaps. Scaling by
> 0.0100269 to fit
> Error: Edge length 147796.289062 larger than maximum 65535 allowed.
> Check for overwide node(s).
> [...]
> /scratch/devel/RE-flex/work/RE-flex-4.1.2/doc/html/class_reflex__coll__graph.dot:1:
> error: Problems running dot: exit code=1, command='/usr/pkg/bin/dot',
> arguments='"/scratch/devel/RE-flex/work/RE-flex-4.1.2/doc/html/class_reflex__coll__graph.dot"
> -Tpng -o
> "/scratch/devel/RE-flex/work/RE-flex-4.1.2/doc/html/class_reflex__coll__graph.png"'
>
> So dot fails to generate the output .map and .png files and instead
> the .dot files are left in doc/html (which explains the PLIST issue.)
>
> I have the latest graphviz 8.1.0nb9 installed with only the default
> option (gd) enabled.
>
> My guess would be something went wrong before dot is even run. Can
> you have a look at $WRKSRC/doc/html/class_reflex__coll__graph.dot ?
> It should be a very simple graph of 23 nodes. On my system, the
> generated png is 1763x787 in size, nowhere near the cairo limit.
>
> I'll set up a clean system and see if I can replicate the issue there.
I was able to replicate the issue in a fresh NetBSD 10 RC6 test vm.
The file $WRKSRC/doc/html/class_reflex__coll__graph.dot generated is the
same between my main system and the test vm. The issue seems to be with
graphviz or one of its dependencies; even some very simple graphs
produce errors like the ones you were seeing. Try running
test-vm$ cat >test.dot <<END
digraph {
Node2 -> Node1 [label="test"];
Node3 -> Node2;
Node4 -> Node3;
}
END
test-vm$ dot test.dot -Tpng -o test.png
dot: graph is too large for cairo-renderer bitmaps. Scaling by 0.0445108 to fit
test-vm$ file test.png
test.png: PNG image data, 4 x 32767, 8-bit/color RGB, non-interlaced
test-vm$ dot test.dot
digraph {
graph [bb="0,0,62.365,1.4779e+06"];
node [label="\N"];
Node2 [height=0.5,
pos="31.182,1.4777e+06",
width=0.86618];
Node1 [height=0.5,
pos="31.182,18",
width=0.86618];
Node2 -> Node1 [label=test,
lp="46.182,7.3888e+05",
pos="e,31.182,36.352 31.182,1.4777e+06
31.182,1.4719e+06 31.182,7462.8 31.182,47.258"];
Node3 [height=0.5,
pos="31.182,1.4778e+06",
width=0.86618];
Node3 -> Node2 [pos="e,31.182,1.4778e+06 31.182,1.4778e+06
31.182,1.4778e+06 31.182,1.4778e+06 31.182,1.4778e+06"];
Node4 [height=0.5,
pos="31.182,1.4779e+06",
width=0.86618];
Node4 -> Node3 [pos="e,31.182,1.4778e+06 31.182,1.4779e+06
31.182,1.4779e+06 31.182,1.4779e+06 31.182,1.4779e+06"];
}
As you can see something is very wrong - the coordinates are off the
charts. This should produce a very simple graph, and on my main machine
it does:
main-machine$ dot test.dot
digraph {
graph [bb="0,0,87.685,271.25"];
node [label="\N"];
Node2 [height=0.5,
pos="43.842,107.25",
width=1.2178];
Node1 [height=0.5,
pos="43.842,18",
width=1.2178];
Node2 -> Node1 [label=test,
lp="57.717,62.625",
pos="e,43.842,36.202 43.842,89.012 43.842,77.062
43.842,60.881 43.842,47.084"];
Node3 [height=0.5,
pos="43.842,180.25",
width=1.2178];
Node3 -> Node2 [pos="e,43.842,125.28 43.842,162.06
43.842,154.3 43.842,144.93 43.842,136.2"];
Node4 [height=0.5,
pos="43.842,253.25",
width=1.2178];
Node4 -> Node3 [pos="e,43.842,198.28 43.842,235.06
43.842,227.3 43.842,217.93 43.842,209.2"];
}
Not sure what's going on here.
I do think the changes I proposed in this thread should be committed
since they're unrelated to the graphviz issue and fix real errors.
Cheers,
--
Malte Dehling
Attachment:
signature.asc
Description: PGP signature