uired?
I guess, not.
Maybe /lib/cpp is used as a last resort, and ./configure couldn't find
cpp elsewhere on your system. I wonder why it actually tried to use it
when it didn't exist.
In a minimal Debian system, dia builds fine without /lib/
development of dia
Subject: Re: /lib/cpp
On Tue, 2004-09-07 at 14:01, Roland Stigge wrote:
>
http://www.pathname.com/fhs/pub/fhs-2.3.html#LIBESSENTIALSHAREDLIBRARIESANDK
ERN
>
> says:
>
> "If a C preprocessor is installed, /lib/cpp must be a reference to it,
>
On Tue, 2004-09-07 at 14:01, Roland Stigge wrote:
> 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. [...]"
Using it would b
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
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
