This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug build/15823] New: Host rpcgen is sort of fundamentally broken for cross-compilers
- From: "brooks at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 08 Aug 2013 00:03:55 +0000
- Subject: [Bug build/15823] New: Host rpcgen is sort of fundamentally broken for cross-compilers
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=15823
Bug ID: 15823
Summary: Host rpcgen is sort of fundamentally broken for
cross-compilers
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: build
Assignee: unassigned at sourceware dot org
Reporter: brooks at gcc dot gnu.org
CC: carlos at redhat dot com
The rpggen program will, by default, call "/lib/cpp" as the cpp executable (see
line 81 of rpc-main.c).
If a user passes a -Y option defining a directory, it will instead append
"/cpp" to that directory name, and use that instead. (line 1319, rpc-main.c)
Thus, it is hardcoded that the name of the cpp executable must be "cpp".
However, we find that, due to
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42955, GCC does not ship a working
executable named "cpp" -- and has not for many years. (The bug is that GCC's
$target/bin/cpp is broken; only bin/$target-cpp works.)
There are of course workarounds; the glibc sunrpc/Makefile itself uses one by
defining a CPP variable and then pointing -Y at a "scripts" directory
containing a "cpp" shell script that simply executes ${CPP} $@. However, this
workaround requires every user of rpcgen to set up such a wrapper script.
It would be notably better if we could simply provide a true cpp executable
name to rpcgen directly. I note that there is not even any apparent benefit to
having the user specify a directory rather than a complete path to the
executable; the path is used for nothing else.
--
You are receiving this mail because:
You are on the CC list for the bug.