From: lck <leeckp@nievax.nie.ac.sg>
To: gnu-win32@cygnus.com
Subject: bswap
Date: Sun, 01 Nov 1998 00:38:00 -0000 [thread overview]
Message-ID: <363C1F7E.77CD7700@nievax.nie.ac.sg> (raw)
After installing the B20 cygwin I get error message like the one below
where I did not with
the B19 with egcs1.1 port from Murmit Khan
gcc -I./Hardware -I./Includes -I/usr/include -I. -c -O6
-fomit-frame-pointer -fs
trict-aliasing -ffast-math -DREGPARAM="" -finline-functions
-fschedule-insns2 -f
unroll-all-loops -malign-double -D__inline__=inline -mcpu=i586
-march=i586 -mno-
cygwin Hardware/Nmemory.c -o Hardware/Nmemory.o
In file included from .\Includes\sysdeps.h:42,
from Hardware/Nmemory.c:9:
P:\H-I586-CYGWIN32\BIN\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\i58
6-cygwin32\include\sys\param.h:22: warning: `MAXPATHLEN' redefined
P:\H-I586-CYGWIN32\BIN\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\i58
6-cygwin32\include\sys/unistd.h:136: warning: this is the location of
the previo
us definition
C:\WINDOWS\TEMP\ccuPj6El.s: Assembler messages:
C:\WINDOWS\TEMP\ccuPj6El.s:2454: Error: suffix or operands invalid for
`bswap'
C:\WINDOWS\TEMP\ccuPj6El.s:2501: Error: suffix or operands invalid for
`bswap'
C:\WINDOWS\TEMP\ccuPj6El.s:2573: Error: suffix or operands invalid for
`bswap'
C:\WINDOWS\TEMP\ccuPj6El.s:2606: Error: suffix or operands invalid for
`bswap'
C:\WINDOWS\TEMP\ccuPj6El.s:2657: Error: suffix or operands invalid for
`bswap'
C:\WINDOWS\TEMP\ccuPj6El.s:2726: Error: suffix or operands invalid for
`bswap'
C:\WINDOWS\TEMP\ccuPj6El.s:2775: Error: suffix or operands invalid for
`bswap'
MAKE.EXE: *** [Hardware/Nmemory.o] Error 1
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
reply other threads:[~1998-11-01 0:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=363C1F7E.77CD7700@nievax.nie.ac.sg \
--to=leeckp@nievax.nie.ac.sg \
--cc=gnu-win32@cygnus.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).