[MacPorts] #61536: asymptote @2.65 build on Big Sur causes kernel panic, does not work on El Capitan or Catalina either

[MacPorts]

#61536: asymptote @2.65 build on Big Sur causes kernel panic, does not work on El
Capitan or Catalina either
------------------------+----------------------
  Reporter:  snowflake  |      Owner:  mojca
      Type:  defect     |     Status:  assigned
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.6.99
Resolution:             |   Keywords:
      Port:  asymptote  |
------------------------+----------------------

Comment (by snowflake):

 I've been doing some builds on Catalina using a Portfile with null code
 for fetch, checksum, and extract. This is so I can build with a script
 which copies the checkout to the Macports work areas.

 It appears that the source went from broken to working to broken again in
 the space of 4 hours.

 Here are the results:
 {{{
 --------------------------------------------
 commit 42b291049920c2a023ab5f3598cc917eb36297ca (HEAD)
 Merge: e62d0401 d9826965
 Author: John Bowman <bowman at ualberta.ca>
 Date:   Sun Oct 25 20:18:21 2020 -0600

 *** Severe Memory Leak (many GB) ***
 --------------------------------------------
 commit 3361214340d58235f4dbb8f24017d0cd5d94da72 (HEAD)
 Author: John Bowman <bowman at ualberta.ca>
 Date:   Sun Oct 25 22:24:51 2020 -0600

 *** builds and works without memory leak ***

 Use ps2write instead of eps2write where possible,
     for compatibility with gs 9.53.
 --------------------------------------------
 commit e688d42e33a521facdb050c77b454b819478d3fd (HEAD)
 Author: John Bowman <bowman at ualberta.ca>
 Date:   Sun Oct 25 23:08:36 2020 -0600

 *** BUILD ERRORS ***
 In file included from util.cc:33:
 ./locate.h:21:61: error: default argument references parameter 'suffix'
 string locateFile(string id, bool full=false, string suffix=suffix);
 There are many of these errors.
 --------------------------------------------

 }}}
 I'm not convinced that switching from eps2write to ps2write has fixed the
 memory leak. It is still in the background waiting to pounce.

-- 
Ticket URL: <https://trac.macports.org/ticket/61536#comment:13>
MacPorts <https://www.macports.org/>
Ports system for macOS