Bram Moolenaar writes:
> -------------
> On FreeBSD, NetBSD, and OpenBSD, the compiler doesn't search include
> files in /usr/local/include, and the linker doesn't search libraries in
> /usr/local/lib. Therefore some packages won't find other packages
> installed earlier. To overcome this problem, it is recommended to use
> the following options:
>
> env CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib ./configure
> -------------
Yes this is what I mean.
> Ehm, I think it's very wrong for a compiler to use files and libraries in
> /usr/local if the user didn't explicitly ask for this. That the compiler only
> uses the header files and libraries that came with it is the normal behavior.
You are entitled to your opinion. The gcc on Linux does it
differently; it searches in /usr/local by default.
> "configure" was made to find the right things on the system. This is where
> portability problems are to be solved. Thus the problem is with the configure
> script, not with FreeBSD or the compiler.
The autoconf and OpenBSD developers are aware of the issue. The *BSD
people don't want to change their gcc configuration. Maybe the next
version of autoconf will solve this issue, maybe not. For the moment,
the burden is on the *BSD users (and on me who has to explain why
libiconv was considered not present although you installed it).
Bruno
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
