From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: Advice on setting Cygwin build parameters for OpenSC.
Date: Sun, 02 Sep 2018 09:08:00 -0000 [thread overview]
Message-ID: <d7fea18b-5088-9751-0ef6-6b3d33183d72@t-online.de> (raw)
In-Reply-To: <BY1PR14MB015068FFCE2A1631A3DC7A32C40D0@BY1PR14MB0150.namprd14.prod.outlook.com>
Am 02.09.2018 um 03:22 schrieb Darren Whobrey:
> The tweak required to get OpenSC to work with the standard Cygwin
> utils, like ssh-agent, is to comment out a line in the configure.ac
> script that previously was causing it to force a WND build, which
> resulted in struct packing of 1 â and that doesnât work with the ssh
> utils distributed with Cygwin. For details see the end of thread
> here: https://github.com/OpenSC/OpenSC/issues/607.
That line is flat-out wrong. Delete it. You're already in a
--host=*cygwin* specific section of your configure.ac script, so there's
no further precautions to be taken.
While at it, you may just as well delete the entire "with_cygwin_native"
branch (lines 100..105), because that has been un-applicable for years.
Building for native windows (i.e. MinGW) is has long since stopped to
be done by a -mno-cygwin flag. Instead you would pass the configure
script a --host={something with mingw in it} flag to initiate a proper
cross-build, and that will bring you into the existing --host=*mingw*
case abvoe.
> The question is, what is the most sensible way to update the
> configure.ac and still support other Cygwin users that may be using
> mingw or other toolchains rather than gcc?
Checking for GCC is almost certainly a red herring here.
> should be to not include the offending line, but then that would
> break WND builds.
Not really, because whatever you mean by "WND builds", they won't be
ending up in that cygwin case.
--
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
next prev parent reply other threads:[~2018-09-02 9:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 1:22 Darren Whobrey
2018-09-02 9:08 ` Hans-Bernhard Bröker [this message]
2018-09-06 5:47 ` dwhobrey
2018-09-06 14:05 ` Andrey Repin
2018-09-06 16:25 ` Csaba Raduly
2018-09-09 3:41 ` cyg Simple
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=d7fea18b-5088-9751-0ef6-6b3d33183d72@t-online.de \
--to=hbbroeker@t-online.de \
--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).