public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Ben Michie" <booplets@bigfoot.com>
To: gcc-help@gcc.gnu.org
Subject: c_compiler
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <200002061735490360.00183CD8@fox.uq.net.au> (raw)
Message-ID: <20000401000000.Ujm1i4z0csvJJ-I_uXWEFYn1GM8yj0l0BMuuXmHSi0c@z> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 321 bytes --]

Hi gcc ppls,
 
I was attempting to install the latest gcc package 
from suse (v6.3) and I came across a peculiar error, it was something along the 
lines of "can't find c_compiler" or "gcc needs c_compiler". Does any1 know what 
this means or have any suggestions that I could try doing.
 
Many thanks, Ben Michie


             reply	other threads:[~2000-04-01  0:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-05 23:39 Ben Michie [this message]
2000-04-01  0:00 ` c_compiler Ben Michie
2000-07-13 15:52 c compiler Edward Lartey
     [not found] <200208012209.AAA06454@mailin.webmailer.de>
2002-08-01 16:00 ` c++ compiler Simon Brügmann
2002-08-01 18:00   ` Oscar Fuentes
2002-08-01 20:50 Dockeen
2005-07-25 17:44 Niels Jende
2005-07-25 17:46 ` corey taylor
2007-01-13 19:32 C compiler Berg, Michelle D.
2007-01-15 10:06 ` Hugh Sasse
2011-03-13 14:43 Rohit Rehan
2011-03-13 14:47 ` Jonathan Wakely
2013-04-30  2:31 C++ Compiler Scarlbc
2013-04-30  9:06 ` Jonathan Wakely
2014-10-19 14:28 C compiler BASAVARAJ L KAGE
2014-10-20 12:42 ` Jonathan Wakely
     [not found] <815189974.291369.1523654409630.ref@mail.yahoo.com>
2018-04-13 21:20 ` C++ Compiler Roy Ware via gcc-help
2018-04-13 21:35   ` Martin Sebor
2018-04-13 21:35   ` Andrew Bell
2018-04-13 21:35   ` Marc Glisse
2018-04-13 21:45     ` Roy Ware via gcc-help

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=200002061735490360.00183CD8@fox.uq.net.au \
    --to=booplets@bigfoot.com \
    --cc=gcc-help@gcc.gnu.org \
    /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).