From: "Hannes Müller" <h.c.f.mueller@gmail.com>
To: 40780@debbugs.gnu.org
Subject: bug#40780: guile 3.0.2: Prevent warning using libguile with -Wpedantic (redefinition)
Date: Wed, 22 Apr 2020 21:30:52 +0200 [thread overview]
Message-ID: <a583e645c4018b316845fadd86a07179fabf048f.camel@gmail.com> (raw)
Dear Maintainer,
2 warnings as shown below for libguile 3.0.2 (i.e. usage of libguile in
external C code) with gcc 9.3.0 and option -Wpedantic are indicated. In
contrast I get no warnings for libguile 2.2.7 with the same compiler
options. Therefore, please fix this easy to circumvent warning.
Best regards
Hannes
In file included from /usr/include/guile/3.0/libguile/numbers.h:29,
from /usr/include/guile/3.0/libguile/array-
handle.h:27,
from /usr/include/guile/3.0/libguile.h:35,
from read_cfg.c:7:
/usr/include/guile/3.0/libguile/print.h:79:3: warning: redefinition of
typedef 'scm_print_state' [-Wpedantic]
79 | } scm_print_state;
| ^~~~~~~~~~~~~~~
In file included from /usr/include/guile/3.0/libguile.h:33,
from read_cfg.c:7:
/usr/include/guile/3.0/libguile/scm.h:824:32: note: previous
declaration of 'scm_print_state' was here
824 | typedef struct scm_print_state scm_print_state;
| ^~~~~~~~~~~~~~~
In file included from /usr/include/guile/3.0/libguile/threads.h:27,
from /usr/include/guile/3.0/libguile/async.h:25,
from /usr/include/guile/3.0/libguile.h:38,
from read_cfg.c:7:
/usr/include/guile/3.0/libguile/dynstack.h:37:3: warning: redefinition
of typedef 'scm_t_dynstack' [-Wpedantic]
37 | } scm_t_dynstack;
| ^~~~~~~~~~~~~~
In file included from /usr/include/guile/3.0/libguile.h:33,
from read_cfg.c:7:
/usr/include/guile/3.0/libguile/scm.h:825:29: note: previous
declaration of 'scm_t_dynstack' was here
825 | typedef struct scm_dynstack scm_t_dynstack;
| ^~~~~~~~~~~~~~
next reply other threads:[~2020-04-22 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 19:30 Hannes Müller [this message]
2020-12-05 11:25 ` bug#40780: guile 3.0.4: #40780 can be closed (typedef redefinition allowed in c11) Hannes Müller
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a583e645c4018b316845fadd86a07179fabf048f.camel@gmail.com \
--to=h.c.f.mueller@gmail.com \
--cc=40780@debbugs.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).