[asterisk-dev] autoconf issues for FreeBSD

Kevin P. Fleming kpfleming at digium.com
Wed Oct 4 18:37:45 MST 2006


----- Luigi Rizzo <rizzo at icir.org> wrote:
> I am pretty sure that the code below (which was my patch at the time)
> is NOT a proper fix - i would expect autoconf to deal with platform
> issues
> without having us deal with them on each and every port.

That fix probably won't work correctly any longer, since the change to use ASTCFLAGS and ASTLDFLAGS for the build system.

autoconf itself does nothing to increase platform compatibility; it is a tool that allows a package builder to increase compatibility. The benefits from autoconf are derived entirely from the logic that we put in the configure script, not autoconf itself.

Once again (I'll agree with Russell here) it makes absolutely no sense for /usr/local to be the standard place for libraries to be installed, but that they are not in the search path for the compiler and linker. All this does is require every package that wants to build on FreeBSD to require special logic to add them to the search path, when the FreeBSD toolchain could easily have these paths embedded into the toolchain by default. How frustrating :-)

-- 
Kevin P. Fleming
Senior Software Engineer
Digium, Inc.



More information about the asterisk-dev mailing list