public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: John Love-Jensen <eljay@adobe.com>
To: Joseph Maxwell <jaymax@jaymax.com>, MSX to GCC <gcc-help@gcc.gnu.org>
Subject: Re: Installation Problem
Date: Mon, 26 Nov 2007 21:06:00 -0000	[thread overview]
Message-ID: <C3708472.271F1%eljay@adobe.com> (raw)
In-Reply-To: <474B2436.70704@jaymax.com>

Hi Joseph,

> Could you advise?

Odd.  You have GCC 3.3 and GCC 3.4.6 installed.  Which one is referred to by
the 'gcc' command line command?  Does it work?  Can you create a runnable
executable with it?

GCC installation instructions:
http://gcc.gnu.org/install/

Also, did you run ./configure, or did you follow the GCC configure
instructions <http://gcc.gnu.org/install/configure.html> and build in a
different directory than than the GCC source code?

Building GCC in the source directory, or any subdirectory thereof, is not
supported.  You didn't supply that information, and it is one of the things
that trips people up sometimes, so I thought I'd ask.

This is a gcc-help@gcc.gnu.org question, not a gcc@gcc.gnu.org question.
I've removed gcc@gcc.gnu.org from the response list.

HTH,
--Eljay

  reply	other threads:[~2007-11-26 20:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-26 20:11 Joseph Maxwell
2007-11-26 21:06 ` John Love-Jensen [this message]
2007-11-27  2:50 ` Tim Prince
2007-11-27 20:47   ` Joseph Maxwell
2007-11-27 20:53     ` Kevin P. Fleming
2007-11-27 21:11     ` Sven Eschenberg
2007-11-28  2:09     ` Tom Browder
2007-11-28 16:30       ` Joseph Maxwell
2007-11-28 19:09         ` Tom Browder
  -- strict thread matches above, loose matches on Subject: below --
2003-03-03 21:04 Installation problem Marc-André Breton
2003-03-07  5:41 ` LLeweLLyn Reese
2001-05-20 13:19 Brad O'Hearne
2001-05-20 14:14 ` Alexandre Oliva
2000-12-11 23:53 Installation Problem Sharma Dipesh
2000-12-12  7:42 ` Alexandre Oliva

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=C3708472.271F1%eljay@adobe.com \
    --to=eljay@adobe.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jaymax@jaymax.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).