net-fs/nfs-utils-1.2.3-r1 (which is latest and latest stable version of the package) fails to build with /usr/bin/rpcgen -l -o mount_clnt.c mount.x cannot find any C preprocessor (cpp) /usr/bin/rpcgen: C preprocessor failed with exit code 1 make[2]: *** [mount_clnt.c] Error 1 make[2]: Leaving directory `/tmp/portage/net-fs/nfs-utils-1.2.3-r1/work/nfs-utils-1.2.3/support/export' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/portage/net-fs/nfs-utils-1.2.3-r1/work/nfs-utils-1.2.3/support' make: *** [all-recursive] Error 1 emake failed This issue is also mentioned in Bug #358509. Reproducible: Always Steps to Reproduce: 1. emerge =net-fs/nfs-utils-1.2.3-r1 Actual Results: /usr/bin/rpcgen -l -o mount_clnt.c mount.x cannot find any C preprocessor (cpp) /usr/bin/rpcgen: C preprocessor failed with exit code 1 make[2]: *** [mount_clnt.c] Error 1 make[2]: Leaving directory `/tmp/portage/net-fs/nfs-utils-1.2.3-r1/work/nfs-utils-1.2.3/support/export' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/portage/net-fs/nfs-utils-1.2.3-r1/work/nfs-utils-1.2.3/support' make: *** [all-recursive] Error 1 emake failed Expected Results: The package is built fine.
Created attachment 266251 [details] emerge --info
Created attachment 266253 [details] Buidl.log
Sorry, misinterpreted Bug #358509 comment #1. The reporter says that the stable fails to build but he meant the previous stable, probably 1.1.4-r1.
are you sure your `cpp` works ? go into the build dir and run things yourself cd /tmp/portage/net-fs/nfs-utils-1.2.3-r1/work/nfs-utils-1.2.3/support/export strace -s 4096 -f -o log /usr/bin/rpcgen -l -o mount_clnt.c mount.x if it still fails, then post that log as an attachment
Created attachment 266307 [details] strace -s 4096 -f -o strace.log /usr/bin/rpcgen -l -o mount_clnt.c mount.x (In reply to comment #4) > are you sure your `cpp` works ? I may be ignorant of something but at the moment I am pretty sure my cpp is ok: black:~> cpp --version cpp (Gentoo 4.4.5 p1.2, pie-0.4.5) 4.4.5 Copyright (C) 2010 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. I also compile a lot, and this involves a lot of preprocessing. Previously I have never seen a message like this one. > cd /tmp/portage/net-fs/nfs-utils-1.2.3-r1/work/nfs-utils-1.2.3/support/export > strace -s 4096 -f -o log /usr/bin/rpcgen -l -o mount_clnt.c mount.x > > if it still fails, then post that log as an attachment Yes, it still fails. I have attached the log.
black:~> which cpp /usr/bin/cpp black:~> ls /lib/cpp /usr/ccs/lib/cpp ls: cannot access /lib/cpp: No such file or directory ls: cannot access /usr/ccs/lib/cpp: No such file or directory Now that I created a symlink from /usr/bin/cpp to /lib/cpp, the package builds ok. But in my opinion, these 2 paths are very wrong places for the cpp binary.
I remember to have seen this layout (/usr/ccs/{bin,lib}) on Solaris, years ago. I don't have a machine running SunOS to check this.
This seems to be a problem with missing /lib -> /lib64 symlink. When I tried to run "gcc-config 1" (I only have one version of gcc installed on this machine) gcc-config returned with the following error message: cp: cannot create regular file `//lib/cpp': No such file or directory and yes, /lib is missing... So this bug might be a result of bug #358143
let's assume that. otherwise, gcc-config makes sure that /lib/cpp exists. *** This bug has been marked as a duplicate of bug 358143 ***
Yes, I am a victim of Bug #358143. I was sure that the symlink is in place and have never checked this. Thank everybody for support!
