From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: Can't build emacs!
Date: Fri, 29 Oct 2004 13:54:38 +1000 [thread overview]
Message-ID: <87654u9o1t.fsf@enki.rimspace.net> (raw)
In-Reply-To: cls8il$itp$1@news.net.uni-c.dk
On 29 Oct 2004, JS wrote:
> I have just installed ubuntu Linux and extracted the latest emacs
> version: 21.3 on my AMD Barton 2500 XP machine.
>
> I get the following errormessage when I try to run
> "configure":
>
> johs@ubuntu:~/emacs-21.3 $ ./configure
> loading cache ./config.cache
> checking host system type... i686-pc-linux-gnu
> checking for gcc... no
> checking for cc... no
> configure: error: no acceptable cc found in $PATH
> johs@ubuntu:~/emacs-21.3 $
>
> What is the solution for this problem?
Install a C compiler. It should be named something intuitive like
'gcc.'
Regards,
Daniel
--
Trust the art, not the artist.
-- Bruce Springsteen
next prev parent reply other threads:[~2004-10-29 3:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 2:09 Can't build emacs! JS
2004-10-29 3:54 ` Daniel Pittman [this message]
[not found] ` <mailman.5896.1099023040.2017.help-gnu-emacs@gnu.org>
2004-10-29 9:35 ` JS
2004-10-29 11:00 ` Daniel Pittman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87654u9o1t.fsf@enki.rimspace.net \
--to=daniel@rimspace.net \
/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).