public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ming Cheng <chengm349@hotmail.com>
To: Paul Smith <paul@mad-scientist.net>,
	"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 03:12:10 +0000	[thread overview]
Message-ID: <SI2PR03MB524268483334072AC40FAA50FBB29@SI2PR03MB5242.apcprd03.prod.outlook.com> (raw)
In-Reply-To: <f6dabf110f3c10853d895ba944eba17bef3aabb3.camel@mad-scientist.net>

Hi Paul,

I downloaded the PDF and failed to find _target, _type.  I must miss you point. Please guide further.

Thanks.
Ming
________________________________
From: Paul Smith <paul@mad-scientist.net>
Sent: Tuesday, June 21, 2022 11:55 AM
To: Ming Cheng <chengm349@hotmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Fw: Makefile format

On Tue, 2022-06-21 at 10:42 +0100, Jonathan Wakely via Gcc-help wrote:
> > Thanks for your kind first step. I should have made my question
> > more clearer.
> >
> > We have a module called abc. Amazingly user can just define
> > abc_type, abc_target; and GNU make seems to me that  according to
> > its rules will implicitly look for these bars if defined. Does the
> > same doc have these rules description?
>
> Yes, the GNU Make manual is detailed and complete, see
> https://www.gnu.org/software/make/manual/html_node/Catalogue-of-
> Rules.html#Catalogue-of-Rules
> This is off-topic for the gcc-help list though.

Please use the help-make@gnu.org mailing list for assistance using GNU
make.

Cheers!

  reply	other threads:[~2022-06-22  3:12 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 [this message]
2022-06-22 14:06             ` Paul Smith

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=SI2PR03MB524268483334072AC40FAA50FBB29@SI2PR03MB5242.apcprd03.prod.outlook.com \
    --to=chengm349@hotmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=help-make@gnu.org \
    --cc=paul@mad-scientist.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).