From: Sevan Janiyan <venture37@geeklan.co.uk>
To: 41467@debbugs.gnu.org
Subject: bug#41467: Compiling extensions using Guile 3.0.2 headers doesn't work with clang without -std=c11
Date: Tue, 1 Aug 2023 02:38:57 +0100 [thread overview]
Message-ID: <ca4a9ed0-3cd9-026c-c7f8-36451cbf8569@geeklan.co.uk> (raw)
In-Reply-To: <E1jcEUS-0006mr-SE@smtp.tt-solutions.com>
Hi,
Redefinitions are part of C11 and compilers which support C11 and
default to C11 mode would have masked the issue which is why we are
here. Because of the redefinitions, it is not possible to build Guile
with older compilers which only support C99.
I hit this issue attempting to build Guile 3.0.9 with GCC 4.0.1.
The first error being
CC libgnu_la-regex.lo
In file included from ../libguile/threads.h:27,
from glthread/lock.h:27,
from regex_internal.h:56,
from regex.c:71:
../libguile/dynstack.h:37: error: redefinition of typedef 'scm_t_dynstack'
../libguile/scm.h:825: error: previous declaration of 'scm_t_dynstack'
was here
In file included from ../libguile/smob.h:28,
from ../libguile/threads.h:29,
from glthread/lock.h:27,
from regex_internal.h:56,
from regex.c:71:
../libguile/print.h:79: error: redefinition of typedef 'scm_print_state'
../libguile/scm.h:824: error: previous declaration of 'scm_print_state'
was here
make[4]: *** [libgnu_la-regex.lo] Error 1
There's more issues after addressing these. I will follow up with a
patch of what I took out for the build to succeed (not necessarily
correct but to highlight where the issues are).
Sevan
next prev parent reply other threads:[~2023-08-01 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 20:42 bug#41467: Compiling extensions using Guile 3.0.2 headers doesn't work with clang without -std=c11 Vadim Zeitlin
2023-08-01 1:38 ` Sevan Janiyan [this message]
2023-08-01 11:11 ` Sevan Janiyan
2023-08-01 11:22 ` Sevan Janiyan
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=ca4a9ed0-3cd9-026c-c7f8-36451cbf8569@geeklan.co.uk \
--to=venture37@geeklan.co.uk \
--cc=41467@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).