From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Bjarni Ingi Gislason <bjarniig@simnet.is>
Subject: Re: groff: error after update of gnulib, 13th January 2023
Date: Fri, 13 Jan 2023 03:25:30 +0100 [thread overview]
Message-ID: <10435880.85pcf5A44T@nimes> (raw)
In-Reply-To: <Y8C3U97oDVvw4laR@localhost>
Bjarni Ingi Gislason wrote:
> ../lib/openat-die.c:37:3: warning: implicit declaration of function 'error'; did you mean 'strerror'? [-Wimplicit-function-declaration]
> 37 | error (exit_failure, errnum,
> ...
> "error.h" is a local file with:
>
> // -*- C++ -*-
> /* Copyright (C) 1989-2020 Free Software Foundation, Inc.
> Written by James Clark (jjc@jclark.com)
> [...]
> class errarg {
The 'openat-die' module depends on the 'error' module
https://www.gnu.org/software/gnulib/MODULES.html#module=error
So you now have a conflict between Gnulib's error.h (which is
meant to make glibc's error.h portable) and groff's error.h.
Also, at link time, some linkers might be confused between the error.o
file from Gnulib (which is meant to contain glibc compatible error()
and error_at_line() functions) and groff's error.o.
What has changed between yesterday and today is that, in VPATH builds,
Gnulib's error.h was in the source directory and is now in the build
directory. Depending on the order of -I options the other error.h
is now visible.
Bruno
next prev parent reply other threads:[~2023-01-13 2:26 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 [this message]
2023-01-13 19:09 ` Bjarni Ingi Gislason
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=10435880.85pcf5A44T@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).