* Re: master a9b29ee4a0: Update from Gnulib by running admin/merge-gnulib
[not found] ` <20220928073725.36EB3C00615@vcs2.savannah.gnu.org>
@ 2022-09-28 11:05 ` Po Lu
2022-09-28 17:03 ` Paul Eggert
0 siblings, 1 reply; 6+ messages in thread
From: Po Lu @ 2022-09-28 11:05 UTC (permalink / raw)
To: emacs-devel; +Cc: Paul Eggert
Paul Eggert <eggert@cs.ucla.edu> writes:
> +assert.h: assert.in.h verify.h $(top_builddir)/config.status
> + $(gl_V_at){ $(SED_HEADER_STDOUT) \
^
Is this not a typo in gnulib?
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: master a9b29ee4a0: Update from Gnulib by running admin/merge-gnulib
2022-09-28 11:05 ` master a9b29ee4a0: Update from Gnulib by running admin/merge-gnulib Po Lu
@ 2022-09-28 17:03 ` Paul Eggert
2022-09-29 0:18 ` Po Lu
2022-09-29 1:38 ` Po Lu
0 siblings, 2 replies; 6+ messages in thread
From: Paul Eggert @ 2022-09-28 17:03 UTC (permalink / raw)
To: Po Lu; +Cc: emacs-devel
On 9/28/22 04:05, Po Lu wrote:
>> +assert.h: assert.in.h verify.h $(top_builddir)/config.status
>> + $(gl_V_at){ $(SED_HEADER_STDOUT) \
> ^
> Is this not a typo in gnulib?
>
Sorry, I'm not seeing a typo there. What should the text be instead?
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: master a9b29ee4a0: Update from Gnulib by running admin/merge-gnulib
2022-09-28 17:03 ` Paul Eggert
@ 2022-09-29 0:18 ` Po Lu
2022-09-29 1:22 ` Paul Eggert
2022-09-29 1:38 ` Po Lu
1 sibling, 1 reply; 6+ messages in thread
From: Po Lu @ 2022-09-29 0:18 UTC (permalink / raw)
To: Paul Eggert; +Cc: emacs-devel
Paul Eggert <eggert@cs.ucla.edu> writes:
> Sorry, I'm not seeing a typo there. What should the text be instead?
$(gl_V_at) $(SED_HEADER_STDOUT)
without the stray brace, which leads to "Command line too long" on
MS-DOS.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: master a9b29ee4a0: Update from Gnulib by running admin/merge-gnulib
2022-09-29 0:18 ` Po Lu
@ 2022-09-29 1:22 ` Paul Eggert
2022-09-29 1:41 ` Po Lu
0 siblings, 1 reply; 6+ messages in thread
From: Paul Eggert @ 2022-09-29 1:22 UTC (permalink / raw)
To: Po Lu; +Cc: emacs-devel
On 9/28/22 17:18, Po Lu wrote:
> Paul Eggert <eggert@cs.ucla.edu> writes:
>
>> Sorry, I'm not seeing a typo there. What should the text be instead?
>
> $(gl_V_at) $(SED_HEADER_STDOUT)
>
> without the stray brace, which leads to "Command line too long" on
> MS-DOS.
The brace isn't stray. There's a matching closing brace on line 1467 of
lib/gnulib.mk.in.
Perhaps the process of using sed to edit lib/gnulib.mk.in is somehow
corrupting the closing brace? It can't simply be the rule length, as
there are longer rules in lib/gnulib.mk.in (e.g., the dirent.h rule).
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: master a9b29ee4a0: Update from Gnulib by running admin/merge-gnulib
2022-09-28 17:03 ` Paul Eggert
2022-09-29 0:18 ` Po Lu
@ 2022-09-29 1:38 ` Po Lu
1 sibling, 0 replies; 6+ messages in thread
From: Po Lu @ 2022-09-29 1:38 UTC (permalink / raw)
To: Paul Eggert; +Cc: emacs-devel
Paul Eggert <eggert@cs.ucla.edu> writes:
> Sorry, I'm not seeing a typo there. What should the text be instead?
Nevermind, I was looking at broken output from the MS-DOS scripts.
Sorry for the noise.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2022-09-29 1:41 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <166435064249.6217.1318220121176926281@vcs2.savannah.gnu.org>
[not found] ` <20220928073725.36EB3C00615@vcs2.savannah.gnu.org>
2022-09-28 11:05 ` master a9b29ee4a0: Update from Gnulib by running admin/merge-gnulib Po Lu
2022-09-28 17:03 ` Paul Eggert
2022-09-29 0:18 ` Po Lu
2022-09-29 1:22 ` Paul Eggert
2022-09-29 1:41 ` Po Lu
2022-09-29 1:38 ` Po Lu
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).