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 ?
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
