public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/94623] ice for ./gdc.test/compilable/interpret3.d
Date: Mon, 20 Apr 2020 20:11:20 +0000	[thread overview]
Message-ID: <bug-94623-4-5ERyixcjK4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94623-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94623

--- Comment #19 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to ibuclaw from comment #17)
> (In reply to David Binderman from comment #16)
> > 
> > I am struggling to understand what this output means:
> > 
> It's picking up the modules from a system location.  These most certainly
> don't belong to the gdc compiler.  Which bad package maintainer is
> installing compiler-specific modules in a common location? LDC?

I have package ldc-druntime-devel version 1.15.0 installed, 
so that looks to be the source of the problem.

  parent reply	other threads:[~2020-04-20 20:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 16:45 [Bug d/94623] New: " dcb314 at hotmail dot com
2020-04-17 17:09 ` [Bug d/94623] " ibuclaw at gdcproject dot org
2020-04-17 18:05 ` dcb314 at hotmail dot com
2020-04-19 13:30 ` ibuclaw at gdcproject dot org
2020-04-19 14:07 ` dcb314 at hotmail dot com
2020-04-19 17:07 ` ibuclaw at gdcproject dot org
2020-04-20  7:54 ` dcb314 at hotmail dot com
2020-04-20  8:05 ` dcb314 at hotmail dot com
2020-04-20  8:11 ` ibuclaw at gdcproject dot org
2020-04-20  8:27 ` ibuclaw at gdcproject dot org
2020-04-20  8:31 ` dcb314 at hotmail dot com
2020-04-20  9:14 ` dcb314 at hotmail dot com
2020-04-20 15:51 ` ibuclaw at gdcproject dot org
2020-04-20 16:53 ` dcb314 at hotmail dot com
2020-04-20 17:27 ` ibuclaw at gdcproject dot org
2020-04-20 17:40 ` ibuclaw at gdcproject dot org
2020-04-20 18:31 ` dcb314 at hotmail dot com
2020-04-20 19:31 ` ibuclaw at gcc dot gnu.org
2020-04-20 20:04 ` ibuclaw at gdcproject dot org
2020-04-20 20:11 ` dcb314 at hotmail dot com [this message]
2020-04-20 20:20 ` ibuclaw at gdcproject dot org
2020-04-21  6:58 ` cvs-commit at gcc dot gnu.org
2020-04-21  7:01 ` ibuclaw at gdcproject dot org
2020-04-21  7:09 ` dcb314 at hotmail dot com
2020-04-21  9:59 ` ibuclaw at gdcproject dot org
2020-04-21 10:03 ` ibuclaw at gdcproject dot org

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-94623-4-5ERyixcjK4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.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).