From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: "Dickson, Ross" <ross.dickson@intel.com>
Cc: egcs@cygnus.com
Subject: Re: egcs/gcc and solaris x86 V2.6
Date: Wed, 15 Jul 1998 04:15:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.00.9807151313240.16276-100000@markab.dbai.tuwien.ac.at> (raw)
In-Reply-To: <B38DE02578EBD111AC4200A0C95D19EE341A0D@orsmsx30.jf.intel.com>
On Tue, 14 Jul 1998, Dickson, Ross wrote:
> When I attempted to compile gcc 2.8.1 from ftp.gnu.org configure said
> "no acceptable cc found in $PATH", the workshop compiler was in the
> path as /usr/ucb/cc.
Hmm, just an idea: What happens if you do `setenv CC /usr/ucb/cc` or
similar before running ./configure?
Gerald
--
Gerald Pfeifer (Jerry) Vienna University of Technology
pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next prev parent reply other threads:[~1998-07-15 4:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-14 16:57 Dickson, Ross
1998-07-15 4:15 ` Gerald Pfeifer [this message]
1998-07-15 6:45 ` Gerald Pfeifer
1998-07-15 11:36 ` Jeffrey A Law
1998-07-16 0:32 ` Jeffrey A Law
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=Pine.GSO.4.00.9807151313240.16276-100000@markab.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=egcs@cygnus.com \
--cc=ross.dickson@intel.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).