From: Robert Lipe <robertlipe@usa.net>
To: Steve day <steveday@3xor.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Gcc and SCO 5.0.6 OpenServer
Date: Sun, 22 Apr 2001 19:52:00 -0000 [thread overview]
Message-ID: <20010422215258.I5595@rjlhome.sco.com> (raw)
In-Reply-To: <027a01c0cac0$b297d380$3501a8c0@icl.com>
Steve day wrote:
> I am using a SCO OpenServer v5.0.6 .
> With Skunkware I have Gcc v2.95.2 19991024.
> I downloaded a MIME::BASE64 decoder and the compilation fell over with:-
> "cc: unrecognized option '-w0'".
[ ... ]
> I have searched my Gcc man file for "-w0" but to no avail.
Interesting. '-w0' is a valid flag to /bin/cc but not to gcc. Have
you done something like rename gcc to cc? If so, that might be defeating
autoconf-like scripts that case on the name of the compiler to figure
out what options to pass.
> If it is possible to donate any pointers my way it would help me join the
I hereby donate to thee 'char *p = NULL'. :-)
RJL
prev parent reply other threads:[~2001-04-22 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-21 17:14 Steve day
2001-04-22 19:52 ` Robert Lipe [this message]
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=20010422215258.I5595@rjlhome.sco.com \
--to=robertlipe@usa.net \
--cc=gcc@gcc.gnu.org \
--cc=steveday@3xor.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).