-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 21/02/12 17:12, Alon Bar-Lev wrote: > On Tue, Feb 21, 2012 at 5:56 PM, David Sommerseth > <openvpn.l...@topphemmelig.net> wrote: >> There might be similar restrictions related to autoconf/automake >> tools too. As James has some automation for the Access Server >> builds for those supported platforms, we must be sure we don't break >> that for him. From what I see, on a recent 5.7 box ... > > No there is none. Unlike other dependencies autotools dependencies are > of development machine. You should create tarball on newer machine > then compile it on the target platform. Target platform may not have > autotools installed at all. > > The new build system will support >=autoconf-2.60, automake>=1.10, > libtool>=2.2
That is not how James does his builds, from what I've understood. He does builds in his own compile farm straight from source repositories. James might just as well pop up NACKing things if these changes breaks his tool chain. To put is simple: We are not allowed to break his environments. On the RHEL5.7 base, libtool-1.5.22 is the base version. > Again, from experience generating tarball using these versions tends > to work well on very old platforms. That's good, which can solve RHEL4 issues in a nice way. But I expect James to do plenty of RHEL5 builds in the future, so there is noway we are allowed to break this. kind regards, David Sommerseth -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9D2a4ACgkQDC186MBRfrr4RQCdFid58/1E8SEDyAs7QQvoo83q KrkAn0KXXd5WRDJFeUnPa+iG1aIuH0CC =uw9T -----END PGP SIGNATURE-----
