From: Bruno Haible <bruno@clisp.org>
To: Bjarni Ingi Gislason <bjarniig@simnet.is>
Cc: bug-gnulib@gnu.org
Subject: Re: groff: error after update of gnulib, 13th January 2023
Date: Fri, 13 Jan 2023 22:56:24 +0100 [thread overview]
Message-ID: <12509392.IdSKlfLAKj@nimes> (raw)
In-Reply-To: <Y8GsYv2pg9mRTY/O@localhost>
Bjarni Ingi Gislason wrote:
> 2) with the commit, the config.log contains
>
> GL_GENERATE_ERROR_H_FALSE=''
> GL_GENERATE_ERROR_H_TRUE='#'
>
> and the Makefile contains
>
> lib/error.h: $(top_builddir)/config.status
> rm -f $@
That's because you happen to do this build on a platform which already
has /usr/include/error.h. On the other platforms error.h gets created in
the build directory, from error.in.h.
You cannot have a reliable build system if the same include file basename
(here: "error.h") is used to denote two different .h files, one that
declares error_at_line, and one which declares groff C++ classes. This
will *never* be reliable, regardless how to attempt to arrange the -I
options in the AM_CPPFLAGS.
Bruno
next prev parent reply other threads:[~2023-01-13 21:56 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
2023-01-13 21:56 ` Bruno Haible [this message]
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=12509392.IdSKlfLAKj@nimes \
--to=bruno@clisp.org \
--cc=bjarniig@simnet.is \
--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).