From: Andrea 'Fyre Wyzard' Bocci <fwyzard@inwind.it>
To: Yahya Darboe <darboey@yahoo.com>,gcc@gnu.org
Subject: Re: qcc configuration
Date: Sat, 24 Nov 2001 06:33:00 -0000 [thread overview]
Message-ID: <5.1.0.14.0.20011201014011.00a44760@popmail.inwind.it> (raw)
In-Reply-To: <20011201001831.33574.qmail@web13904.mail.yahoo.com>
At 16.18 30/11/01 (GMT -0800), Yahya Darboe wrote:
>"Second, when configuring a native system, either cc or gcc
>must be in your path or you must set CC in your environment
>before running configure. Otherwise the configuration
>scripts may fail."
>
>Above, you mentioned that one must either have gcc in their
>path or set cc in their environment, but you did not
>specify how this can be accomplished.
>
>I have doing many things but none of them help.
>Could you please, please, help to provide me with detailed
>instructions of how to have these environment set properly
>so I can get Gcc compiled.
I assume you're using some kind of Unix, or Cygnus if running under Windows.
If this is not true, this probably won't help you :-(
You can see what yo path is with
echo $PATH
You can check that you have gcc in your path just trying to run it.
If you get something like "gcc: No input files" you have it in your path
If you get something like "gcc: command not found" you DON'T have it in the
path.
In the latter case, you can add it to your path with
(if running sh / bash)
PATH=$PATH:"directory where gcc is"
export PATH
(if running csh / tcsh)
setenv PATH $PATH:"directory where gcc is"
OR, you can set CC:
(if running sh / bash)
CC="directory where gcc is"/gcc
export CC
(if running csh / tcsh)
setenv CC "directory where gcc is"/gcc
If you use cc instead of cc, just use the above instructions substituing
"cc" for "gcc" where needed.
HTH
fwyzard
WARNING: multiple messages have this Message-ID
From: Andrea 'Fyre Wyzard' Bocci <fwyzard@inwind.it>
To: Yahya Darboe <darboey@yahoo.com>, gcc@gnu.org
Subject: Re: qcc configuration
Date: Fri, 30 Nov 2001 16:51:00 -0000 [thread overview]
Message-ID: <5.1.0.14.0.20011201014011.00a44760@popmail.inwind.it> (raw)
Message-ID: <20011130165100.XUpLsaqKJNBEhnZCoks5eHnjmUn_h4-3AkulvxKMxgw@z> (raw)
In-Reply-To: <20011201001831.33574.qmail@web13904.mail.yahoo.com>
At 16.18 30/11/01 (GMT -0800), Yahya Darboe wrote:
>"Second, when configuring a native system, either cc or gcc
>must be in your path or you must set CC in your environment
>before running configure. Otherwise the configuration
>scripts may fail."
>
>Above, you mentioned that one must either have gcc in their
>path or set cc in their environment, but you did not
>specify how this can be accomplished.
>
>I have doing many things but none of them help.
>Could you please, please, help to provide me with detailed
>instructions of how to have these environment set properly
>so I can get Gcc compiled.
I assume you're using some kind of Unix, or Cygnus if running under Windows.
If this is not true, this probably won't help you :-(
You can see what yo path is with
echo $PATH
You can check that you have gcc in your path just trying to run it.
If you get something like "gcc: No input files" you have it in your path
If you get something like "gcc: command not found" you DON'T have it in the
path.
In the latter case, you can add it to your path with
(if running sh / bash)
PATH=$PATH:"directory where gcc is"
export PATH
(if running csh / tcsh)
setenv PATH $PATH:"directory where gcc is"
OR, you can set CC:
(if running sh / bash)
CC="directory where gcc is"/gcc
export CC
(if running csh / tcsh)
setenv CC "directory where gcc is"/gcc
If you use cc instead of cc, just use the above instructions substituing
"cc" for "gcc" where needed.
HTH
fwyzard
next prev parent reply other threads:[~2001-12-01 0:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-24 4:45 Yahya Darboe
2001-11-24 6:15 ` Per Bothner
2001-11-30 16:29 ` Per Bothner
2001-11-24 6:33 ` Andrea 'Fyre Wyzard' Bocci [this message]
2001-11-30 16:51 ` Andrea 'Fyre Wyzard' Bocci
2001-11-30 16:19 ` Yahya Darboe
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=5.1.0.14.0.20011201014011.00a44760@popmail.inwind.it \
--to=fwyzard@inwind.it \
--cc=darboey@yahoo.com \
--cc=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).