[MacPorts] #64628: gnutls @3.6.16_3+dane+guile: compilation of guile objects fails

MacPorts noreply at macports.org
Tue Feb 8 21:22:29 UTC 2022


#64628: gnutls @3.6.16_3+dane+guile: compilation of guile objects fails
--------------------------+--------------------
  Reporter:  cooljeanius  |      Owner:  (none)
      Type:  defect       |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.7.1
Resolution:               |   Keywords:
      Port:  gnutls       |
--------------------------+--------------------

Comment (by ryandesign):

 gnutls @3.6.16_2+guile and earlier did not actually use guile if you were
 compiling with clang from Xcode 12 and later.
 [35edbee0b1af40d247ba890d562722af5843406c/macports-ports] correctly fixed
 that problem: gnutls @3.6.16_3+guile and later will now actually try to
 use guile. It builds fine for me with the +guile variant on macOS 10.15.7
 with Xcode 12.4.

 I see that the reporter here is using macOS 11.6.2 with Xcode 13.2.1 and
 is also using the +dane variant. Building with +guile and +dane variants
 still works for me on macOS 10.15.7.

 The relevant error in the log seems to me to be:

 {{{
 :info:build In procedure dynamic-link: file:
 "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_gnutls/gnutls/work/gnutls-3.6.16/guile/src
 /guile-gnutls-v-2", message: "file not found"
 }}}

 This "file not found" when trying to load guile-gnutls-v-2 was mentioned
 elsewhere as well, for example https://lists.gnupg.org/pipermail/gnutls-
 devel/2018-March/008552.html. There it says:

 > In particular, libltdl sometimes erroneously
 > reports “file not found” when the problem is something else (unresolved
 > symbol, etc.)

 This made me wonder if we we're looking at another instance of the well-
 known macOS 11+ libtool bug with undefined symbols. However, I was unable
 to reproduce the issue on another machine with macOS 11.6.3 and Xcode
 12.5, so that doesn't seem like a likely cause.

 My machines only have 8 processors; the log here is using 16 parallel
 jobs. Maybe that is relevant? Eric, please try continuing the build with
 parallel building disabled:

 {{{
 sudo port upgrade gnutls build.jobs=1
 }}}

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


More information about the macports-tickets mailing list