From: Roman <r.dio@usa.net>
To: egcs@egcs.cygnus.com
Subject: m68000 VxWorks coprocessor protocol violation
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <003501be71a4$e77062b0$c6c4eccf@rdiouskine.motus.qc.ca> (raw)
Message-ID: <19990331234600.3Dg_0VIPsm-dbWeKnF3Rapi2MPmFRLwDxFnlgaBOpps@z> (raw)
Hi,
I've successfully configured / builded / installed egcs1.1.1 as a
i586-linux to m68k-vxworks cross.
The configure was run with --nfp -- The whole thing works well until I
attempt to link in libstdc++.a . Any code linked with stdc++ library
(with -msoft-float -m68000) generates a "Coprocessor protocol violation"
error if run on the target which, of course, doesn't have a coprocessor. In
the same time libgcc.a works well in soft-float variation.
libc.a, libg.a and libm.a are taken from original vxworks distribution.
ANY help will be appreciated (URGENT!).
Regargs,
Roman
r.dio@usa.net
next reply other threads:[~1999-03-31 23:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-18 17:13 Roman [this message]
[not found] ` < 003501be71a4$e77062b0$c6c4eccf@rdiouskine.motus.qc.ca >
1999-03-18 19:02 ` Jeffrey A Law
1999-03-31 23:46 ` Jeffrey A Law
1999-03-31 23:46 ` Roman
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='003501be71a4$e77062b0$c6c4eccf@rdiouskine.motus.qc.ca' \
--to=r.dio@usa.net \
--cc=egcs@egcs.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).