From: "Rupert Wood" <me@rupey.net>
To: "'Momchil Velikov'" <velco@fadata.bg>
Cc: <kabir.patel@uk.andersen.com>, <gcc-help@gcc.gnu.org>
Subject: RE: Problems with make
Date: Mon, 28 Jan 2002 04:28:00 -0000 [thread overview]
Message-ID: <616BE6A276E3714788D2AC35C40CD18D03AA08@whale.softwire.co.uk> (raw)
In-Reply-To: <616BE6A276E3714788D2AC35C40CD18D393F99@whale.softwire.co.uk>
Momchil Velikov wrote:
> >> When I run >>make makefile
:
> Rupert> You need to tell make what you'd like it to build. If you
> Rupert> don't specify anything then it assumes a target 'all' which
> Rupert> doesn't exist in your makefile.
>
> Actually it picks up the first target, no need for ``all''.
>
> The problem is that there's no dependency upon the Makefile itself.
Oops, yes, I stand corrected; answered from memory without checking
docs. I also hadn't noticed that he was running 'make makefile' instead
of plain 'make'.
Kabir, if you want to specify the makefile to use then you should type
'make -f <makefile name>'. It will automatically search a number of
filenames to use as the makefile including 'makefile' and 'Makefile' if
you don't specify -f.
Rup.
next parent reply other threads:[~2002-01-28 12:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <616BE6A276E3714788D2AC35C40CD18D393F99@whale.softwire.co.uk>
2002-01-28 4:28 ` Rupert Wood [this message]
[not found] <420931cd.73b89a7f.78a5.30baSMTPIN_ADDED@mx.gmail.com>
2005-02-09 9:11 ` problems " corey taylor
2005-02-09 1:46 Jupp Tscheak
-- strict thread matches above, loose matches on Subject: below --
2005-02-09 1:46 Jupp Tscheak
[not found] <616BE6A276E3714788D2AC35C40CD18D393F88@whale.softwire.co.uk>
2002-01-28 3:41 ` Problems " Rupert Wood
2002-01-28 4:16 ` Momchil Velikov
2002-01-28 3:31 kabir.patel
1999-12-23 5:27 problems " Adriano Holanda
1999-12-31 22:24 ` Adriano Holanda
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=616BE6A276E3714788D2AC35C40CD18D03AA08@whale.softwire.co.uk \
--to=me@rupey.net \
--cc=gcc-help@gcc.gnu.org \
--cc=kabir.patel@uk.andersen.com \
--cc=velco@fadata.bg \
/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).