Opened 11 years ago

Closed 11 years ago

#41858 closed defect (wontfix)

libvmime: ERROR: GNU TLS development package is not installed

Reported by: darylew@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: Cc: ryandesign (Ryan Carsten Schmidt)
Port: libvmime

Description

I've been reading up on libvmime. I saw the requirements and installed them with Mac Ports, then I checked and saw that libvmime itself was in MacPorts. It didn't work. Doing a clean and re-install didn't work. Nor did trying with LLVM/GCC-4.2 work. Looking at the last parts of the log, it seems that there's a problem with libvmime think I didn't have GNU TLS, but I installed it before trying libvmime!

Attachments (1)

main.log (49.1 KB) - added by darylew@… 11 years ago.
Log file created when libvmime build failed.

Download all attachments as: .zip

Change History (2)

Changed 11 years ago by darylew@…

Attachment: main.log added

Log file created when libvmime build failed.

comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added
Port: gnutls removed
Resolution: wontfix
Status: newclosed
Summary: libvmime does not build with Mavericks, problem with GNU TLSlibvmime: ERROR: GNU TLS development package is not installed

This is because:

  • libvmime's scons script gets a list of all installed pkg-config files, and fails to find the libraries it's looking for if any installed pkg-config file has a problem. I have already reported this problem to the developers of libvmime, and they're not doing anything about it because they've already replaced the scons build system with something else but haven't released a new version of libvmime with these changes.
  • cyrus-sasl2's pkg-config file has a bug: #41300.

The workaround is to deactivate the cyrus-sasl2 port for the duration of the libvmime build.

sudo port clean libvmime
sudo port -f deactivate cyrus-sasl2
sudo port install libvmime
sudo port activate cyrus-sasl2

Last I checked that won't work either, however, because of #41292, which I have also already reported to the developers, and which they have not yet responded to. Perhaps you could add a note to that upstream issue and encourage the developers to release a new version that fixes the problem.

Note: See TracTickets for help on using tickets.