[MacPorts] #59904: gnutls @3.6.6: fatal error: 'nettle/nettle-stdint.h' file not found

[MacPorts]

#59904: gnutls @3.6.6: fatal error: 'nettle/nettle-stdint.h' file not found
------------------------+-------------------------
  Reporter:  homer3018  |      Owner:  Schamschula
      Type:  defect     |     Status:  assigned
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.6.2
Resolution:             |   Keywords:
      Port:  gnutls     |
------------------------+-------------------------

Comment (by homer3018):

 Hi Ryan and thanks for replying !

 I'll try and answer your comments in order.
 >I see that you are using the latest nettle 3.5.1, but are building gnutls
 3.3.6. This is out of date, possibly to such a degree that it is
 incompatible with the latest nettle. The version of gnutls currently in
 MacPorts is 3.6.11.1.
 I have no idea why It's trying to install v 3.3.6 instead of 3.6.11.1,
 Trying
 {{{
 $ sudo port install gnutls @3.6.11.1
 Warning: cltversion: The Command Line Tools are installed, but MacPorts
 cannot determine the version.
 Warning: cltversion: For a possible fix, please see:
 https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt
 --->  Computing dependencies for gnutls
 --->  Building gnutls
 Error: Failed to build gnutls: command execution failed
 Error: See
 /opt/local/var/macports/logs/_Users_seb_ports_devel_gnutls/gnutls/main.log
 for details.
 Error: Follow https://guide.macports.org/#project.tickets to report a bug.
 Error: Processing of port gnutls failed
 }}}

 ends up the same way.

 >I see that you are building gnutls from a local Portfile in
 /Users/seb/ports/devel/gnutls.
 I have no idea why it is like so.
 >Try removing that Portfile and building our copy of the Portfile from the
 standard location instead.
 I'm sorry but I have no idea about how to do that either.

 I'm not doing any Portfiles development so I'm ok with trying it all again
 from scratch if needed, I'd just need some guidance about how to proceed
 from here. Maybe as you mentioned reverse the changes in `macports.conf`,
 `variants.conf` and `sources.conf` ?

 Maybe this is all some consequences when I upgraded to 10.15 and to
 MacPorts 2.6.2 ?

 As for contributing back to the port devs I'll make sure I'll start this
 conversation soon enough, it might just be easier for everyone.

 >Also, note that we have darktable in MacPorts (sudo port install
 darktable); you don't need to build it from source yourself nor do any
 patching of our Portfiles to install it.
 I'm a lot more familiar with Git so this is probably why I naturally lean
 toward it. I have no issues building it as often as needed. I'm just
 having this issue now (which might be related to the 10.15 upgrade along
 with migrating MacPorts to 2.6.2) but otherwise it's all good. I'm running
 Darktable 3.1.0 which is the dev version of the 3.0.0 release while the
 ports still seat at 2.6.3 which was the last release. Still I didn't even
 know there was a port so thank you for letting me know, and also for
 helping me out :)

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