From: Bill Shui <wshui@mail.usyd.edu.au>
To: help-gcc@gnu.org
Subject: compiling with gcc...
Date: Fri, 19 Nov 1999 04:39:00 -0000 [thread overview]
Message-ID: <38354666.FA186F6@mail.usyd.edu.au> (raw)
Hi there,
I recently upgrade my Debian (i386) kernel to 2.2.13
and I have also installed gcc-2.95.2
then when I tried to compile some program from source (programs such as
CVS, ssh-2, etc)
I get error messages shown as below:
(for CVS-1.9) I got messages as below:
gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O -c server.c
server.c: In function `do_cvs_command':
server.c:1834: Invalid `asm' statement:
server.c:1834: fixed or forbidden register 2 (cx) was spilled for class
CREG.
server.c: In function `server_pause_check':
server.c:2224: Invalid `asm' statement:
server.c:2224: fixed or forbidden register 2 (cx) was spilled for class
CREG.
make[1]: *** [server.o] Error 1
for ssh-2.0.13:
sshunixeloop.c: In function `ssh_event_loop_run':
sshunixeloop.c:710: Invalid `asm' statement:
sshunixeloop.c:710: fixed or forbidden register 2 (cx) was spilled for
class CREG.
sshunixeloop.c:711: Invalid `asm' statement:
sshunixeloop.c:711: fixed or forbidden register 2 (cx) was spilled for
class CREG.
both seemed to have problem dealing with FD_ZERO macro
and I just could not figure out why and how to fix it...
hoping someone out there could help me.
cheers.
Bill
--
Bill Shui | http://www-personal.usyd.edu.au/~wshui
------------------------------------------------------------------
WARNING: multiple messages have this Message-ID
From: Bill Shui <wshui@mail.usyd.edu.au>
To: help-gcc@gnu.org
Subject: compiling with gcc...
Date: Tue, 30 Nov 1999 23:28:00 -0000 [thread overview]
Message-ID: <38354666.FA186F6@mail.usyd.edu.au> (raw)
Message-ID: <19991130232800.v0XGTdUe9mVnkvbUFllyKysIYIGfQrj020aHZGvXn_Q@z> (raw)
Hi there,
I recently upgrade my Debian (i386) kernel to 2.2.13
and I have also installed gcc-2.95.2
then when I tried to compile some program from source (programs such as
CVS, ssh-2, etc)
I get error messages shown as below:
(for CVS-1.9) I got messages as below:
gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O -c server.c
server.c: In function `do_cvs_command':
server.c:1834: Invalid `asm' statement:
server.c:1834: fixed or forbidden register 2 (cx) was spilled for class
CREG.
server.c: In function `server_pause_check':
server.c:2224: Invalid `asm' statement:
server.c:2224: fixed or forbidden register 2 (cx) was spilled for class
CREG.
make[1]: *** [server.o] Error 1
for ssh-2.0.13:
sshunixeloop.c: In function `ssh_event_loop_run':
sshunixeloop.c:710: Invalid `asm' statement:
sshunixeloop.c:710: fixed or forbidden register 2 (cx) was spilled for
class CREG.
sshunixeloop.c:711: Invalid `asm' statement:
sshunixeloop.c:711: fixed or forbidden register 2 (cx) was spilled for
class CREG.
both seemed to have problem dealing with FD_ZERO macro
and I just could not figure out why and how to fix it...
hoping someone out there could help me.
cheers.
Bill
--
Bill Shui | http://www-personal.usyd.edu.au/~wshui
------------------------------------------------------------------
next reply other threads:[~1999-11-19 4:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-19 4:39 Bill Shui [this message]
1999-11-19 8:47 ` Martin Kahlert
1999-11-30 23:28 ` Martin Kahlert
1999-11-30 23:28 ` Bill Shui
1999-12-13 22:02 ` Terry
1999-12-13 22:02 ` Terry
1999-12-31 22:24 ` Terry
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=38354666.FA186F6@mail.usyd.edu.au \
--to=wshui@mail.usyd.edu.au \
--cc=help-gcc@gnu.org \
/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).