public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Mike Reilly" <mike_reilly.nospamplease@bc.sympatico.ca>
To: help-gcc@gnu.org
Subject: Re: How to set CC enviroment?
Date: Wed, 05 Jan 2000 22:27:00 -0000	[thread overview]
Message-ID: <VxWc4.117$LD1.388307@news.bctel.net> (raw)
In-Reply-To: <84u6gd$shk$1@news4.jaring.my>

You can check if your CC environment variable is set by typing 'set' at the
command prompt.  To create a CC variable if one doesn't exist, type
'CC="/usr/sbin/gcc" or whatever the path is to gcc (sorry I'm on an NT box
right now, don't have a decent news reader for Linux yet - anyone have any
suggestions for a powerful yet easy to use one?).

You can then check if your CC variable is set by typing 'set' once again.
If typing 'set' returns too many for one screen, redirect output to a file.
set >> vars.txt
for example.

However, it may be that you don't currently have things set up correctly on
your machine.  On mine (mandrake 6.0), I didn't have any development
libraries installed, and couldn't get anything going correctly until I did
(doh! there goes a couple of days figuring that out).

If you have a lot of problems, deja news will be your best resource, as well
as the gcc docs.  Good luck.

Mike
Danny Goh wrote in message < 84u6gd$shk$1@news4.jaring.my >...
>As I run the ./configure, the machine show this problem..
>
>Configuring for a sparc-sun-solaris2.7 host.
>Created "Makefile" in /opt/srcdir using "mh-frag"
>./configure: cc: not found
>*** The command 'ccc -o conftest -g   conftest.c' failed.
>*** You must set the environment variable CC to a working compiler.
>
>Thanks in advance
>
>


WARNING: multiple messages have this Message-ID
From: "Mike Reilly" <mike_reilly.nospamplease@bc.sympatico.ca>
To: help-gcc@gnu.org
Subject: Re: How to set CC enviroment?
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <VxWc4.117$LD1.388307@news.bctel.net> (raw)
Message-ID: <20000401000000.5wO8zI-P3PvouLlXxkA8EouFjdX1J_TUxIkbfZjAQAs@z> (raw)
In-Reply-To: <84u6gd$shk$1@news4.jaring.my>

You can check if your CC environment variable is set by typing 'set' at the
command prompt.  To create a CC variable if one doesn't exist, type
'CC="/usr/sbin/gcc" or whatever the path is to gcc (sorry I'm on an NT box
right now, don't have a decent news reader for Linux yet - anyone have any
suggestions for a powerful yet easy to use one?).

You can then check if your CC variable is set by typing 'set' once again.
If typing 'set' returns too many for one screen, redirect output to a file.
set >> vars.txt
for example.

However, it may be that you don't currently have things set up correctly on
your machine.  On mine (mandrake 6.0), I didn't have any development
libraries installed, and couldn't get anything going correctly until I did
(doh! there goes a couple of days figuring that out).

If you have a lot of problems, deja news will be your best resource, as well
as the gcc docs.  Good luck.

Mike
Danny Goh wrote in message < 84u6gd$shk$1@news4.jaring.my >...
>As I run the ./configure, the machine show this problem..
>
>Configuring for a sparc-sun-solaris2.7 host.
>Created "Makefile" in /opt/srcdir using "mh-frag"
>./configure: cc: not found
>*** The command 'ccc -o conftest -g   conftest.c' failed.
>*** You must set the environment variable CC to a working compiler.
>
>Thanks in advance
>
>


  parent reply	other threads:[~2000-01-05 22:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-04 17:30 Danny Goh
2000-01-04 17:45 ` Saran
2000-04-01  0:00   ` Saran
2000-01-05 22:27 ` Mike Reilly [this message]
2000-01-06 10:05   ` James Moody
2000-04-01  0:00     ` James Moody
2000-04-01  0:00   ` Mike Reilly
2000-01-06 18:45 ` Craig Simpson
2000-04-01  0:00   ` Craig Simpson
2000-04-01  0:00 ` Danny Goh

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='VxWc4.117$LD1.388307@news.bctel.net' \
    --to=mike_reilly.nospamplease@bc.sympatico.ca \
    --cc=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).