From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 25401@debbugs.gnu.org
Subject: bug#25401: tcc fails to build (test failure)
Date: Mon, 09 Jan 2017 10:05:53 +0100 [thread overview]
Message-ID: <87wpe4r4b2.fsf@gnu.org> (raw)
In-Reply-To: <87inppcizn.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 08 Jan 2017 22:59:29 +0100")
Ricardo Wurmus <rekado@elephly.net> skribis:
> The package “tcc” fails to build. The check phase fails:
>
> starting phase `check'
> make -C tests test
> make[1]: Entering directory '/tmp/guix-build-tcc-0.9.26.drv-0/tcc-0.9.26/tests'
> ------------ hello-exe ------------
> ../tcc -B.. ../examples/ex1.c -o hello || (../tcc -vv; exit 1) && ./hello
> ------------ hello-run ------------
> ../tcc -B.. -run ../examples/ex1.c
> Hello World
> gcc -o libtcc_test libtcc_test.c ../libtcc.a -I.. -Wall -g -O2 -fno-strict-aliasing -Wno-pointer-sign -Wno-sign-compare -Wno-unused-result -DCONFIG_TCC_SYSINCLUDEPATHS="\"/gnu/store/iwgi9001dmmihrjg4rqhd6pa6788prjw-glibc-2.24/include:/gnu/store/jc898psn5yc9s328nn8fya3sc2daf037-linux-libre-headers-4.4.18/include:{B}/include\"" -DCONFIG_TCC_LIBPATHS="\"/gnu/store/iwgi9001dmmihrjg4rqhd6pa6788prjw-glibc-2.24/lib\"" -DCONFIG_TCC_CRTPREFIX="\"/gnu/store/iwgi9001dmmihrjg4rqhd6pa6788prjw-glibc-2.24/lib\"" -DCONFIG_TCC_ELFINTERP="\"/gnu/store/iwgi9001dmmihrjg4rqhd6pa6788prjw-glibc-2.24/lib/ld-linux-x86-64.so.2\"" -DTCC_TARGET_X86_64 -lm -ldl
> make[1]: *** [Makefile:63: hello-exe] Segmentation fault
FWIW it started failing after the last ‘core-updates’ merge, which
updated Binutils and glibc, among other things.
We should check whether tinycc Git master has this problem.
Ludo’.
next prev parent reply other threads:[~2017-01-09 9:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 21:59 bug#25401: tcc fails to build (test failure) Ricardo Wurmus
2017-01-09 9:05 ` Ludovic Courtès [this message]
2017-01-09 20:44 ` ng0
2017-01-10 8:21 ` Ludovic Courtès
2017-01-10 9:17 ` ng0
2018-02-05 22:10 ` 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=87wpe4r4b2.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25401@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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).