public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Smith <paul@mad-scientist.net>
To: Ming Cheng <chengm349@hotmail.com>,
	"help-make@gnu.org" <help-make@gnu.org>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Fw: Makefile format
Date: Wed, 22 Jun 2022 10:06:11 -0400	[thread overview]
Message-ID: <80a018f898afb675f57ea6ae022e24ad5518131f.camel@mad-scientist.net> (raw)
In-Reply-To: <SI2PR03MB524268483334072AC40FAA50FBB29@SI2PR03MB5242.apcprd03.prod.outlook.com>

On Wed, 2022-06-22 at 03:12 +0000, Ming Cheng wrote:
> I downloaded the PDF and failed to find _target, _type.  I must miss
> you point. Please guide further.

What I'm saying is that the gcc-help mailing list is not the right
place to ask for help understanding makefiles or using GNU make.  gcc-
help is for help with the GCC compiler.  GNU make is a completely
separate project, so you shouldn't be sending those questions to the
GCC list.

Instead you should send your questions about understanding makefiles or
using GNU make only to the help-make@gnu.org mailing list, not the GCC
list.


As for your question, I didn't fully understand it so when you send
questions to the help-make@gnu.org mailing list, please include an
example of the part of the makefile that you don't understand, and/or
the make command you typed, and/or the output you received that was not
right, and explain why it wasn't what you expected and what you wanted
to happen instead.

Just to be clear, there is nothing built into GNU make that treats any
files ending with "_target" or "_type" in any special way at all, so
you won't find any reference to such a thing in the GNU make manual.

If something special is happening with those targets then something in
your makefiles is doing it.  We cannot guess what that might be, with
the information provided.

      reply	other threads:[~2022-06-22 14:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20  4:57 Ming Cheng
2022-06-20  6:45 ` Jonathan Wakely
     [not found]   ` <SI2PR03MB5242F39C786CA8C53496F745FBB39@SI2PR03MB5242.apcprd03.prod.outlook.com>
2022-06-21  8:49     ` Fw: " Ming Cheng
2022-06-21  9:42       ` Jonathan Wakely
2022-06-21 11:55         ` Paul Smith
2022-06-22  3:12           ` Ming Cheng
2022-06-22 14:06             ` Paul Smith [this message]

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=80a018f898afb675f57ea6ae022e24ad5518131f.camel@mad-scientist.net \
    --to=paul@mad-scientist.net \
    --cc=chengm349@hotmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=help-make@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).