From: "Valle, Adam" <Adam.Valle@exchange.webmd.net>
To: 'Robert Lipe' <robertlipe@usa.net>
Cc: "'gcc@gnu.org'" <gcc@gnu.org>
Subject: RE: SCO OpenServer Build status for GCC 2.95
Date: Mon, 07 Oct 2002 14:05:00 -0000 [thread overview]
Message-ID: <F2FC2BCB5CCDD511B4D200508BCA281F017CF7FB@bnawlex001.corp.envoy.com> (raw)
Have you heard of any issues (good or bad) with any gcc versions on SCO
OpenServer 5.0.2 SCO OpenServer 5.0.3, or UnixWare?
Thanks,
Adam
-----Original Message-----
From: Robert Lipe [mailto:robertlipe@usa.net]
Sent: Thursday, July 25, 2002 3:18 PM
To: Valle, Adam
Cc: 'gcc@gnu.org'
Subject: Re: SCO OpenServer Build status for GCC 2.95
Valle, Adam wrote:
> On http://gcc.gnu.org/gcc-2.95/buildstat.html , there are two listings for
> OpenServer 5.0.5 :
> i386-pc-sco3.2v5.0.5
> Successful
> i586-pc-sco3.2v5.0.5
> Successful
>
> Was one of these intended for OpenServer 5.0.4?
I would assume no typos. 5.0.4 is a pretty tenured release these days.
The above results are telling you that it succeeded targeting either
processor.
GCC tickles a couple of bugs in the assembler and linker on the OS of
that vintage. There was a TLS (TLS706, I think) that fixed a number of
these problems.
> Has there been a successfull release of gcc 2.95 on this platform?
I recall the source release pretty much Just Working. There were binary
kits put up on www.caldera.com/skunkware.
Signed,
Your Fellow Nashvillian
next reply other threads:[~2002-10-07 19:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 14:05 Valle, Adam [this message]
2002-10-07 14:30 ` Robert Lipe
2002-10-07 15:05 ` Robert Lipe
-- strict thread matches above, loose matches on Subject: below --
2002-10-07 17:25 Valle, Adam
2002-07-26 23:56 Valle, Adam
2002-07-25 14:24 Valle, Adam
2002-07-25 16:03 ` Robert Lipe
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=F2FC2BCB5CCDD511B4D200508BCA281F017CF7FB@bnawlex001.corp.envoy.com \
--to=adam.valle@exchange.webmd.net \
--cc=gcc@gnu.org \
--cc=robertlipe@usa.net \
/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).