From: Sergei Trofimovich <slyfox@inbox.ru>
To: 25803@debbugs.gnu.org
Subject: bug#25803: ./configure CFLAGS=-ggdb3 fails 'guile-snarf'
Date: Sun, 19 Feb 2017 22:36:39 +0000 [thread overview]
Message-ID: <20170219223639.61a78924@sf> (raw)
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
It popped out as a
https://bugs.gentoo.org/show_bug.cgi?id=608190
where one of packages failed to build with CFLAGS=-ggdb3 was guile-2.0.13
guile git master is also affected:
$ ./configure CFLAGS=-ggdb3
$ make
make[1]: Entering directory '/home/slyfox/dev/git/guile/libguile'
CC libguile_2.2_la-alist.lo
In file included from alist.c:398:0:
../libguile/alist.x: In function 'scm_init_alist':
../libguile/alist.x:2:2537: error: conflicting types for 'scm_i_foreign_call'
The problem here is in gcc -ggdb3 which leaves too much
of unrelated input. guile-snarf does not understand how to drop it:
guile/libguile $ guile-snarf alist.c -DHAVE_CONFIG_H -DBUILDING_LIBGUILE=1 -I.. -I.. -I../lib -I../lib -I/usr/lib64/libffi-3.2.1/include -I/home/slyfox/dev/git/guile -ggdb2 | wc -c
1389
guile/libguile $ guile-snarf alist.c -DHAVE_CONFIG_H -DBUILDING_LIBGUILE=1 -I.. -I.. -I../lib -I../lib -I/usr/lib64/libffi-3.2.1/include -I/home/slyfox/dev/git/guile -ggdb3 | wc -c
230085
Fails on both gcc-5.4.0 / gcc-6.3.0
--
Sergei
[-- Attachment #2: Цифровая подпись OpenPGP --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
next reply other threads:[~2017-02-19 22:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 22:36 Sergei Trofimovich [this message]
2017-02-19 22:58 ` bug#25803: [PATCH] guile-snarf: skip -g* arguments to avoid build failure Sergei Trofimovich
2017-04-19 15:20 ` Andy Wingo
2017-04-21 15:00 ` bug#25803: guile-snarf now fails when passed arguments contains whitespace Ludovic Courtès
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=20170219223639.61a78924@sf \
--to=slyfox@inbox.ru \
--cc=25803@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).