From: Andreas Enge <andreas@enge.fr>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 34570@debbugs.gnu.org
Subject: bug#34570: Failure to build swig/graphviz
Date: Tue, 19 Feb 2019 10:34:01 +0100 [thread overview]
Message-ID: <20190219093401.GA6522@jurong> (raw)
In-Reply-To: <20190219101632.7b0c1b7d@scratchpost.org>
On Tue, Feb 19, 2019 at 10:16:32AM +0100, Danny Milosavljevic wrote:
> I think that the test suite contains multiple sets of tests and and earlier set
> failed (the 514 perl5 tests apparently didn't fail; the warning shouldn't
> make tests fail anyway). What's before what you posted in the log?
Lots of lines similar to these:
> > \@ build-log 23167 506
> > In file included from /gnu/store/im7irb1qnmvwypz53dxv5i75wy94dcz5-glibc-2.28/include/bits/libc-header-start.h:33:0,
> > from /gnu/store/im7irb1qnmvwypz53dxv5i75wy94dcz5-glibc-2.28/include/string.h:26,
> > from multi_import_b_wrap.cxx:341:
> > /gnu/store/im7irb1qnmvwypz53dxv5i75wy94dcz5-glibc-2.28/include/features.h:381:4: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Wcpp]
> > # warning _FORTIFY_SOURCE requires compiling with optimization (-O)
In the meantime I got around the problem by copying the build from berlin,
so I also cannot reproduce the failed build. Apparently some machine did
correctly compute the derivation; if there is not an obvious error somewhere,
it might be easier to close the bug report as not reproducible or non-deter-
ministic.
Andreas
next prev parent reply other threads:[~2019-02-19 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 9:11 bug#34570: Failure to build swig/graphviz Andreas Enge
2019-02-19 9:16 ` Danny Milosavljevic
2019-02-19 9:34 ` Andreas Enge [this message]
2019-02-19 22:57 ` Andreas Enge
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190219093401.GA6522@jurong \
--to=andreas@enge.fr \
--cc=34570@debbugs.gnu.org \
--cc=dannym@scratchpost.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).