From: Jim Frost <jim@jimfrost.com>
To: gcc-help@gcc.gnu.org
Subject: help!!!
Date: Mon, 03 Mar 2003 17:37:00 -0000 [thread overview]
Message-ID: <200303031737.48617.jim@jimfrost.com> (raw)
Any ideas with the following??? gcc3.2
linux:~/aquaosk-2.0 # ./configure
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking for -p flag to install... yes
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output... configure: error: C compiler cannot
create executables
See `config.log' for more details.
Help appreciated!!!
Thanks,
Jim Frost
--
KMail 1.5 KDE 3.1
next reply other threads:[~2003-03-03 17:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 17:37 Jim Frost [this message]
2003-03-07 5:46 ` help!!! LLeweLLyn Reese
-- strict thread matches above, loose matches on Subject: below --
2018-06-01 15:58 Help!! Tomas Ukkonen
2006-12-26 13:38 help!! manish manish
2006-12-27 17:01 ` help!! Ian Lance Taylor
2006-01-28 5:42 Help? Garvin Pang
2006-01-28 7:41 ` Help? Brian Dessent
2005-06-02 15:54 help_ imacat
2003-07-12 10:05 help? Shen Hui
[not found] <20021204042724.64819.qmail@web15002.mail.bjs.yahoo.com>
2002-12-04 0:16 ` help! Ben Elliston
2002-11-19 10:16 help!!! mingo lu
[not found] <20020617195757.13842.qmail@uwdvg001.cms.usa.net>
2002-06-17 13:05 ` help!! Phil Edwards
2002-04-04 23:41 Help! 朱 少波
2001-01-02 18:27 Help? Kwanghoon Choi
2001-01-02 19:37 ` Help? Alexandre Oliva
2000-05-15 9:15 HELP!!! Michael Michael
2000-05-16 23:27 ` HELP!!! Martin v. Loewis
2000-03-08 14:14 HELP !!! FabrÃcio Souza
2000-03-09 17:00 ` Alexandre Oliva
2000-04-01 0:00 ` Alexandre Oliva
2000-04-01 0:00 ` FabrÃcio Souza
2000-02-24 0:56 Help! 陳鵬升
2000-04-01 0:00 ` 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=200303031737.48617.jim@jimfrost.com \
--to=jim@jimfrost.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).