Date: Thu, 13 Jan 2005 20:04:29 -0600 From: Nikolas Britton <freebsd@nbritton.org> To: Keith Bottner <keith@barkinglizards.com> Cc: "Freebsd-Newbies@Freebsd. Org" <freebsd-newbies@freebsd.org> Subject: Re: automake, autoconf compiling Message-ID: <41E728AD.2050000@nbritton.org> In-Reply-To: <20050113204932.2BAD643D54@mx1.FreeBSD.org> References: <20050113204932.2BAD643D54@mx1.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Keith Bottner wrote: >First let me say that I am definitely a newbie to FreeBSD but not to Linux >or Windows. > >I am trying to get a development system setup and am having trouble >identifying how FreeBSD handles automake, autoconf and the like. >Specifically I am trying to get the Apache log4cxx source to compile and of >course I am running into problems with automake, aclocal, autoheader, >autoconf and libtoolize not being in the path. 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 stages). > >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 have never had this problem on Linux as they have always been properly >setup on install and I want to get FreeBSD going and do it the way that is >accepted as the standard so that later generalizing my project with autoconf >will be standardized as well. > >I appreciate any feedback and realize this is a rather broad question, but >hey I said I was new to FreeBSD. > > You do know about the ports (and packages) system, correct? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41E728AD.2050000>