I’m upgrading dvisvgm from to 2.3.4_4 to 2.6.1_0. I’m on a fairly recent
MacBook pro, and it has been building for 13 hours! The process is “make” and
it’s taking 100% of just one CPU. Does this sound correct? Should I just kill
it and clean the port, then retry? Even building gcc from sour
Dear Adam,
On Tue, 6 Nov 2018 at 05:24, Adam Dershowitz wrote:
>
> I’m upgrading dvisvgm from to 2.3.4_4 to 2.6.1_0. I’m on a fairly recent
> MacBook pro, and it has been building for 13 hours! The process is “make”
> and it’s taking 100% of just one CPU. Does this sound correct?
No. Anythin
> On Nov 6, 2018, at 00:17, Mojca Miklavec wrote:
>
> However the folder for dvisvgm doesn't exist due to:
>
>$ port_binary_distributable.tcl -v dvisvgm
>"dvisvgm" is not distributable because its license "GPL-3+"
> conflicts with license "GPL-2" of dependency "libpaper"
>
> (I wasn't
