On Tue, 2004-09-07 at 13:26, Frank Salter wrote:
> I am using Slackware 10 and gcc 3.4.1. When compiling dia-0.94 from source
> it required /lib/cpp as the C pre-processor. A symbolic link to
> /usr/local/bin/cpp resolved the difficulty!
> However /lib and /usr/local/bin are located on different drives, and I try
> to avoid linking across drives as it appears to be bad practise. I believe
> that Slackware provides a highly standardised organisation and its manifest
> shows NO file /lib/cpp.
> I have previously compiled early versions of dia and I can not remember
> having to create such a symbolic link, but I am unable to say that /lib/cpp
> did not exist in my distribution.
> cpp appears to be a strange thing to find in a library. Is this intentional
> or is it an error?
http://www.pathname.com/fhs/pub/fhs-2.3.html#LIBESSENTIALSHAREDLIBRARIESANDKERN
says:
"If a C preprocessor is installed, /lib/cpp must be a reference to it,
for historical reasons. [...]"