I have just converted some of my VMs to no-multilib and removed CONFIG_IA32_EMULATION from the kernel. With a few exceptions, everything works fine. Unfortunately, I cannot re-emerge open-vm-tools. Reproducible: Always Steps to Reproduce: 1. eselect profile set default/linux/amd64/10.0/no-multilib 2. emerge -1 sandbox glibc gcc && rm /etc/env.d/04multilib && env-update && . /etc/profile && fix_libtool_files $(gcc -dumpversion) 3. update kernel to set CONFIG_IA32_EMULATION=n, rebuild, start new kernel 4. emerge open-vm-tools Actual Results: compile fails due to cpp failure in /usr/bin/rpcgen. More information in the build log that I'll attach. >>> Compiling source in /var/tmp/portage/app-emulation/open-vm-tools-0.0.2010091 9.301124/work/open-vm-tools-2010.09.19-301124 ... make -sj5 Making all in lib Making all in guestRpc cannot find any C preprocessor (cpp) /usr/bin/rpcgen: C preprocessor failed with exit code 1 make[2]: *** [nicinfo.h] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 Expected Results: open-vm-tools should've compiled successfully. Build log and emerge --info to follow.
Created attachment 250305 [details] open-vm-tools-0.0.20100919.301124_build.log
Created attachment 250307 [details] open-vm-tools-0.0.20100919.301124_emerge-info.txt
One more thing I forgot: I do have a cpp: $ file /usr/bin/cpp /usr/bin/cpp: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped However, I was surprised it wasn't associated with a package: $ qfile -v /usr/bin/cpp $ $ find /var/db/pkg -name CONTENTS -exec fgrep /usr/bin/cpp {} /var/db/pkg/sys-devel/gcc-4.4.3-r2/CONTENTS:sym /usr/bin/cpp-4.4.3 -> /usr/x86_64-pc-linux-gnu/gcc-bin/4.4.3/x86_64-pc-linux-gnu-cpp 1286511852 Is this an open-vm-tools bug, a gcc-config or gcc bug, or a PIBKAC?
I manually symlinked my /usr/bin/cpp from /usr/x86_64-pc-linux-gnu/gcc-bin/4.4.3/x86_64-pc-linux-gnu-cpp That resolved the issue. The question remains why that manual symlinking was necessary.
if the issue no longer exists after doing `gcc-config -f -O`, then there really isnt much debugging we can do into the issue also, it's PEBKAC, not PIBKAC