> Yes, the change for arch is from /lib to /usr/lib, though I
> haven't found the specifics for cpp. My guess at this point
> is that a sym link isn't being made.

> I'm checking all ends -- if it isn't a whacky path in
> tdebase, I'll report back and close the report. I haven't
> had the couple of hours needed to pick through this
> line-by-line yet. I'll hopefully get some time tonight.
> Nothing like having 3 kids between 7 and 13 to make that
> evaporate though :)

I don't think this a a whacky path in tdebase. tdebase merely uses rpcgen as a build tool. rpcgen gets built when building glibc, and although Arch has moved to 2.16, the code snippets for the cpp executable path have not changed at least since 2.11.1.

If those code snippets in glibc have not changed then updating to 2.16 would not cause breakage. Since cpp is built in the gcc package, from your previous post I'm guessing you'll find the missing sym link breakage in one of these two places:

[2012-07-03 11:15] upgraded gcc (4.7.1-1 -> 4.7.1-3)
[2012-07-05 19:59] upgraded gcc (4.7.1-3 -> 4.7.1-4)

One or both of those packages no longer creates the /lib/cpp -> /usr/bin/cpp sym link. I'm guessing the 4.7.1-1 package creates the sym link because you were able to build tdebase and were so happy to find the kate/kwrite issues gone. :-)

Darrell