From: Marco Atzeri <marco.atzeri@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: Soren <somian08@gmail.com>
Subject: Re: compilation errors trying to build unzip on cygwin
Date: Mon, 15 Feb 2021 17:10:33 +0100 [thread overview]
Message-ID: <fa1f66e1-21b9-ef42-a02c-db36e544e7a1@gmail.com> (raw)
In-Reply-To: <CAGB_HuT5U7_g7ZLwqVT-9q51B-gS-KmNFGFB5TevYAwaAbefVw@mail.gmail.com>
back on mailing list
On 15.02.2021 00:36, Soren wrote:
>
> On Sat, Feb 13, 2021 at 11:20 PM Marco Atzeri wrote:
>
>
> Well, that would be a simple fix, although it leaves the mystery PATH
> behavior unsolved. I'll mention that I moved gnwin32-make out of the way
> and then got compiler (assembler) errors. Here is my console output:
>
> $ /usr/bin/make -f unix/Makefile cygwin
> ln: failed to create hard link './Makefile': File exists
> /usr/bin/make unzips CC=gcc LD=gcc AS=gcc\
> CFLAGS="-O3 -DASM_CRC -DNO_LCHOWN -DNO_LCHMOD"\
> AF="-Di386 " CRCA_O=crc_gcc.o\
> E=".exe" CP="cp" LN="ln -s"
> make[1]: Entering directory '/usr/src/unzip-6.0-17.src/unzip60'
> gcc -Di386 -x assembler-with-cpp -c -o crc_gcc.o crc_i386.S
> crc_i386.S: Assembler messages:
> crc_i386.S:203: Error: invalid instruction suffix for `push'
> crc_i386.S:204: Error: invalid instruction suffix for `push'
> crc_i386.S:205: Error: invalid instruction suffix for `push'
> crc_i386.S:206: Error: invalid instruction suffix for `push'
> crc_i386.S:207: Error: invalid instruction suffix for `push'
> crc_i386.S:208: Error: invalid instruction suffix for `push'
> crc_i386.S:292: Error: invalid instruction suffix for `pop'
> crc_i386.S:293: Error: invalid instruction suffix for `pop'
> crc_i386.S:294: Error: invalid instruction suffix for `pop'
> crc_i386.S:295: Error: invalid instruction suffix for `pop'
> crc_i386.S:296: Error: invalid instruction suffix for `pop'
> crc_i386.S:297: Error: invalid instruction suffix for `pop'
> make[1]: *** [Makefile:381: crc_gcc.o] Error 1
> make[1]: Leaving directory '/usr/src/unzip-6.0-17.src/unzip60'
> make: *** [unix/Makefile:749: cygwin] Error 2
>
> Thanks to any persons who are following this thread.
compiling the latest source shows no issue at all
from my side with a recent 64bit Cygwin.
$ 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 ?
next prev parent reply other threads:[~2021-02-15 16:10 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 [this message]
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
-- 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=fa1f66e1-21b9-ef42-a02c-db36e544e7a1@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
--cc=somian08@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).