Re: Long build?

> On Nov 6, 2018, at 10:27 AM, Ken Cunningham > wrote: > > > >> On Nov 6, 2018, at 7:15 AM, Adam Dershowitz > > wrote: >> >> touch -r dvisvgm.txt.in dvisvgm.txt > > Hangs on a touch, it appears. > > When I’ve seen this in the past, disabling parallel building

Re: Long build?

/usr/bin/sed --Adam > On Nov 6, 2018, at 11:49 AM, wrote: > > Interesting, what is the output of the following? > > $ which -a sed > > > Cheers! > Frank > >> On Nov 6, 2018, at 8:15 AM, Adam Dershowitz > > wrote: >> >> Trying it verbose was a good suggestion.

Re: Long build?

Interesting, what is the output of the following? $ which -a sed Cheers! Frank > On Nov 6, 2018, at 8:15 AM, Adam Dershowitz wrote: > > Trying it verbose was a good suggestion. For me, it still hangs, but I did > get some more info. Here are the last few lines, where it finally just

Re: Long build?

Trying it verbose was a good suggestion. For me, it still hangs, but I did get some more info. Here are the last few lines, where it finally just hangs: /bin/sh ../libtool --tag=CXX --mode=link /usr/bin/clang++ -std=gnu++11 -Wall -Wnon-virtual-dtor -Wno-mismatched-tags -I../libs/clipper

Re: Long build?

I also ran into this on my High Sierra machine this morning. I halted the job, restarted it in verbose mode, and it finished. > On Nov 6, 2018, at 8:49 AM, Adam Dershowitz wrote: > > I’ve done that. It just shows make at 98.8% cpu. When I’ve tried to sample, > I get a call chain that has a

Re: Long build?

I’ve done that. It just shows make at 98.8% cpu. When I’ve tried to sample, I get a call chain that has a lot of ??? (in make). I tried to add a screen shot of the call chain, since activity monitor won’t allow me to copy, but the message ended up being too large. The beginning of the call

Re: Long build?

As it seems so far you're the only one with the hiccup, you have to see what's happening. When it's stuck, run top to see what's eating up the clock. Activity Monitor or ps to see what's running. Possibly sample the process that's stuck .to see what it's doing. Ken > On Nov 6, 2018, at 06:31,

Re: Long build?

> On Nov 6, 2018, at 1:17 AM, Mojca Miklavec wrote: > > 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

Re: Long build?

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.

Long build?

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