The first time you were alarmed that something took a long time to build, longer than you expected, but it built.
I still don't know what you are concerned about. It seems the issue is that sometimes it takes a lot longer to build than you expect? If packages are building and things are correct, what concerns you? it is not clear.
Yes, I thought that is something with ncurses. If I am running GNOME than I am checking what Synth doing (ctrl-alt-F?) and going back to GNOME.it sounds like are running synth in a resizable virtual terminal and then you resized the window. Or something else affected ncurses from working, dunno.
Yes, I do because sometimes I start GNOME and more often Fluxbox. I will do. Thank you and it was very interesting and educational for me, listening your interviewI don't know gnome. Are you saying you are switching between X and syscons with control-alt-F?
If you primarily use a desktop, I think I'd recommend opening xterm and running synth in a window there (perhaps within screen or tmux) and just stick that window on one of the desktops so you can check it whenever you want. Switching modes like that is probably ncurses doesn't like.
Why on earth is your ports tree trying to use the devel/libc++ port, when you are on FreeBSD 10.3-PRELEASE? This release has libc++ in the base system, and the port should use that instead...
Some people using synth noticed that libc++ gets rebuilt every time because it fails dependency check. I created a PR 207756 to help address the issue. Here is the latest reply from Dimitry who is maintainer of libc++:
Code:Why on earth is your ports tree trying to use the devel/libc++ port, when you are on FreeBSD 10.3-PRELEASE? This release has libc++ in the base system, and the port should use that instead...
Maybe Marino and Dmitry can contact each other directly to resolve the issue?
Some people using synth noticed that libc++ gets rebuilt every time because it fails dependency check. I created a PR 207756 to help address the issue. Here is the latest reply from Dimitry who is maintainer of libc++:
Maybe Marino and Dmitry can contact each other directly to resolve the issue?