I had an issue with lang/sbcl not working or compiling properly under Synth 1.66_1. The synth process suspends whenever it goes to build lang/sbcl. I was told to file a bug report by marino@ the maintainer of synth for this issue. There is a thread on the FreeBSD forums I started about this issue. The issue appears to have been introduced with the January 17, 2017 update of lang/sbcl. The forum thread has several people working on a fix for the issue. marino@ the maintainer of synth gives a workaround to get synth to work with the current lang/sbcl port: Here is the link to the forum post: https://forums.freebsd.org/threads/59430/ The workaround for now is this: 1) Create a second, nearly identical profile to LiveSystem, which the only difference is that the curses display is disabled. Only use the second profile to build sbcl 2) Run Synth inside screen or tmux and close the window so that tty is disconnected (and thus not broken) 3) As ASX suggested, keep one profile but just never use the curses display (the web display still works)
Add maintainer to CC (not sure why this wasn't done by bugzilla automatically)
Add reference to D9186 which documents significant issue about how this port was updated, specifically how the proper bootstrap was removed and replaced with CCL, breaking DF in the process. It should not have been approved and further work is required, naming changing the "SBCL" option from using an installed sbcl to bootstrap, replacing it to use proper packaged bootstraps. (and CCL option moved to non-default method) https://reviews.freebsd.org/D9186
By the way, synth version 1.67 was modified to ignore the TTY signals emitted by CCL during execution, which was responsible for the suspension during the build.
I addressed most of the major issues with sbcl update here: https://svnweb.freebsd.org/ports?view=revision&revision=432557 Even with sbcl bootstrap, the background TTY signals are getting emitted, so it seems specific to sbcl 1.13 build itself, not CCL. Since synth has been modified to handle it, and since there's apparently no issue on poudriere, let's close the report. I don't know what else can be done about it.