public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Parikshat Dubey" <parikshatdubey@hotmail.com>
To: bug-make@gnu.org
Cc: jg@jguk.org, brian.budge@gmail.com, daniel.llorensdelrio@epfl.ch,
	pedz@easesoftware.com, vivek1717@gmail.com,
	pranjal.vir@gmail.com, gcc-help@gcc.gnu.org
Subject: Makefile Issue
Date: Fri, 26 May 2006 10:39:00 -0000	[thread overview]
Message-ID: <BAY13-F16A307B34ED31179499257CF9E0@phx.gbl> (raw)

Hi All!

I have one sample make file but there are many autogenerated things inside 
it which i am unable to comprehend and understand.I want to know how 
autogenerated makefile is generated and what are the specific things in 
makefile i need to  focus on.

I wan to know also how i can use autogenerated makefile in another makefile.

Thanks & Regards
Parikshat Dubey

_________________________________________________________________
Fall in Love... Get married! Join FREE! 
http://www.shaadi.com/ptnr.php?ptnr=msnhottag

             reply	other threads:[~2006-05-26 10:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-26 10:39 Parikshat Dubey [this message]
2006-05-26 10:51 ` Brian Dessent
  -- strict thread matches above, loose matches on Subject: below --
2006-07-20 16:31 MakeFile Issue Parikshat Dubey
2006-07-20 16:31 Parikshat Dubey
2006-07-20 16:30 Makefile Issue Parikshat Dubey
2006-07-03 16:34 Makefile issue Parikshat Dubey
2006-07-18 14:05 ` Dima Sorkin
2006-05-19  6:29 makefile issue Parikshat Dubey
2006-05-11 19:16 makefile error Daniel Llorens del Río
2006-05-13  8:14 ` Makefile Issue Parikshat Dubey
2006-05-13 11:47   ` Perry 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=BAY13-F16A307B34ED31179499257CF9E0@phx.gbl \
    --to=parikshatdubey@hotmail.com \
    --cc=brian.budge@gmail.com \
    --cc=bug-make@gnu.org \
    --cc=daniel.llorensdelrio@epfl.ch \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jg@jguk.org \
    --cc=pedz@easesoftware.com \
    --cc=pranjal.vir@gmail.com \
    --cc=vivek1717@gmail.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).