unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
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 12:22:25 +0100	[thread overview]
Message-ID: <9607660a-fc03-0504-3b0f-d89f8944e26e@geeklan.co.uk> (raw)
In-Reply-To: <b032a1ad-a2af-190e-da03-a69e9d15d542@geeklan.co.uk>

On 01/08/2023 12:11, Sevan Janiyan wrote:
> The MAX macro in socket.h conflicts with the MAX macro in the system 
> header files.

Forgot to mention, the header inclusions in the diff are because 
scm_t_dynstack & scm_t_dynstack typedefs were commented out of 
libguile/scm.h (resolving the redefinition).


Sevan





      reply	other threads:[~2023-08-01 11:22 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
2023-08-01 11:11   ` Sevan Janiyan
2023-08-01 11:22     ` Sevan Janiyan [this message]

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=9607660a-fc03-0504-3b0f-d89f8944e26e@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).