On Tue, Oct 29, 2013 at 5:21 AM, Michael Felt <mamfelt@gmail.com> wrote:
Just to verify what I should be testing - and - is it too late to get something added for packaging?

I assume that for httpd-2.4.X that should build with only apr-1.5.X (preferred), or with apr-1.4.some-minimum + apr-util-1.5.X

httpd 2.4.next will require apr-1.5.x only if using the event MPM (I doubt that works on AIX anyway).

But many if not most will be using the latest apr and apr-util.
 

What I would like to add is the buildaix scripts - similar to what I did for httpd, or at a minimum, the layout.AIX.

As apr has compiler dependancies (if you change complier you must rebuild apr) I would prefer to have the build script that changes the package name dependent on the compiler.

A nice start would be the AIX layout.

michael@x054:[/data/prj/apache/apr/apr-1.5.x-save]jsvn diff config.layout
Index: config.layout
===================================================================

Does this work with apr trunk?  It needs to be committed there first, then to 1.5.x.
 
--- config.layout       (revision 1536612)
+++ config.layout       (working copy)
@@ -229,3 +229,26 @@
     infodir:       ${exec_prefix}/share/info
     libsuffix:    -${APR_MAJOR_VERSION}
 </Layout>
+
+# AIX layout
+<Layout AIX>
+    prefix:        /opt
+    exec_prefix:   /opt
+    datadir:       /var/apr
+    localstatedir: /var
+    sysconfdir:    ${localstatedir}/apr/etc
+    mandir:        /usr/share/man
+    bindir:        ${exec_prefix}/bin
+    sbindir:       ${exec_prefix}/sbin
+    includedir:    ${exec_prefix}/include
+    libdir:        ${exec_prefix}/lib
+    libexecdir:    ${exec_prefix}/libexec
+    errordir:      ${datadir}/error
+    iconsdir:      ${datadir}/icons
+    htdocsdir:     ${datadir}/htdocs
+    manualdir:     ${datadir}/manual
+    runtimedir:    ${localstatedir}/run
+    logfiledir:    ${localstatedir}/logs
+    proxycachedir: ${localstatedir}/proxy
+    installbuilddir: ${localstatedir}/build
+</Layout>

Is it necessary to control all of these from the layout?  There are significantly more settings, generally httpd-specific, than the other layouts have.

proxycachedir?  That sounds like Apache 1.3 to me.  What uses that?





On Mon, Oct 28, 2013 at 10:37 PM, William A. Rowe Jr. <wrowe@rowe-clan.net> wrote:
On Mon, 28 Oct 2013 16:58:45 -0400
Jeff Trawick <trawick@gmail.com> wrote:

> On Mon, Oct 28, 2013 at 4:54 PM, William A. Rowe Jr.
> <wrowe@rowe-clan.net>wrote:
>
> > On Mon, 28 Oct 2013 13:01:09 -0400
> > Jeff Trawick <trawick@gmail.com> wrote:
> >
> > > On Mon, Oct 28, 2013 at 12:50 PM, Gregg Smith <gls@gknw.net>
> > > wrote:
> > >
> > > > Just a note,
> > > >
> > > >
> > > > On 10/19/2013 10:32 AM, Gregg Smith wrote:
> > > >
> > > >> On 10/19/2013 7:26 AM, Jeff Trawick wrote:
> > > >>
> > > >>> On Thu, Oct 17, 2013 at 11:08 PM, Gregg Smith <gls@gknw.net
> > > >>> <mailto: gls@gknw.net>> wrote:
> > > >>>
> > > >>>     I'd like to first rid the 1.5 traditional Windows build
> > > >>> of the Release9x & Debug9x targets. Anyone against this?
> > > >>>
> > > >>>
> > > >>> no concerns here; is there code that can get deleted too?
> > > >>>
> > > >>
> > > >> probably, I would assume so, I haven't ran it down that far
> > > >> yet.
> > > >>
> > > >
> > > > I did not do this after all nor do I think I am brave enough to.
> > > >
> > > > apr_escape, testescape and gen_test_char were added into the
> > > > build with r1534053.
> > > > .mak/.dep files were added in r1534516.
> > > >
> > > > We should be ready to go on the Windows side now.
> >
> > So, given that 1.5 remains compatible with 1.4... but projects which
> > build APR themselves will have to adapt to the new gen_test_char or
> > we need to make the suggested change, let's just take the httpd
> > example.
> >
> > Does it make more sense for httpd 2.2 Makefile.win to detect the
> > presence of gen_test_char and build it when encountered, or does it
> > make more sense to compile-link-invoke gen_test_char.c?  I'm happy
> > to make the respective change later tonight or tomorrow, based on
> > consensus.
> >
> >
> Is the Windows build interface of apr 1.5.x different such that
> httpd's Makefile.win would care?
>
> httpd itself doesn't use apr escape and shouldn't care that apr
> happens to have a build utility of the same name as one of its own
> (or something is borked).

The httpd 2.2 Makefile.win build invokes the pcre, expat, apr, apr-iconv
and apr-util builds project-by-project, it doesn't use any corresponding
top-level build mechanics.  This was one aspect that was greatly improved
by moving to the httpd-2.4 model.

If httpd doesn't pre-build gen_test_char before apr.mak, then the apr
build will fail, unless we nest the new gen_test_char pre-build.

I think the better solution for a one-source file, source generation
app is to embed that build into the [lib]apr.dsp/mak files for now.
But as an alternative, we can teach httpd 2.2 Makefile.win to anticipate
this requirement if that project is present.  That would mean that 1.5
apr wouldn't build with older httpd 2.2 releases, only the next release
onwards.





--
Born in Roswell... married an alien...
http://emptyhammock.com/