#58919: fontforge build failure on 10.7.5

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

#58919: fontforge build failure on 10.7.5

macports-4
#58919: fontforge build failure on 10.7.5
----------------------+-----------------------
 Reporter:  lemzwerg  |      Owner:  (none)
     Type:  defect    |     Status:  new
 Priority:  Normal    |  Milestone:
Component:  ports     |    Version:
 Keywords:  lion      |       Port:  fontforge
----------------------+-----------------------
 Building recently upgraded fontforge fails with
 {{{
 :info:build scripting.c:10698:1: error: unknown type name '_Noreturn'
 :info:build _Noreturn void ProcessNativeScript(int argc, char *argv[],
 FILE *script) {
 :info:build ^
 }}}

--
Ticket URL: <https://trac.macports.org/ticket/58919>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: #58919: fontforge build failure on 10.7.5

macports-4
#58919: fontforge build failure on 10.7.5
------------------------+--------------------
  Reporter:  lemzwerg   |      Owner:  (none)
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:             |   Keywords:  lion
      Port:  fontforge  |
------------------------+--------------------
Changes (by lemzwerg):

 * Attachment "main.log.xz" added.

 main.log file of fontforge build on lion

--
Ticket URL: <https://trac.macports.org/ticket/58919>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: #58919: fontforge build failure on 10.7.5

macports-4
In reply to this post by macports-4
#58919: fontforge build failure on 10.7.5
------------------------+--------------------
  Reporter:  lemzwerg   |      Owner:  (none)
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:             |   Keywords:  lion
      Port:  fontforge  |
------------------------+--------------------

Comment (by kencu):

 Interesting. It's OK on 10.6.8:
 {{{
 fontforge @20190801_0+gui+python37 (active) platform='darwin 10'
 archs='x86_64' date='2019-09-02T21:34:12-0700'
 }}}
 built with clang-5.0/libc++.

--
Ticket URL: <https://trac.macports.org/ticket/58919#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: #58919: fontforge build failure on 10.7.5

macports-4
In reply to this post by macports-4
#58919: fontforge build failure on 10.7.5
------------------------+--------------------
  Reporter:  lemzwerg   |      Owner:  (none)
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:             |   Keywords:  lion
      Port:  fontforge  |
------------------------+--------------------

Comment (by lemzwerg):

 Maybe it's because I neither have `gui` nor `python37`?

--
Ticket URL: <https://trac.macports.org/ticket/58919#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: #58919: fontforge build failure on 10.7.5

macports-4
In reply to this post by macports-4
#58919: fontforge build failure on 10.7.5
------------------------+--------------------
  Reporter:  lemzwerg   |      Owner:  (none)
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:             |   Keywords:  lion
      Port:  fontforge  |
------------------------+--------------------

Comment (by kencu):

 Replying to [comment:2 lemzwerg]:
 > Maybe it's because I neither have `gui` nor `python37`?
 More likely the default `/usr/bin/clang` is just too old and rickety to
 build it. The new MacPorts 2.6 will default to a newer compiler, but for
 now, you can try this:
 {{{
 sudo port -v install fontforge configure.compiler=macports-clang-5.0
 }}}
 I know `clang-5.0` works. Probably `clang-8.0` will work too. Feel free to
 build the gui and the python bindings if you care to -- that fontforge gui
 is pretty cool!

--
Ticket URL: <https://trac.macports.org/ticket/58919#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: #58919: fontforge build failure on 10.7.5

macports-4
In reply to this post by macports-4
#58919: fontforge build failure on 10.7.5
------------------------+--------------------
  Reporter:  lemzwerg   |      Owner:  (none)
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:             |   Keywords:  lion
      Port:  fontforge  |
------------------------+--------------------

Comment (by lemzwerg):

 Hmm.  I am using the current git version of `macports-base`, which is
 essentially a beta of 2.6 – so why is `/usr/bin/clang++` selected by
 default?

 Regarding GUI: I'm not a Mac user at all – I control my Mac using a `mosh`
 terminal from my GNU/Linux box :-)  I exclusively use it to test software
 builds, in particular LilyPond.

 And compilation with `clang-5.0` succeeded, thanks.

--
Ticket URL: <https://trac.macports.org/ticket/58919#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: #58919: fontforge build failure on 10.7.5

macports-4
In reply to this post by macports-4
#58919: fontforge build failure on 10.7.5
------------------------+--------------------
  Reporter:  lemzwerg   |      Owner:  (none)
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:             |   Keywords:  lion
      Port:  fontforge  |
------------------------+--------------------

Comment (by jmroot):

 2.6 will still try the system clang if it can use the selected stdlib. So
 on 10.7 and later, more or less.

 Here, _Noreturn is a C11 feature, so it should at least be using the
 appropriate -std= option. Compilers that don't support C11 also need to be
 excluded. With 2.6 we could just set compiler.c_standard, but for now we
 just have to do some blacklisting.

--
Ticket URL: <https://trac.macports.org/ticket/58919#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: #58919: fontforge build failure on 10.7.5

macports-4
In reply to this post by macports-4
#58919: fontforge build failure on 10.7.5
------------------------+--------------------
  Reporter:  lemzwerg   |      Owner:  (none)
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:             |   Keywords:  lion
      Port:  fontforge  |
------------------------+--------------------

Comment (by lemzwerg):

 OK, thanks for the info – Ken, is this something to be fixed in the
 Portfile?

 Note that the forthcoming version of FontForge switches to cmake; I've
 just checked that a test for C++11 is included.

--
Ticket URL: <https://trac.macports.org/ticket/58919#comment:6>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: #58919: fontforge build failure on 10.7.5

