From: Alexandre Oliva <aoliva@redhat.com>
To: Nathanael Nerode <neroden@doctormoo.dyndns.org>
Cc: mike stump <mrs@windriver.com>, gcc@gcc.gnu.org
Subject: Re: autoconfiscation -- questions about make usage
Date: Wed, 30 Jan 2002 16:36:00 -0000 [thread overview]
Message-ID: <orwuxz33mj.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: Nathanael Nerode's message of "Wed, 30 Jan 2002 14:06:19 -0500 (EST)"
On Jan 30, 2002, Nathanael Nerode <neroden@doctormoo.dyndns.org> wrote:
> (They use dashes and .PHONY.)
dashes in macro names are not SUS, but dashes in filenames are,
AFAIK. If we're really using dashes in macro names, these should
probably be fixed.
As for .PHONY, for make programs that don't understand it, it looks
like a harmless dependency of file .PHONY on other files, so it is
simply ignored.
> This means I am probably going to be writing a small program to
> automatically generate Makefile.in, because there will be huge
> lists of almost identical targets (which could be collapsed with pattern
> rules, but not suffix rules).
Care to explain in advance what kind of targets you're thinking of
generating? Perhaps we could help save you some work, should someone
think of a way to do it without needing such a program.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2002-01-30 21:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200201301855.KAA04578@kankakee.wrs.com>
2002-01-30 12:36 ` Nathanael Nerode
2002-01-30 12:41 ` Zack Weinberg
2002-01-30 16:36 ` Alexandre Oliva [this message]
2002-04-01 14:02 ` Nathanael Nerode
2002-01-30 0:36 Nathanael Nerode
2002-01-30 4:22 ` Joe Buck
2002-01-30 5:29 ` Nathanael Nerode
2002-01-30 6:16 ` Phil Edwards
2002-01-30 11:23 ` Daniel Jacobowitz
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=orwuxz33mj.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=mrs@windriver.com \
--cc=neroden@doctormoo.dyndns.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).