<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr"><br></div><div dir="ltr">I have no definite suggestions but just looking at</div><div dir="ltr"><br></div><div dir="ltr"> <a href="https://ports.macports.org/port/enscript/builds/">https://ports.macports.org/port/enscript/builds/</a></div><div dir="ltr"><br></div><div dir="ltr">I see the builds for old OSes are themselves a good few years old now. Its possible I guess something else has updated that broke the port, and perhaps forcing a rebuild from source might help. Have you tried forcing a build from source ?</div><div dir="ltr"><br></div><div dir="ltr">Chris</div><div dir="ltr"><br><blockquote type="cite">On 21 Dec 2022, at 8:22 pm, Dave Horsfall <dave@horsfall.org> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>Anyone? I'm guessing that an update to a library broke something...</span><br><span></span><br><span>-- Dave</span><br><span></span><br><span>---------- Forwarded message ----------</span><br><span>Date: Mon, 19 Dec 2022 12:44:47 +1100 (EST)</span><br><span>From: Dave Horsfall <dave@horsfall.org></span><br><span>To: macports-users <macports-users@lists.macports.org></span><br><span>Subject: "enscript" no longer working</span><br><span></span><br><span>MacPorts 2.8.0 on High Sierra.</span><br><span></span><br><span>Has anyone else found that "enscript" has stopped working after some </span><br><span>software update or other? The symptom is that nothing is being printed, </span><br><span>although I can redirect the output to a file and print that instead so </span><br><span>it's obviously generating the correct PS output.</span><br><span></span><br><span>The installed version of "enscript" is 1.6.6, and reinstalling it makes no </span><br><span>difference; when I specify a dummy script in place of "lpr" it gets </span><br><span>invoked as it should, so the spawning mechanism seems to be OK.</span><br><span></span><br><span>Because it's a bit inconvenient to disable SIP right now I cannot trace </span><br><span>the thing to see exactly what's broken, so has anyone else noticed this </span><br><span>and can track it to a particular MP update?</span><br><span></span><br><span>Thanks.</span><br><span></span><br><span>-- Dave</span><br></div></blockquote></body></html>