Package: gdc
Version: 4.9.2-2
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I was trying to learn D, and wrote the following program and tried to
compile it. That did not occur.
bash% cat hello.d
import std.stdio;
void main()
{
writeln("Hello World!");
}
bash% gdc hello.d
hello.d:2: error: module stdio is in file 'std/stdio.d' which cannot be read
import path[0] = /usr/include/d/4.9
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
The program did not compile due to missing standard library
* What outcome did you expect instead?
The program should have cmopiled.
gdc based on the package page at
https://packages.debian.org/jessie/gdc has a dependency on
libphobos-dev. This package is not available for PPC systems. It
is available for a limited set of architectures. Why is gdc availble
for installation on a CPU architecture if one of its dependencies is
not available on that same architecture ? The installation should
not have occurred.
Since libphobos is not available, I would have expected that gdc would
not have installed. Yet it did just that, install it self.
With libphobos not available, I can't make use of D.
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing')
Architecture: powerpc (ppc)
Kernel: Linux 3.13-1-powerpc-smp (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages gdc depends on:
ii gdc-4.9 4.9.2-10
gdc recommends no packages.
gdc suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
