On Tue, 1 Jul 2003, Jani Taskinen wrote:
>
> And that is bad because..?
> What error lead to adding this? (would be nice to know..)
The default compiler paths (usually /usr/include and
/usr/lib) should not be added, because non-default paths
should always take precedent. Some recent compilers are
even eliminating these paths automatically.
The simplest case is an outdated system library in /usr where
you want to compile against your own version in ~/myroot.
You can achieve the latter by supplying appropiate
CPPFLAGS/LDFLAGS. The autoconf system should not try to
overrule that.
In my particular case, I was building a set of binaries for
glibc 2.1 on a glibc 2.3 based system. When adding
-L/usr/lib, gcc would try to build a binary using (1) the
glibc 2.1 dynamic linker/C library and (2) a library compiled
against glibc 2.3. That confuses the hell out of ld, because
(2) expects newer symbols which simply don't exist yet in
(1).
- Sascha
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
