From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Packages of mingw64 i686/x86_64 openssl 1.1.1 are empty!
Date: Sat, 13 Aug 2022 19:04:41 +0200 [thread overview]
Message-ID: <87h72gyt06.fsf@Rainer.invalid> (raw)
In-Reply-To: <CADt9577wg3d7Fnvj35eHyviMpRVWoN1o6Jv1dmKYOoVSmSbNJQ@mail.gmail.com> (Carlo B.'s message of "Thu, 11 Aug 2022 11:06:29 +0200")
Carlo B. writes:
> Actually, if you get the "src" packages of openssl for mingw64 and you
> try to build them with cygport, it happens that includes, DLLs and
> libraries are installed directly into the *REAL* destination
> directory, into:
>
> /usr/x86_64-w64-mingw32/sys-root/mingw
>
> or:
>
> /usr/i686-w64-mingw32/sys-root/mingw
>
> instead of the installation directory created by cygport.
Thanks for the analysis of the error.
> I hope that you could fix them.
This should be fixed now.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
prev parent reply other threads:[~2022-08-13 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 9:06 Carlo B.
2022-08-13 17:04 ` Achim Gratz [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=87h72gyt06.fsf@Rainer.invalid \
--to=stromeko@nexgo.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).