bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bjarni Ingi Gislason <bjarniig@simnet.is>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: groff: error after update of gnulib, 13th January 2023
Date: Fri, 13 Jan 2023 19:09:22 +0000	[thread overview]
Message-ID: <Y8GsYv2pg9mRTY/O@localhost> (raw)
In-Reply-To: <10435880.85pcf5A44T@nimes>

  Thanks for some insights.

  I reverted the commit to get the compilation error-free.

  Some observations with the commit added

1)  /lib/error.h is not compiled from /lib/error.in.h
   It is there when the commit is abset.

2) with the commit, the config.log contains

GL_GENERATE_ERROR_H_FALSE=''
GL_GENERATE_ERROR_H_TRUE='#'

  and the Makefile contains

# We need the following in order to create <error.h> when the system
# doesn't have one that works.
#lib/error.h: lib/error.in.h $(top_builddir)/config.status $(CXXDEFS_H)
#       $(AM_V_GEN)$(MKDIR_P) 'lib'
#       $(gl_V_at)$(SED_HEADER_STDOUT) \
#             -e 's|@''HAVE_ERROR''@|$(HAVE_ERROR)|g' \
#             -e 's|@''HAVE_ERROR_AT_LINE''@|$(HAVE_ERROR_AT_LINE)|g' \
#             -e 's|@''REPLACE_ERROR''@|$(REPLACE_ERROR)|g' \
#             -e 's|@''REPLACE_ERROR_AT_LINE''@|$(REPLACE_ERROR_AT_LINE)|g' \
#             -e '/definitions of _GL_FUNCDECL_RPL/r $(CXXDEFS_H)' \
#             $(top_srcdir)/lib/error.in.h > $@-t
#       $(AM_V_at)mv $@-t $@
lib/error.h: $(top_builddir)/config.status
        rm -f $@



  reply	other threads:[~2023-01-13 19:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13  1:43 groff: error after update of gnulib, 13th January 2023 Bjarni Ingi Gislason
2023-01-13  2:25 ` Bruno Haible
2023-01-13 19:09   ` Bjarni Ingi Gislason [this message]
2023-01-13 21:56     ` Bruno Haible
2023-01-13 23:33       ` Bjarni Ingi Gislason

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://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y8GsYv2pg9mRTY/O@localhost \
    --to=bjarniig@simnet.is \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@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).