On Wed, Jun 7, 2017 at 9:44 PM, Dennis Clarke <dcla...@blastwave.org> wrote: > On 06/07/2017 08:16 PM, William A Rowe Jr wrote: >> >> As I said... checking out and building 'your own tarball' on a >> conventional system absolutely beats convincing AIX, Solaris > > By "conventional" I think you mean "Linux" or anything with a reasonable > GNU toolchain and we all know that won't happen from IBM or Oracle. At > all. Lucky for me I have the latest perl, autoconf, m4 and such built > already and "python" still blows up neatly in any attempt to build from > sources. Don't even ask about PHP ver 7.x where code really gets > gnuified and ugly.
Correct, a typical dev environment with a rather complete toolchain. The output of that ./buildconf step can be tarred up and moved onto most any other obscure architecture or build machine. This is what we do for preparation for the release tarball. If there is an issue with our ./buildconf step and specific versions of python, please share that information here so we can remediate it. >> I like Nick's suggestion, I presume you can find 'patch' on all archs. > > Yes Sir .. I am definately going in that direction. How about an easier path to that patch, though... svn diff -r1797054:HEAD https://svn.apache.org/repos/asf/apr/apr/branches/1.6.x/ You can have a look at which rev no was tagged at http://svn.apache.org/viewvc/apr/apr/tags/ and adjust the command above as appropriate (this is correct for 1.6.1 -> 1.6.x now.)
