From: Hey Ya <cali.dot.mero@gmail.com>
To: 44082@debbugs.gnu.org
Subject: bug#44082: make error | #include nested too deeply: #include <gc/gc.h>
Date: Mon, 19 Oct 2020 21:53:22 +0200 [thread overview]
Message-ID: <CAGeopBcghzGq2ODWyK6QD7DJrkaqAexDtAyOf9Sfy+x9MZbNSA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
Building guile 3.0.4 from source on debian buster fails with error.
.......
from
/home/x0r/Opt/guile-3.0.4/lib/gc-7.4.0/include/gc/gc.h:2,
from
/home/x0r/Opt/guile-3.0.4/lib/gc-7.4.0/include/gc/gc.h:2,
from
/home/x0r/Opt/guile-3.0.4/lib/gc-7.4.0/include/gc/gc.h:2,
from
/home/x0r/Opt/guile-3.0.4/lib/gc-7.4.0/include/gc/gc.h:2,
from
/home/x0r/Opt/guile-3.0.4/lib/gc-7.4.0/include/gc/gc.h:2,
from
/home/x0r/Opt/guile-3.0.4/lib/gc-7.4.0/include/gc/gc.h:2,
from ../libguile/bdw-gc.h:48,
from ../libguile/gc.h:142,
from ../libguile/pairs.h:26,
from ../libguile/alist.h:26,
from ../libguile.h:34,
from guile.c:38:
/home/x0r/Opt/guile-3.0.4/lib/gc-7.4.0/include/gc/gc.h:2:19: error:
#include nested too deeply
#include <gc/gc.h>
^
[-- Attachment #2: Type: text/html, Size: 1220 bytes --]
reply other threads:[~2020-10-19 19:53 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=CAGeopBcghzGq2ODWyK6QD7DJrkaqAexDtAyOf9Sfy+x9MZbNSA@mail.gmail.com \
--to=cali.dot.mero@gmail.com \
--cc=44082@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).