From: Soren <somian08@gmail.com>
To: Marco Atzeri <marco.atzeri@gmail.com>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: compilation errors trying to build unzip on cygwin
Date: Mon, 15 Feb 2021 15:53:08 -0500 [thread overview]
Message-ID: <CAGB_HuS2A6gKQeQy5PwbZ1eHUkVn3SDcxcm=C9s5x6DO82NOzA@mail.gmail.com> (raw)
In-Reply-To: <fa1f66e1-21b9-ef42-a02c-db36e544e7a1@gmail.com>
On Mon, Feb 15, 2021 at 11:10 AM Marco Atzeri <marco.atzeri@gmail.com>
wrote:
>
> $ cygport unzip.cygport all
> ...
> Stripping executables:
> usr/bin/funzip.exe
> usr/bin/unzip.exe
> usr/bin/unzipsfx.exe
> Preparing debuginfo source files:
> 18 files
> >>> Packaging unzip-6.0-17.x86_64
> >>> Creating binary package(s)
> >>> unzip-6.0-17.tar.xz
> ...
> >>> unzip requires: bash cygwin libbz2_1
>
> have you tried to use cygport for
> repeating the patching and compiling step as current build ?
>
No. Oh! cygport! Well, I mentioned I'd been away from cygwin and all system
projects for several years. It seemed like a good idea, and so I installed
cygport and ran it, and got a clean successful build. Thank you very much
for your time, for testing the build for me, Marco. Onward and upward now.
Best,
Soren A.
next prev parent reply other threads:[~2021-02-15 20:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 2:34 Soren
2021-02-14 4:20 ` Marco Atzeri
[not found] ` <CAGB_HuT5U7_g7ZLwqVT-9q51B-gS-KmNFGFB5TevYAwaAbefVw@mail.gmail.com>
2021-02-15 16:10 ` Marco Atzeri
2021-02-15 20:53 ` Soren [this message]
2021-02-14 4:59 ` Brian Inglis
[not found] <mailman.40438.1613431093.968053.cygwin@cygwin.com>
2021-02-16 3:38 ` Soren
-- strict thread matches above, loose matches on Subject: below --
2021-02-14 0:01 Soren
2021-02-14 1:18 ` 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='CAGB_HuS2A6gKQeQy5PwbZ1eHUkVn3SDcxcm=C9s5x6DO82NOzA@mail.gmail.com' \
--to=somian08@gmail.com \
--cc=cygwin@cygwin.com \
--cc=marco.atzeri@gmail.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).