From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: compilation errors trying to build unzip on cygwin
Date: Sat, 13 Feb 2021 20:18:06 -0500 [thread overview]
Message-ID: <69f162ff-b9bc-0e24-376e-6d556b03d33c@cornell.edu> (raw)
In-Reply-To: <CAGB_HuRrhT1uCH=_MBAhKhEKkdzssDGBC5482vtBGbYUvp_oFw@mail.gmail.com>
On 2/13/2021 7:01 PM, Soren via Cygwin wrote:
> HI. HI!. I've been away from cygwin (and all computer programming
> /messing-about) fro several years. Still love Cygwin.
>
> I've gotan archive with the source for `unzip' and I am having trouble
> compiling that program. The is the output on the console:
>
> $ make
> gcc -c -DASM_CRC -DWIN32 -D__GW32__ -D_LARGEFILE_SOURCE=1
> -D_LARGEFILE64_SOURCE=1 -D_FILE_OFFSET_BITS=64 -Wall -O3 -fms-extensions
> -mms-bitfi
> elds -fno-exceptions -fomit-frame-pointer -march=i386 -mcpu=i686
> -idirafter e:/progra~1/gnuwin32/include -idirafter h:/glibc/include -DUNIXB
> ACKUP -DUSE_UNSHRINK -DACORN_FTYPE_NFS -DOS2_EAS -DUSE_CRYPT -Wall -o
> unzip.o -O3 -mtune=native -march=native unzip.c
You need to tell make to use the unix Makefile. See the unzip.cygport file in
the source for Cygwin's unzip package. You can get it from
https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/unzip.git
or by using Cygwin's setup program to download the source.
Ken
next prev parent reply other threads:[~2021-02-14 1:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 0:01 Soren
2021-02-14 1:18 ` Ken Brown [this message]
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
2021-02-14 4:59 ` Brian Inglis
[not found] <mailman.40438.1613431093.968053.cygwin@cygwin.com>
2021-02-16 3:38 ` Soren
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=69f162ff-b9bc-0e24-376e-6d556b03d33c@cornell.edu \
--to=kbrown@cornell.edu \
--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).