From: Shakthi Kannan <shakthimaan@gmail.com>
To: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: building emacs
Date: Thu, 1 Jun 2017 12:49:28 +0530 [thread overview]
Message-ID: <CABG-yt3uY=r_CKvLgihdJZyMBr7Fn+p15AZLUmroG=HAmJWFJg@mail.gmail.com> (raw)
In-Reply-To: <yw.86d1apb537.fsf@zoho.com>
Hi,
--- Jean-Christophe Helary wrote:
| You understood right. I'm the one who did not
| understand what make was doing.
\--
I had made a simple presentation on GNU Make that you might find useful:
http://shakthimaan.com/downloads.html#dum-ka-biryani-make-for-each-other
SK
--
Shakthi Kannan
http://www.shakthimaan.com
next prev parent reply other threads:[~2017-06-01 7:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 10:52 building emacs Jean-Christophe Helary
2017-05-31 11:19 ` Tim Visher
2017-05-31 11:24 ` Jean-Christophe Helary
2017-05-31 11:26 ` Eli Zaretskii
2017-05-31 11:41 ` Jean-Christophe Helary
2017-05-31 12:09 ` Emanuel Berg
2017-05-31 13:22 ` Skip Montanaro
2017-05-31 14:00 ` Emanuel Berg
2017-06-01 7:19 ` Shakthi Kannan [this message]
2017-06-01 13:36 ` Jean-Christophe Helary
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABG-yt3uY=r_CKvLgihdJZyMBr7Fn+p15AZLUmroG=HAmJWFJg@mail.gmail.com' \
--to=shakthimaan@gmail.com \
--cc=help-gnu-emacs@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).