Message-ID: <20100310172636.20173.qmail@...1287...> Date: Wed, 10 Mar 2010 18:26:36 +0100 From: Peter Stuge References: <1268218182-21015-1-git-send-email-openvpn.list@...1114...> <4B978D0E.9090606@...1114...> <9e0cf0bf1003100842r408389c7occa7dcf0d27ad59a@...278...> <4B97CDF3.6060703@...1114...> <9e0cf0bf1003100903k3647ba78t40bb93d5d9a5d8d8@...278...> <4B97D385.3010506@...1114...> MIME-Version: 1.0 In-Reply-To: <4B97D385.3010506@...1114...> Subject: Re: [Openvpn-devel] [PATCH] On TARGET_LINUX define _GNU_SOURCE if not defined List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Content-Disposition: inline To: openvpn-devel@lists.sourceforge.net David Sommerseth wrote: > it's a requirement to be able to build OpenVPN on RHEL4.6. As Alon explained, building is not the problem. autotools are used when preparing git source for build. This is done for every release, so that there is a ready-made configure script included in the tarball. When building a release (or snapshot, if there are any) from such a tarball then autoconf is no longer relevant, it was run only when the tarball was created. RHEL4.6 can easily build a release that was prepared using the most recent autoconf. That RHEL4.6 system doesn't need autoconf installed at all. The only way autoconf on that RHEL4.6 would be relevant is if those RHEL4.6 systems strictly need to build directly from git source, as opposed to building from a prepared tarball. Is that the case? //Peter