Date: Wed, 10 Mar 2010 12:04:37 -0600 From: "Karl O. Pinc" References: <1268242750.8679.0@...1207...> <4B97DCEC.9020108@...1114...> In-Reply-To: <4B97DCEC.9020108@...1114...> (from openvpn.list@...1114... on Wed Mar 10 11:54:52 2010) Message-Id: <1268244277.8679.3@...1207...> MIME-Version: 1.0 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="UTF-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline To: David Sommerseth Cc: Alon Bar-Lev , openvpn-devel@lists.sourceforge.net On 03/10/2010 11:54:52 AM, David Sommerseth wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > On 10/03/10 18:39, Karl O. Pinc wrote: > > On 03/10/2010 11:19:13 AM, Alon Bar-Lev wrote: > >> I will try to explain again. > >> > >> You have two roles of environments: > >> > >> 1. Developer/packager workstation. > >> > >> 2. Target environment. > >> > >> For example, 1 would be my computer, and 2 would be the old redhat > >> computer. > >> > >> You go to (1) and do: > >> $ autoreconf -ivf > >> $ ./configure && make dist > >> > >> Now, you transfer the tarball to users, the old redhat computer is=20 > >> one > >> of them. The tarball will work WITHOUT ANY > AUTOCONF/AUTOMAKE/LIBTOOL > >> installed. > >> > >> I use older environments as (2) such as solaris-8. > >=20 > > And you don't generally want to be running ./configure from within > > a rpm specfile, so the same is true of using the rpm tools: >=20 > This is not correct. In fact, you often use the %configure macro in > %build, which does call ./configure. The only "allowed" exception > from > not calling %configure is when ./configure is not a native autotools > generated configure script. Ok. I'm totally wrong here. But how is it then that Alon does not run ./configure on machine 2 above? >=20 > > On machine 2 you download the tarball, the specfile, (and > > any patches the rpm maintainer wants to include in the > > packaged version) and run the rpm build tools on the > > spec file to build a binary rpm.=20=20 > >=20 > > Note that http://www.rpm.org/max-rpm/s1-rpm-inside-scripts.html > > says:=20 > >=20 > > "Once the %prep script has gotten everything ready for the build, > the % > > build script is usually somewhat anti-climactic =E2=80=94 normally invo= king=20 > > make, maybe a configuration script, and little else.=20 >=20 > It's %build which need to do the %configure. All patching must=20 > happen > on %prep. But you are right, if there are applied patches which > updates > some of the autotools generated files, I believe autotools need to be > run again. Right, Alon? Nothing should patch the autotools generated files, just the autotools source files. Right? Karl Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein