From: Peter Ross <pross@xvid.org>
To: cygwin@cygwin.com
Subject: libgnutls-devel depends on missnig libtasn1.la file
Date: Sat, 10 Dec 2016 02:38:00 -0000 [thread overview]
Message-ID: <20161210023817.imnuvtfumnsvxrme@7c616c24653cac4f1c247e3ee013d12b> (raw)
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
Hi,
I am attempting to build softare (GNU libmicrohttpd) with cygport on x86, but am
getting errors when it links against libgnutls:
/usr/bin/sed: can't read /usr/lib/libtasn1.la: No such file or directory
libtool: error: '/usr/lib/libtasn1.la' is not a valid libtool archive
Likely cause:
Cygwin gnutls-devel 3.2.21-1 installs /usr/lib/libgnutls.la and this file references libtasn1.la
However /usr/lib/libtasn1.la has been removed as of libtans1-devel 0.49-1.
See announce message here: https://cygwin.com/ml/cygwin-announce/2016-08/msg00084.html .
Could the maintainers of libgnutls-devel and libtasn1 please resolve this!
Here is my libmicrohttpd.cygport file should you need to reproduce the problem:
http://pastebin.com/raw/HTwzpbXb
-- Peter
(A907 E02F A6E5 0CD2 34CD 20D2 6760 79C5 AC40 DD6B)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
next reply other threads:[~2016-12-10 2:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 2:38 Peter Ross [this message]
2016-12-10 19:27 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161210023817.imnuvtfumnsvxrme@7c616c24653cac4f1c247e3ee013d12b \
--to=pross@xvid.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).