From: Robert Lipe <robertl@dgii.com>
To: Ruslan@Shevchenko.kiev.ua
Cc: egcs@cygnus.com
Subject: SCO OS bug.
Date: Mon, 19 Jan 1998 02:25:00 -0000 [thread overview]
Message-ID: <19980119001053.41968@dgii.com> (raw)
> 1. Initial : SCO Open Server 5.0 with Skunware (i.e. gcc 2.7.2.1)
> developmmet system.
OpenServer version numbers have three digits. They are all important.
The six different Skunkwares to date (they have version numbers, too)
have each had some kind of GCC-like substances on them.
> Install fails during misconfigurations in Makefile
> i.e. on some stange of bootstrapping receive next configure message:
>
> Is system have working c compiler .... no
> 2. After few "make, clean" by hand it's installels.
That's quite alarming. This should be analyzed and solved before
you continue.
> 3. During compiling omniBroker (www.ooc.org), with -mcoff receive
> message
> from native SCO assembler:
> SymbolicTable full
strings /usr/bin/as /usr/ccs/bin/elf/as /usr/ccs/bin/coff/as | grep Symbolic
on my 5.0.4 system returns nothing.
In fact, I can't find that string in ld, in gcc, or in anything else.
You're going to have to figure out what program that message is coming
from. I don't think it's the SCO native assembler. Regardless, COFF
has substantial limitations on things like sizes of symbolic debugging
tables that you may be running into. We encourage the use of ELF - this
is why we made it the default.
> 4. omniBroker programms work incorrect.
Until the rest of this wierdness is worked out, I wouldn't bother
trying to actually execute anything.
-
Robert Lipe http://www.dgii.com/people/robertl robertl@dgii.com
reply other threads:[~1998-01-19 2:25 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=19980119001053.41968@dgii.com \
--to=robertl@dgii.com \
--cc=Ruslan@Shevchenko.kiev.ua \
--cc=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).