automake, autoconf compiling
keramida at ceid.upatras.gr
Thu Jan 13 13:47:45 PST 2005
PLEASE DON'T TOP-POST. THANK YOU :-)
On 2005-01-13 16:24, Tom Huppi <thuppi at huppi.com> wrote:
>On Thu, 13 Jan 2005, Keith Bottner wrote:
>> I am trying to get a development system setup and am having trouble
>> identifying how FreeBSD handles automake, autoconf and the like.
>> [...] I did chase them down in the /usr/local/libexec/automake18 and
>> similar directories but placing them in the path still generates
>> errors (i.e. there continues to be things that are missing at various
>> I guess my general question is: What is the standard way for setting
>> up FreeBSD to use these (GNU tools) with the least trouble across
>> disparate projects?
> I've recently been struggling with similar issues, and would be
> interested to know what others might have found effective.
I use autoconf/automake and libtool daily at work.
The programs I write have to run on at least 3 different operating
systems (FreeBSD, Linux and Solaris) without the need for constant
manual tweaking of the source.
The best way to do that is to use the same version of autotools on all
those platforms. So, I install the latest possible versions of these
tools with --prefix=/opt/autotools on all the machines I have to use,
and stop worrying about all the details.
When I have to use the tools, I add /opt/autotools/bin at the beginning
of my PATH. When I don't need them, I remove /opt/autotools/bin from my
This has worked wonders so far.
 The operative keyword here is "at work". I don't use autoconf and
friends for programs I write on my own. I prefer bsd.*.mk for that.
More information about the freebsd-questions