From: n8tm@aol.comnojunk (Tim Prince)
To: help-gcc@gnu.org
Subject: Re: gcc and linux newbie's question
Date: Mon, 20 Dec 1999 05:58:00 -0000 [thread overview]
Message-ID: <19991220085554.10619.00000113@ng-ch1.aol.com> (raw)
In-Reply-To: <385DD787.2EA064EC@polyu.edu.hk>
>1) Is "source directory" the directory where I place the
> decompressed and unpackaged gcc bzip2 files?
Yes, e.g. <source directory>/gcc-2.95.2...
>set
> CC in your environment before running configure.
>2) Does it mean I should set those things before configuration?
yes, according to your shell, along the lines of
export CC=/usr/bin/gcc
or
setenv CC /bin/cc
so that $CC invokes the compiler you wish to use for initial bootstrap
Tim Prince
tprince@computer.org
WARNING: multiple messages have this Message-ID
From: n8tm@aol.comnojunk (Tim Prince)
To: help-gcc@gnu.org
Subject: Re: gcc and linux newbie's question
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <19991220085554.10619.00000113@ng-ch1.aol.com> (raw)
Message-ID: <19991231222400.1hJweNsAI3M9WrbYYxhxyUeeJ-IgZI2aqKrQttlH40w@z> (raw)
In-Reply-To: <385DD787.2EA064EC@polyu.edu.hk>
>1) Is "source directory" the directory where I place the
> decompressed and unpackaged gcc bzip2 files?
Yes, e.g. <source directory>/gcc-2.95.2...
>set
> CC in your environment before running configure.
>2) Does it mean I should set those things before configuration?
yes, according to your shell, along the lines of
export CC=/usr/bin/gcc
or
setenv CC /bin/cc
so that $CC invokes the compiler you wish to use for initial bootstrap
Tim Prince
tprince@computer.org
next prev parent reply other threads:[~1999-12-20 5:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-19 23:31 Hankel O'Fung
1999-12-20 5:58 ` Tim Prince [this message]
1999-12-21 19:48 ` root
1999-12-21 20:47 ` llewelly
1999-12-31 22:24 ` llewelly
1999-12-21 23:07 ` Tim Prince
1999-12-31 22:24 ` Tim Prince
1999-12-31 22:24 ` root
1999-12-31 22:24 ` Tim Prince
1999-12-31 22:24 ` Hankel O'Fung
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=19991220085554.10619.00000113@ng-ch1.aol.com \
--to=n8tm@aol.comnojunk \
--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).