macports-4
In reply to this post by macports-4
#58919: fontforge build failure on 10.7.5
------------------------+--------------------
  Reporter:  lemzwerg   |      Owner:  jmroot
      Type:  defect     |     Status:  closed
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:  fixed      |   Keywords:  lion
      Port:  fontforge  |
------------------------+--------------------
Changes (by jmroot):

 * status:  new => closed
 * owner:  (none) => jmroot
 * resolution:   => fixed


Comment:

 In [changeset:"fcf2a3773d75c01e215798574a849c4989fb3201/macports-ports"
 fcf2a3773d75c01e215798574a849c4989fb3201/macports-ports] (master):
 {{{
 #!ConfigurableCommitTicketReference repository="macports-ports"
 revision="fcf2a3773d75c01e215798574a849c4989fb3201"
 fontforge: various fixes

  * Require C11 compiler
  * Fix default variant
  * Remove old workaround

 Closes: https://trac.macports.org/ticket/58919
 }}}

--
Ticket URL: <https://trac.macports.org/ticket/58919#comment:7>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: #58919: fontforge build failure on 10.7.5

macports-4
In reply to this post by macports-4
#58919: fontforge build failure on 10.7.5
------------------------+----------------------
  Reporter:  lemzwerg   |      Owner:  jmroot
      Type:  defect     |     Status:  reopened
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:             |   Keywords:  lion
      Port:  fontforge  |
------------------------+----------------------
Changes (by jmroot):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 Hmm, well that didn't actually fix 10.7. It built on 10.6 though. :)

 Guess I'll try restricting to the next Xcode version up.

--
Ticket URL: <https://trac.macports.org/ticket/58919#comment:8>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: #58919: fontforge build failure on 10.7.5

macports-4
In reply to this post by macports-4
#58919: fontforge build failure on 10.7.5
------------------------+----------------------
  Reporter:  lemzwerg   |      Owner:  jmroot
      Type:  defect     |     Status:  reopened
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:             |   Keywords:  lion
      Port:  fontforge  |
------------------------+----------------------

Comment (by jmroot):

 Replying to [comment:6 lemzwerg]:
 > Note that the forthcoming version of FontForge switches to cmake; I've
 just checked that a test for C++11 is included.

 This failure was specifically on C code, so I don't know if it does need
 C++11.

--
Ticket URL: <https://trac.macports.org/ticket/58919#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: #58919: fontforge build failure on 10.7.5

macports-4
In reply to this post by macports-4
#58919: fontforge build failure on 10.7.5
------------------------+----------------------
  Reporter:  lemzwerg   |      Owner:  jmroot
      Type:  defect     |     Status:  reopened
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:             |   Keywords:  lion
      Port:  fontforge  |
------------------------+----------------------

Comment (by jmroot):

 In [changeset:"b2aa03d07f09b9f281a9487d2e37dab2ae3ba50f/macports-ports"
 b2aa03d07f09b9f281a9487d2e37dab2ae3ba50f/macports-ports] (master):
 {{{
 #!ConfigurableCommitTicketReference repository="macports-ports"
 revision="b2aa03d07f09b9f281a9487d2e37dab2ae3ba50f"
 fontforge: adjust compiler blacklist

 Clang from Xcode 4.6.3 doesn't seem to work, so restrict to 5.0 and up.

 See: https://trac.macports.org/ticket/58919
 }}}

--
Ticket URL: <https://trac.macports.org/ticket/58919#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: #58919: fontforge build failure on 10.7.5

macports-4
In reply to this post by macports-4
#58919: fontforge build failure on 10.7.5
------------------------+--------------------
  Reporter:  lemzwerg   |      Owner:  jmroot
      Type:  defect     |     Status:  closed
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:  fixed      |   Keywords:  lion
      Port:  fontforge  |
------------------------+--------------------
Changes (by jmroot):

 * status:  reopened => closed
 * resolution:   => fixed


--
Ticket URL: <https://trac.macports.org/ticket/58919#comment:11>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: #58919: fontforge build failure on 10.7.5

macports-4
In reply to this post by macports-4
#58919: fontforge build failure on 10.7.5
------------------------+--------------------
  Reporter:  lemzwerg   |      Owner:  jmroot
      Type:  defect     |     Status:  closed
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:  fixed      |   Keywords:  lion
      Port:  fontforge  |
------------------------+--------------------

Comment (by kencu):

 a large amount of compiler fussing on Macports would be eliminated if 10.7
 and 10.8 (and 10.9...) defaulted their compilers to match 10.6 ...

 Is there any resson to not do that, and make everyone's life easier?

 The more these older systems work exactly like current ones, the less
 headaches we all will have.

--
Ticket URL: <https://trac.macports.org/ticket/58919#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: #58919: fontforge build failure on 10.7.5

macports-4
In reply to this post by macports-4
#58919: fontforge build failure on 10.7.5
------------------------+--------------------
  Reporter:  lemzwerg   |      Owner:  jmroot
      Type:  defect     |     Status:  closed
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:  fixed      |   Keywords:  lion
      Port:  fontforge  |
------------------------+--------------------

Comment (by ryandesign):

 In [changeset:"6634ca1cbc2682d4a32e9bfe7f88720ae392695f/macports-ports"
 6634ca1cbc2682d4a32e9bfe7f88720ae392695f/macports-ports] (master):
 {{{
 #!ConfigurableCommitTicketReference repository="macports-ports"
 revision="6634ca1cbc2682d4a32e9bfe7f88720ae392695f"
 fontforge: Blacklist clang < 500

 Re-fixes https://trac.macports.org/ticket/58919
 }}}

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