From: Danny Milosavljevic <dannym@scratchpost.org>
To: Pjotr Prins <pjotr2017@thebird.nl>, 30411@debbugs.gnu.org
Subject: [bug#30411] [PATCH] gnu: ldc: Update to 1.7.0.
Date: Tue, 20 Feb 2018 10:47:20 +0100 [thread overview]
Message-ID: <20180220104720.2cc49871@scratchpost.org> (raw)
In-Reply-To: <20180218214110.GB9488@thebird.nl>
Hi Pjotr,
On Sun, 18 Feb 2018 22:41:10 +0100
Pjotr Prins <pjotr2017@thebird.nl> wrote:
> Danny, do you mind fixing. I am on the road and would like to get it
> into the new release.
Sure, no problem.
But building ldc 0.17.4 I get phobos datetime test failures.
Not sure why - because as you've written it, ctest shouldn't have tested phobos.
Also, ldc 1.7 does use phobos. I determined this as follows:
I removed phobos-src from ldc-bootstrap, then used the resulting ldc-bootstrap
to build ldc 1.7. It failed. I tried to excise phobos users from it but gave up.
(Even ldc 1.1 used std.datetime during building)
So I reverted the "check" phase.
Also, ldc 1.7.0 test failure on the X200 laptop:
sh: line 1: 16660 Illegal instruction /tmp/guix-build-ldc-1.7.0.drv-0/build/dmd-testsuite-debug/runnable/test_cdvecfill_1 > /tmp/guix-build-ldc-1.7.0.drv-0/build/dmd-testsuite-debug/1d696d6e3478bf73e2aaef0f8b23bba98e05e3cd74f80b02330a43bd3d2595a3 2>&1
... runnable/test_cdvecfill.d -O (-mcpu=avx -mcpu=avx2) -conf=/tmp/guix-build-ldc-1.7.0.drv-0/build/bin/ldc2.conf -g -link-debuglib
Test failed. The logged output:
/tmp/guix-build-ldc-1.7.0.drv-0/build/bin/ldmd2 -conf= -m64 -Irunnable -O -od/tmp/guix-build-ldc-1.7.0.drv-0/build/dmd-testsuite-debug/runnable -of/tmp/guix-build-ldc-1.7.0.drv-0/build/dmd-testsuite-debug/runnable/test_cdvecfill_0 runnable/test_cdvecfill.d
/tmp/guix-build-ldc-1.7.0.drv-0/build/dmd-testsuite-debug/runnable/test_cdvecfill_0
/tmp/guix-build-ldc-1.7.0.drv-0/build/bin/ldmd2 -conf= -m64 -Irunnable -O -mcpu=avx -od/tmp/guix-build-ldc-1.7.0.drv-0/build/dmd-testsuite-debug/runnable -of/tmp/guix-build-ldc-1.7.0.drv-0/build/dmd-testsuite-debug/runnable/test_cdvecfill_1 runnable/test_cdvecfill.d
/tmp/guix-build-ldc-1.7.0.drv-0/build/dmd-testsuite-debug/runnable/test_cdvecfill_1
Which is understandable because the X200 laptop doesn't have AVX.
It's building another round now - let's see.
next prev parent reply other threads:[~2018-02-20 9:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 14:12 [bug#30411] [FIXME] Dlang ldc and dub packages fail on core-updates Pjotr Prins
2018-02-18 6:09 ` [bug#30411] [PATCH] gnu: ldc: Update to 1.7.0 pjotr.public12
2018-02-18 12:34 ` Danny Milosavljevic
2018-02-18 21:58 ` Pjotr Prins
[not found] ` <20180218214110.GB9488@thebird.nl>
2018-02-20 9:47 ` Danny Milosavljevic [this message]
2018-02-21 1:26 ` Pjotr Prins
2018-02-22 1:42 ` Pjotr Prins
2018-02-23 11:59 ` bug#30411: " Danny Milosavljevic
2018-02-23 17:10 ` [bug#30411] " Pjotr Prins
2018-02-23 17:31 ` Leo Famulari
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=20180220104720.2cc49871@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=30411@debbugs.gnu.org \
--cc=pjotr2017@thebird.nl \
/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).