public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: RedSonja <Sally.Riedhammer@cassidian.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc will not read its own makefile
Date: Tue, 31 May 2011 13:51:00 -0000	[thread overview]
Message-ID: <mcrpqmzrofq.fsf@coign.corp.google.com> (raw)
In-Reply-To: <31740482.post@talk.nabble.com> (RedSonja's message of "Tue, 31	May 2011 05:44:00 -0700 (PDT)")

RedSonja <Sally.Riedhammer@cassidian.com> writes:

> Jonathan Wakely-4 wrote:
>> 
>> On 31 May 2011 13:21, RedSonja wrote:
>>>
>>> Hello. I am porting a big C++ project from Windows to Solaris 9 with
>>> Eclipse
>>> and gnu. It can make its own makefile but then it says:
>>>
>>> gcc -f /export/home/MyPath/Debug/makefile -v
>> 
>> Maybe you meant "make -f ..." ?
>> 
>> GCC is a compiler, it doesn't read makefiles
>> 
>> 
>
>
> it says:
>
> (Exec error:Cannot run make)
>
> Why would it say that? I typed make at first. Do I have to install it
> separately?

The "make" program is not part of gcc.  You do have to have the make
program installed in order to build gcc or to use a Makefile.  If you
don't have a make program, you should install it.  I'm sure that Solaris
provides a make program, though perhaps it is not installed by default.
It may be installed in /usr/ccs/bin/make on Solaris, so check that
/usr/ccs/bin is on your PATH.

Ian

  reply	other threads:[~2011-05-31 13:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 13:27 RedSonja
2011-05-31 13:28 ` Jonathan Wakely
2011-05-31 13:35   ` RedSonja
2011-05-31 13:51     ` Ian Lance Taylor [this message]
2011-05-31 14:37       ` Jonathan Wakely
2011-05-31 15:17       ` RedSonja
2011-05-31 22:28         ` Jonathan Wakely
     [not found]           ` <4DE56E62.2080101@aol.com>
2011-06-01  9:22             ` Kai Ruottu

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=mcrpqmzrofq.fsf@coign.corp.google.com \
    --to=iant@google.com \
    --cc=Sally.Riedhammer@cassidian.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).