From: "Rin V." <narinw@email.com>
To: "Puneet Singhal" <puneet@opussoft.com>, gcc-help@gcc.gnu.org
Subject: RE: Problem configuring gcc
Date: Wed, 21 Mar 2001 01:39:00 -0000 [thread overview]
Message-ID: <383333881.985167570488.JavaMail.root@web613-ec> (raw)
Thank you your your fast response. I have had precompiled GCC located on
/usr/local/bin/gcc directory.
Regards,
Narin
------Original Message------
From: "Puneet Singhal" <puneet@opussoft.com>
To: Rin V. <narinw@email.com>, gcc-help@gcc.gnu.org
Sent: March 21, 2001 9:22:27 AM GMT
Subject: RE: Problem configuring gcc
>*** The command 'gcc -o conftest -Wall -fPIC conftest.c' failed.
>*** You must set the environment variable CC to a working complier.
You must have a valid C compiler on ur OS to compile GCC.
get a precompiled GCC from www.sunfreeware.com and then if you need then
recompile GCC with your own params.
cheers,
Puneet
*********************************************
The Boulder Pledge: "Under no circumstances will I ever purchase anything
offered to me as the result of an unsolicited email message. Nor will I
forward chain letters, petitions, mass mailings, or virus warnings to large
numbers of others. This is my contribution to the survival of the online
community."
*********************************************
Those who do not understand Unix are condemned to reinvent it, poorly.
-- Henry Spencer
Unix is user-friendly (it only choose its friends carefully)
----------------------------------------------------------------------------
----
-----------------------------------------------
FREE! The World's Best Email Address @email.com
Reserve your name now at http://www.email.com
next reply other threads:[~2001-03-21 1:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 1:39 Rin V. [this message]
2001-03-21 14:34 ` Alexandre Oliva
-- strict thread matches above, loose matches on Subject: below --
2001-03-21 1:07 Rin V.
2001-03-21 1:20 ` Puneet Singhal
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=383333881.985167570488.JavaMail.root@web613-ec \
--to=narinw@email.com \
--cc=gcc-help@gcc.gnu.org \
--cc=puneet@opussoft.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).