Your message dated Mon, 13 Jun 2011 12:19:19 +0200
with message-id <4df5e427.2090...@debian.org>
and subject line Re: Bug#630094: gdc looks for cc1d in wrong path
has caused the Debian Bug report #630094,
regarding gdc looks for cc1d in wrong path
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
630094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gdc-4.4
Version: 1.063-4.4.6-2
Severity: serious
$ gdc hash.d
gdc: error trying to exec 'cc1d': execvp: No such file or directory
$ strace gdc hash.d
execve("/usr/bin/gdc", ["gdc", "hash.d"], [/* 21 vars */]) = 0
[... snipped ...]
stat("/mnt/1/usr/bin/../lib/gcc/x86_64-linux-gnu/4.4.6/cc1d", 0x7fff976f3240) =
-1 ENOENT (No such file or directory)
stat("/mnt/1/usr/bin/../lib/gcc/cc1d", 0x7fff976f3240) = -1 ENOENT (No such
file or directory)
stat("/usr/libexec/gcc/x86_64-linux-gnu/4.4.6/cc1d", 0x7fff976f3240) = -1
ENOENT (No such file or directory)
stat("/usr/libexec/gcc/x86_64-linux-gnu/cc1d", 0x7fff976f3240) = -1 ENOENT (No
such file or directory)
stat("/usr/lib/gcc/x86_64-linux-gnu/4.4.6/cc1d", 0x7fff976f3240) = -1 ENOENT
(No such file or directory)
stat("/usr/lib/gcc/x86_64-linux-gnu/cc1d", 0x7fff976f3240) = -1 ENOENT (No such
file or directory)
stat("/mnt/1/usr/bin/../lib/gcc/x86_64-linux-gnu/4.4.6/../../../../x86_64-linux-gnu/bin/x86_64-linux-gnu/4.4.6/cc1d",
0x7fff976f3240) = -1 ENOENT (No such file or directory)
stat("/mnt/1/usr/bin/../lib/gcc/x86_64-linux-gnu/4.4.6/../../../../x86_64-linux-gnu/bin/cc1d",
0x7fff976f3240) = -1 ENOENT (No such file or directory)
vfork(gdc: error trying to exec 'cc1d': execvp: No such file or directory
) = 27254
--- SIGCHLD (Child exited) @ 0 (0) ---
wait4(27254, [{WIFEXITED(s) && WEXITSTATUS(s) == 255}], 0, NULL) = 27254
stat("/tmp/ccjeVKQM.s", {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
unlink("/tmp/ccjeVKQM.s") = 0
exit_group(1) = ?
>From the strace, it seems that gdc is looking for cc1d under the '4.4.6'
subdirectory in gcc/x86_64-linux-gnu, but the gdc-4.4 package ships cc1d
in a different directory:
$ dpkg -L gdc-4.4
[... snipped ...]
/usr/lib/gcc/x86_64-linux-gnu
/usr/lib/gcc/x86_64-linux-gnu/4.4
/usr/lib/gcc/x86_64-linux-gnu/4.4/cc1d
[... snipped ...]
Manually adding a symlink 4.4.6 -> 4.4 in /usr/lib/gcc/x86_64-linux-gnu
fixes the problem.
--T
--- End Message ---
--- Begin Message ---
Version: 1.063-4.4.6-3
--- End Message ---
