[asterisk-dev] autoconf issues for FreeBSD

[Steve Kennedy]

On Wed, Oct 04, 2006 at 08:37:45PM -0500, Kevin P. Fleming wrote:

> ----- 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 :-)

Sun does similar things. Standard stuff goes into /usr/bin etc
Optional Sun packages (or some 3rd party stuff) into /opt as a base
Sunfreeware into various areas with config under /etc/sfw binaries
/usr/sfw/bin etc
BSD's system stuff normal, everything else /usr/local


Steve

-- 
NetTek Ltd  UK mob +44-(0)7775 755503
UK +44-(0)20 79932612 / US +1-(310)8577715 / Fax +44-(0)20 7483 2455
Skype/GoogleTalk/AIM/Gizmo/Mac stevekennedyuk / MSN steve at gbnet.net
Euro Tech News Blog http://eurotechnews.blogspot.com