unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Tomas Korbar <tkorbar@redhat.com>
To: guile-devel@gnu.org
Subject: Guile 3.0.7 can not be compiled on Fedora rawhide
Date: Thu, 15 Jul 2021 14:12:18 +0200	[thread overview]
Message-ID: <CABpWmcz-O+Rg4ODLAavnE7DrRemSwb_Oq9EGnqoDXph_sr95Sg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 607 bytes --]

Hi Guys,
I am trying to package guile 3.0.7 into Fedora but I encountered a problem.
In sources, there is a header lib/libc-config.h and then there is
preprocessor condition for presence of __attribute_maybe_unused__ macro.
This macro is newly defined in the latest version of glibc which we have in
Fedora rawhide but other macros upon which guile relies are not defined,
specifically it is __attribute_nonnull__. Do you have any idea how to solve
this situation? Currently guile 3.0.7 can not be compiled on Fedora rawhide
without manual removal of previously described conditional.

Thanks for any help.

[-- Attachment #2: Type: text/html, Size: 684 bytes --]

                 reply	other threads:[~2021-07-15 12:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CABpWmcz-O+Rg4ODLAavnE7DrRemSwb_Oq9EGnqoDXph_sr95Sg@mail.gmail.com \
    --to=tkorbar@redhat.com \
    --cc=guile-devel@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).