From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: How is libgssapi_krb5_2 built on cygwin?
Date: Thu, 05 Apr 2018 00:26:00 -0000 [thread overview]
Message-ID: <ab4e6bdd-f8c5-dd5d-43ba-853c0baa8d08@SystematicSw.ab.ca> (raw)
In-Reply-To: <94CC0760-7645-4BB2-982B-4CE3BFAB8FD1@oracle.com>
On 2018-04-04 17:13, Weijun Wang wrote:
> I am thinking about building MIT krb5 on Windows with cygwin but using the
> source distribution from MIT [1] shows this error:
> configure: error: Shared libraries are not yet supported on this platform.
> I'd like to know how cygwin compiles the libgssapi_krb5_2 packgae. Do you
> have a patch I can apply?
> [1] https://web.mit.edu/KERBEROS/dist/index.html
Cygwin supplies a number of ...krb5... packages from MIT reference sources.
Search packages from the link on the Cygwin home page e.g.
https://cygwin.com/cgi-bin2/package-grep.cgi?grep=krb5&arch=x86_64
which looks like there is only one krb5 source package krb5-1.15.2-2-src
viewable as:
https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Fkrb5%2Fkrb5-1.15.2-2-src&grep=krb5
which shows a number of patches, including Cygwin specific patches, and another
source package for krb5-auth-dialog.
Almost all Cygwin packages now use cygport for building (and packaging).
Download the krb5 source package, have a look at it, and how the packages are
built from the .cygport file.
Install the cygport package, maybe libkrb5-devel and sources, try a build, then
look at adapting that package build for your sources, if different.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2018-04-05 0:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 23:17 Weijun Wang
2018-04-05 0:26 ` Brian Inglis [this message]
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=ab4e6bdd-f8c5-dd5d-43ba-853c0baa8d08@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).