On 05/13/17 12:16, Sevan Janiyan wrote:
On 13/05/2017 17:08, Jason Bacon wrote:
Anybody ever run into an issue like this when bootstrapping pbulk?
Yes, when your toolchain is incomplete.
Why is it trying to execute cc1?
'gcc: error trying to exec 'cc1': execvp: No such file or directory'
Sevan
cc1 is one of the compile stages invoked by gcc;
bacon ~ 67: strings /usr/local/bin/gcc5 | grep cc1|more
%(cc1_cpu) %{profile:-p}
cc1_options
cc1plus
cc1 -E %{traditional|traditional-cpp:-traditional-cpp}
cc1_cpu
cc1 -fpreprocessed %{save-temps*:%b.i}
%{!save-temps*:%g.i} %(cc1_options)}
%{!save-temps*:%{!traditional-cpp:%{!no-integrated-cpp: cc1
%(cpp_unique_options) %(cc1_options)}}} %{!fsyntax-only:%(invoke_as)}}}}
...
The toolchain is not incomplete. It works fine outside the chroot.
The cc1 command is there under $prefix/libexec, but somehow gcc can't
find it when I run it in the sandbox. I would have thought that gcc
uses rpath to locate cpp, cc1, etc, but this seems to be some sort of
odd PATH issue that I'm having a hard time tracking down.
Thanks,
JB