Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@delorie.com>
To: pedwards@disaster.jaj.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH doc/refcard.tex
Date: Mon, 25 Dec 2000 01:12:00 -0000	[thread overview]
Message-ID: <200012250912.EAA22869@indy.delorie.com> (raw)
In-Reply-To: <20001224235038.A5058@disaster.jaj.com>

> Date: Sun, 24 Dec 2000 23:50:38 -0500
> From: Phil Edwards <pedwards@disaster.jaj.com>
> 
> While trying to recall some of the more esoteric GDB commands (using
> current CVS version to try to debug some C++, sigh), I tried to print
> the reference card.  While futzing with paper sizes, I noticed that the
> version and copyright information is old.  Fixed thusly.

Thanks.  However, I think the FSF doesn't want us to use year ranges
(as in "1998--2000"), so I used explicit years instead.

> (Incidentally, the doc/Makefile.in commands for refcard.dvi won't work.
> When REFEDITS is empty, the command sequence includes "for f in ; do some
> commands ; done" and every Bourne-family shell I tried pukes on the early
> ';'.  The irony is that this is in a branch which knows that REFEDITS is
> not empty, but is joined together with the lines executed when it is empty,
> into one long shell statement.)

This works for me with Bash.  Hmm.  Does it work if you replace
"$(REFEDITS)" with $$REFEDITS ?  (You might need to "export REFEDITS"
somewhere in the Makefile.)
From mir@sunchorus.France.Sun.COM Tue Dec 26 02:42:00 2000
From: Adam Mirowski <mir@sunchorus.France.Sun.COM>
To: "Eli Zaretskii" <eliz@is.elta.co.il>, <pedwards@disaster.jaj.com>
Cc: <gdb-patches@sources.redhat.com>
Subject: Re: PATCH doc/refcard.tex
Date: Tue, 26 Dec 2000 02:42:00 -0000
Message-id: <200012261042.LAA19117@sunchorus.France.Sun.COM>
X-SW-Source: 2000-12/msg00257.html
Content-length: 988

>> (Incidentally, the doc/Makefile.in commands for refcard.dvi won't work.
>> When REFEDITS is empty, the command sequence includes "for f in ; do some
>> commands ; done" and every Bourne-family shell I tried pukes on the early
>> ';'.  The irony is that this is in a branch which knows that REFEDITS is
>> not empty, but is joined together with the lines executed when it is empty,
>> into one long shell statement.)
>
>This works for me with Bash.  Hmm.  Does it work if you replace
>"$(REFEDITS)" with $$REFEDITS ?  (You might need to "export REFEDITS"
>somewhere in the Makefile.)

There are no quotes around the refedits variable, that
is the problem. Yes, it seems that bash does not need
them in a for/in/do/done construct after "in" when the
variable passed is empty, unlike the original Bourne shell.
Looks like almost everybody compiling gdb docs must be
using bash; I was quite suprized some time ago to see
that a simple "make ps" did not work in the docs directory.

-Adam


       reply	other threads:[~2000-12-25  1:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20001224235038.A5058@disaster.jaj.com>
2000-12-25  1:12 ` Eli Zaretskii [this message]
     [not found] <200012261042.LAA19117@sunchorus.France.Sun.COM>
2000-12-26  8:50 ` Eli Zaretskii
     [not found] ` <200012270825.DAA02213@indy.delorie.com>
2000-12-27  0:32   ` Phil Edwards

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=200012250912.EAA22869@indy.delorie.com \
    --to=eliz@delorie.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=pedwards@disaster.jaj.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