From: Jakub Narebski <jnareb@gmail.com>
To: Thomas Rast <trast@student.ethz.ch>
Cc: Daniel Pfeiffer <occitan@esperanto.org>, git@vger.kernel.org
Subject: Re: Compiling git with makepp patch
Date: Mon, 23 Aug 2010 02:00:04 -0700 (PDT) [thread overview]
Message-ID: <m3k4nhogbr.fsf@localhost.localdomain> (raw)
In-Reply-To: <201008230947.06777.trast@student.ethz.ch>
Thomas Rast <trast@student.ethz.ch> writes:
> Daniel Pfeiffer wrote:
> > [Attachment: git-makepp.patch]
>
> Please read Documentation/SubmittingPatches for next time.
>
> > There are however two things which I can hardly hope to fix:
> [...]
> > PERL_PATH_SQ = $(subst ','\'',$(PERL_PATH))#'
> >
> > [...] makepp parses this line just like Emacs, so it doesn't find
> > the comment, adding in the #' at the point of use, which completely
> > screws the sed command.
> [...]
> > # Shell quote;
> > -bindir_SQ = $(subst ','\'',$(bindir))#'
> > -gitwebdir_SQ = $(subst ','\'',$(gitwebdir))#'
> > -gitwebstaticdir_SQ = $(subst ','\'',$(gitwebdir)/static)#'
> > -SHELL_PATH_SQ = $(subst ','\'',$(SHELL_PATH))#'
> > -PERL_PATH_SQ = $(subst ','\'',$(PERL_PATH))#'
> > -DESTDIR_SQ = $(subst ','\'',$(DESTDIR))#'
> > +Q='
> > +# ' This comment is only to appease IDEs like Emacs.
> > +# The comment is on a new line, else makepp would see it as a quoted hash.
> > +bindir_SQ = $(subst $Q,'\'',$(bindir))
> > +gitwebdir_SQ = $(subst $Q,'\'',$(gitwebdir))
> > +gitwebstaticdir_SQ = $(subst $Q,'\'',$(gitwebdir)/static)
> > +SHELL_PATH_SQ = $(subst $Q,'\'',$(SHELL_PATH))
> > +PERL_PATH_SQ = $(subst $Q,'\'',$(PERL_PATH))
> > +DESTDIR_SQ = $(subst $Q,'\'',$(DESTDIR))
>
> Confusingly, you talk about comments above, but the real issue is that
> your makepp apparently gives the ' special meaning. For once "info
> make" and "man 1p make" on my system agree on the semantics of ': none
> at all. From the latter:
>
> Early proposals stated that an "unquoted" number sign was treated as the
> start of a comment. The make utility does not pay any attention to quotes. A
> number sign starts a comment regardless of its surroundings.
>
> So can you quote chapter and verse to show that there is anything to
> fix?
Nevertheless using
Q='
SQ='\''
bindir_SQ = $(subst $Q,$(SQ),$(bindir))
could make substitution more clear ('make' behavior nothwithstanding).
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-08-23 9:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <84FD9808A65CDF4C959FDB41FC3D134CBCF306D6@MSSRVS4.atlas.de>
2010-08-22 22:31 ` Compiling git with makepp patch Daniel Pfeiffer
2010-08-23 7:47 ` Thomas Rast
2010-08-23 9:00 ` Jakub Narebski [this message]
2010-08-25 21:08 ` Daniel Pfeiffer
2010-08-23 20:27 ` Ævar Arnfjörð Bjarmason
2010-08-25 20:58 ` Daniel Pfeiffer
2010-08-24 4:32 ` Jonathan Nieder
2010-08-25 20:41 ` Daniel Pfeiffer
2010-08-25 21:56 ` Andreas Schwab
2010-08-25 22:53 ` Junio C Hamano
2010-08-26 0:20 ` Jonathan Nieder
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=m3k4nhogbr.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=occitan@esperanto.org \
--cc=trast@student.ethz.ch \
/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 NNTP newsgroup(s).