[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#630094: gdc looks for cc1d in wrong path



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



Reply to: